Hi! Am 04.03.2012 18:45, schrieb Carsten Hey:
>> There are also a lot of network interfaces that don't have MDIO-managed >> PHYs, and then there are 10G PHYs with a different register set (see >> IEEE 802.3 clause 45). This is why Linux provides the ethtool API to >> get PHY state with a little more abstraction. >> >> I suggest that you refer to ethtool as the preferred tool for modern >> network drivers, but leave mii-diag around for old drivers that don't >> support the ethtool API. I don't see any need to remove it as it should >> still work for that old hardware. > Ben's arguments and his suggestion are plausible. Alex, please consider > running "bts severity 301239 important" :) Hmmm... Considering what Ben said (I didn't knew there are network cards not supportied by ethtool, and maintained the package mostly for the lazy like me, who don't want to learn a new thing), I'd like to propose the following solution: What about adding a hint to README.Debian and the package description, pointing out, that it is a legacy package for older network cards, pointing to ethtool for newer hardware, and adding a suggest:ethtool to the package. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
