Wolfgang Grandegger wrote: > Oliver Hartkopp wrote: >> But IMO we should discuss about obviously 'common' sysfs entries like >> >> serialnumber >> firmwareversion >> vendorstring >> ... >> >> There are already some things defined in ethtool: >> >> linuxbox:~# ethtool -i eth0 >> driver: tg3 >> version: 3.102 >> firmware-version: 5755m-v3.29 >> bus-info: 0000:09:00.0 >> >> and whatever we add to /sys/class/net/can0/... >> >> it should fit into the current networking system. > > ethtool uses ioctls. They will tell us to use netlink nowadays. But it > might be worth a try.
I did not want to suggest to use ioctl() ... I just wanted to point at other implementations implementing this kind of interface. I think with netlink and sysfs for the above mentioned use-cases we can fit the latest netdev development requirements. Regards, Oliver _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
