Garrett D'Amore wrote: > elxl as it stands today suffers from a few significant flaws: > > 1) No support for automatic link negotation/reporting. This means it > won't work with nwam.
Seems to work just fine for me when I've used that interface. > 2) No support for full MTU vlans. Don't care. > 3) Closed source. Don't particularly care but porting from a BSD variant could fix that. What I'm saying is I don't care if the current source is used or if it is "rewritten" using a port from elsewhere. What I care about is that I don't think the time is right to EOL this driver. > Finally, there is a community alternative available, that is not > integrated into ON. Murayama has written an alternative driver, but > I've not spent any time with it. I'd suggest then that instead of EOL of the hardware the newer open source driver is integrated under the name elxl. > From my perspective, I just don't see these parts as continuing to be > relevant enough to warrant any significant development effort spent on > their behalf. I'm still not convinced that removing it is worth alienating people that have such hardware given the (once) popularity of this device. -- Darren J Moffat
