atom feed43 messages in org.freebsd.freebsd-archRe: Extending sys/dev/mii
FromSent OnAttachments
Stefan BethkeJan 4, 2012 8:03 am 
Adrian ChaddJan 4, 2012 9:07 am 
Marius StroblJan 4, 2012 1:59 pm 
Stefan BethkeJan 5, 2012 12:52 pm 
Stefan BethkeJan 6, 2012 4:56 am 
Stefan BethkeJan 6, 2012 5:02 am.diff
Marius StroblJan 6, 2012 10:27 am 
Stefan BethkeJan 6, 2012 12:35 pm 
Marius StroblJan 6, 2012 1:47 pm 
Stefan BethkeJan 6, 2012 1:52 pm 
Marius StroblJan 8, 2012 5:00 am 
Stefan BethkeJan 8, 2012 2:27 pm 
Adrian ChaddJan 10, 2012 5:18 pm 
Marius StroblJan 11, 2012 11:37 am 
Adrian ChaddJan 14, 2012 8:15 pm 
Warner LoshJan 14, 2012 9:13 pm 
Stefan BethkeJan 20, 2012 3:08 pm.patch
Warner LoshJan 20, 2012 5:43 pm 
Oleksandr TymoshenkoJan 20, 2012 8:12 pm 
Stefan BethkeJan 21, 2012 4:02 am 
Aleksandr RybalkoJan 21, 2012 5:12 am 
Oleksandr TymoshenkoJan 23, 2012 11:45 pm 
Aleksandr RybalkoJan 24, 2012 5:53 am 
Marius StroblJan 25, 2012 2:17 pm 
Warner LoshJan 25, 2012 2:28 pm 
Marius StroblJan 25, 2012 3:21 pm 
Hans Petter SelaskyJan 26, 2012 8:24 am 
Stefan BethkeJan 26, 2012 8:24 am 
Stefan BethkeJan 26, 2012 8:30 am 
Marius StroblJan 27, 2012 6:15 am 
Adrian ChaddFeb 10, 2012 9:22 pm 
Marius StroblFeb 11, 2012 3:17 am 
Aleksandr RybalkoFeb 11, 2012 4:45 am 
Adrian ChaddFeb 11, 2012 4:59 pm 
Warner LoshFeb 11, 2012 5:15 pm 
Adrian ChaddFeb 11, 2012 8:48 pm 
Warner LoshFeb 11, 2012 8:58 pm 
Juli MallettFeb 11, 2012 9:05 pm 
Adrian ChaddFeb 11, 2012 9:19 pm 
Aleksandr RybalkoFeb 12, 2012 9:51 am 
Aleksandr RybalkoFeb 12, 2012 10:04 am 
Juli MallettFeb 12, 2012 10:30 am 
Aleksandr RybalkoFeb 12, 2012 10:38 am 
Subject:Re: Extending sys/dev/mii
From:Stefan Bethke (st@lassitu.de)
Date:Jan 21, 2012 4:02:28 am
List:org.freebsd.freebsd-arch

Am 21.01.2012 um 02:43 schrieb Warner Losh:

On Jan 20, 2012, at 5:08 PM, Stefan Bethke wrote:

The second problem is that there's currently no way to express a dependency
between two devices other than a parent-child relationship. I would be
interested to learn why this appears to be so uncommon that I could not find any
discussion of such a feature. Has it really never before come up?

Sure there is: you can do it by name. I wrote a driver that attached to the ISA
bus, but also needed to talk to the ppbus that was attached to the printer. My
solution was to have a post-attach name-lookup so that it could then call
methods on the other driver's device_t. I wonder why we can't do that here?

That was my first approach, but the attachment sequence foiled it: arge0 is
probed and attached before the device that provides the MDIO bus arge0 needs to
attach the miibus and phy. As far as I can tell, there is no way to express
(via code or hints or otherwise) that a device should be attached only after
some other device has been attached.

The solution for me was to write miiproxy which contains code that waits for
both devices to attach, and then calls a callback on arge0 to complete the
interface attachment (attaches miibus, makes the interface available).

From a driver writers point of view, it would be desirable to be able to say
"attach this only after 'foo0' has been attached", so the attach method can
still be a single, linear piece of code.

Stefan