Subject: Re: Sharing MII and I2C code in ethernet drivers
To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Chris G. Demetriou <cgd@pa.dec.com>
List: tech-kern
Date: 09/18/1997 09:35:31
> Oh, wait, yes I do... I think the "internal controller for MII" thing is
> really a non-issue... the fack that it's attaching to a "de" or "tl"
> instance is enough - they just provide the right function pointers in
> miibus_attach_args.
> 
> If you do this, then the ifmedia hooks for interfaces with MII are simply
> calls into the MII bus layer.

Why can't you do all of this without stuffing it into the
autoconfiguration framework?  Why the strong desire to put it there?

What kinds of things other than PHYs live on MII busses?  Can you have
mutiple PHYs on an MII bus (and does anyone do this, or have any plans
to do this)?


cgd