On Wed, 2007-08-15 at 12:51 +1000, Boyd Adamson wrote:
> "Garrett D'Amore" <[EMAIL PROTECTED]> writes:
> > On Tue, 2007-08-14 at 10:27 -0700, Artem Kachitchkine wrote:
> >> > For example, there are two major variants of realtek 8139. The
> >> > main 8139 family, which is pretty "sucky", and the 8139C+. The
> >> > 8139C+ supports pretty much everything that the 8169 does
> >> > (including vlan tagging, hardware checksum offload, descriptor
> >> > based DMA, etc.)
> >> >
> >> > The way to tell the difference is to look at a revision register
> >> > that isn't part of the normal PCI configuration space.
> >>
> >> Wouldn't the right solution be to merge two drivers?
> >
> > No. Sometimes you have to have separate drivers.
> >
> > For hme/qfe, this is required for backwards compatibility.
>
> I realise that this is not going to solve the general problem, and I
> don't know what the dependency timing is like, but would the link vanity
> naming help to smooth the transition in the case of hme/qfe? Some kind
> of automatic vanity name that makes hme3 into qfe2 or whatever?
I hate to rely on vanity naming for this.
In truth, on x86, I'm willing to punt for now. All qfe/hme boards can
just be "hme" on x86.
I was actually looking for a more general solution to the problem. If
no general solution is available, I'll punt in this particular case.
Likewise for rge/rtls (although the few owners of 8139C+ chips will
suffer the miserable performance of rtls even though the hardware is
capable of much much more.)
-- Garrett
>
> Boyd
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
