David S. Miller wrote:
Independant of whether I'm interested in the changes, please use
ethtool in deference to ioctls. If you absolutely must use
ioctls, I can't accept the changes without updates to the
compatability layer ioctl translation code of every platform.
Ok, so the general plan would be to add new structs as needed to ethtool.h
and then extend of the the ethtool enums?
Will ethtool ioctls work for generic/virtual interfaces/drivers? I
need some way to get hooks into specific (ie dev.c, vlan, macvlan) code,
but I'm not too particular about how it gets there as long as it
isn't netlink :)
Also, for the VLAN code, it's not really adding a new ioctl, but adding a new
enum value to an existing ioctl payload...
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
|