Garrett D'Amore wrote: > Casper.Dik at Sun.COM wrote: >>> James Carlson wrote: >>> >>>> Garrett D'Amore wrote: >>>> >>>>> 1) No support for automatic link negotation/reporting. This means it >>>>> won't work with nwam. >>>>> 2) No support for full MTU vlans. >>>>> 3) Closed source. >>>>> >>>> None of those things matter for the existing users. ;-} >>>> >>> nwam will start to matter when we switch to using >>> network/physical:nwam by default. >>> >> >> It is strange because an earlier driver *did* properly proper >> full/duplex but this was removed at some time. >> > > Full/duplex works. What doesn't work is link *notification*. I'm sorry > if this was confusing.
Yep; link up/down is missing there. But it's actually missing on a lot of interfaces that people use today, including most (all?) third-party drivers. It's a common annoyance. The old NWAM had kludges to work around some interfaces with stuck-on link status. The new NWAM will need the same. But using lack of link status as a justification for nuking an otherwise usable old driver seems a bit too much to me. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
