First shot at a hwmon device name mapper
cover First shot at a hwmon device name mapper
Hi all,
As discussed lately on this list, here is a first shot at a helper binary that resolves libsensors chip names to kernel device names and back.
This is really a proof of concept at this point. Everything can still be discussed and changed, just speak up if you see any problem or to ask for improvements. Specifically I have no preference for the tool's name or its command line interface, so if you can think of anything better, just let me know.
Signature · 7 lines
Jean Delvare SUSE L3 Support _______________________________________________ lm-sensors mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Quoted 6 lines · Jean Delvare
Hi all,
As discussed lately on this list, here is a first shot at a helper binary that resolves libsensors chip names to kernel device names and back.
Quoted 6 lines
This is really a proof of concept at this point. Everything can still be discussed and changed, just speak up if you see any problem or to ask for improvements. Specifically I have no preference for the tool's name or its command line interface, so if you can think of anything better, just let me know.
I tried with udev, but that doesn't work - if I understand corretly, device rename support needs explicit kernel support per subsystem. The networking subsystem does it with dev_change_name(). Other than that there is device_rename(), which is hardly used.
So I guess we have no other choice than something like this, unless we go radical and start using per-driver names (coretemp0 instead of hwmonX). But I think even that would not be reboot-safe, for example on a system with multiple sensors of the same type connected to different i2c busses. Anyway, not sure if that would be a good idea to start with.
Guenter
_______________________________________________
lm-sensors mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors