Kurt Van Dijck wrote: > On Mon, Nov 02, 2009 at 03:33:25PM +0100, Matthias Fuchs wrote: >> Hi, >> >> I am wondering what is the best way to provide >> some product information for a CAN interface device (hardware version, >> serialno, firmware version)? My favour way is to generate some files >> in sysfs as it is typically (but limited) done for USB devices. > I've done similar things within the softing pcmcia driver. >> Would /sys/class/net/can*/version be suitable? > I believe not. >> Any suggestions? > The properties you're referring to, are attached to the device (USB, > PCMCIA, ..., platform, ), not the CAN network (class) device.
Yep. > the version is not the version of the can network device, it's the > version of the device you're loading the driver for. If you mean the driver version, then it's not even a per device property. Examples: $ find /sys/module/ -name version >> And next question: how should we implement a way to update >> the firmware of a CAN interface? Devices might load firmware on >> every driver start. This could be handled by Linux' firmware >> mechanism. But what kind of interface should be used for >> a flash firmware updater? /sys/class/net/can*/firmware ? > same as above. It's very driver specific. > By having it within the CAN netdevice structure, you'd overload the CAN > device infrastructure. It's better done directly at the device itself. I fully agree. And there is also little chance to get files in /sys/class/net/can*/ accepted because it's for network specific stuff. Wolfgang. _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
