On Tue, 22 Jul 2003 23:36:25 -0700
Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote:
> I am not writing drivers, I'm trying to write code that works with
> everything that looks remotely like an ethernet device.
Making ethtool interfaces available on every net device is not right,
what about the ISDN folks? What if they specifically want ethtool
ioctls to fail for their devices? How can one accomplish that after
Answer: You can't.
> I can make this one change and work with ALL drivers, and not have
> to corrupt every friggin driver under the sun.
This is undesirable. Not all network drivers should implement
ethtool. A certain family of network devices may not want them,
and we must provide for this.
I don't like your change just as much as I did previously.
> Note it allows me to get a binary representation of the net_device_stats
> w/out having to parse /proc/net/dev or figure out the vast complexity
> of libnetlink.
Whatever tools you write which depend upon this will not work
on any existing 2.4.x kernel, therefore making their utility
> I have plenty of other things that are currently new ioctls that could
> be handled the same, and thus I could continue to avoid issues with
> other platforms.
What is this "other platform" issue?
If you add anything new, along the lines of SIOCDEVETHTOOl, it's
going to have to go through an entire full review process and in
that review process any necessary 32-bit ioctl translation code
would get added.