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.
the version is not the version of the can network device, it's the
version of the device you're loading the driver for.
>
> 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.
>
> Further suggestions?
firmware_update: when CAN link is down, you'd be able to destroy the CAN
netdevice, create a firmware update node (I lost the exact function
calls), do your update, recreate the network interface again, ....
>
> Matthias
Kurt
> _______________________________________________
> Socketcan-core mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/socketcan-core
_______________________________________________
Socketcan-core mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-core
