> Ouch. This bus ID format is pretty nasty. It includes vendor and > product IDs, which really do not belong there. And the last part is an > auto-incremented counter, so it isn't stable. > > I've done what I could to make it fit in what libsensors expects, but > this is less than perfect. And I expect this bus ID format to evolve > over time, because I can't be the only one thinking it sucks. So we may > have to update libsensors for future kernels. Well if you need a unique per-device ID (unique if you connect multiple devices) then the USB bus number and the device ID you have chosen would seem to be the most appropriate. If you need a value that is unique across reboots then I imagine the USB vendor/device ID would be the only option - this device doesn't seem to have a unique serial number as many USB devices do. > For now, can you please send me the output of: > $ ls -l /sys/bus/hid/devices total 0 drwxr-xr-x 2 root root 0 2009-10-12 22:35 . drwxr-xr-x 4 root root 0 2009-10-12 22:35 .. lrwxrwxrwx 1 root root 0 2009-10-12 22:35 0003:046D:C226.0001 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.0/0003:046D:C226.0001 lrwxrwxrwx 1 root root 0 2009-10-12 22:35 0003:046D:C226.0002 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.1/0003:046D:C226.0002 lrwxrwxrwx 1 root root 0 2009-10-12 22:35 0003:046D:C525.0003 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.2/3-2.2:1.0/0003:046D:C525.0003 lrwxrwxrwx 1 root root 0 2009-10-12 22:35 0003:046D:C525.0004 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.2/3-2.2:1.1/0003:046D:C525.0004 lrwxrwxrwx 1 root root 0 2009-10-12 22:35 0003:1044:4001.0012 -> ../../../devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/0003:1044:4001.0012 > OK, let's handle it as a HID device then. Experimental libsensors patch > at the end of this message, please give it a try and report. I couldn't > test it so there might be some rough edges left. Ha, it worked perfectly: $ ./sensors ... odin-hid-3-12 Adapter: HID adapter 3.3V: +3.40 V 5V: +5.14 V 5VSB: +5.13 V 12V1: +12.11 V 12V2: +12.16 V 12V3: +12.15 V 12V4: +12.07 V -12V: -12.25 V PSU Fan: 1095 RPM System Fan: 700 RPM Internal: +40.0°C External 1: +0.0°C External 2: +0.0°C External 3: +0.0°C External 4: +0.0°C 5V: 27.01 W 12V1: 11.40 W 12V2: 11.68 W 12V3: 16.59 W 12V4: 13.83 W Total: 91.45 W 5V: +5.25 A 5VSB: +1.25 A 12V1: +0.94 A 12V2: +0.96 A 12V3: +1.37 A 12V4: +1.15 A -12V: +0.00 A > This power supply unit you're working on seems pretty cool. Is this > something one can buy for his/her PC, or only meant for high end server > racks or something? Care to tell us the brand and model name? I would > love to have a monitorable PSU. Sure, it's a standard ATX power supply, comes in 550W and 800W versions. Same USB ID/driver for both. It's manufactured by Gigabyte, and it's called an Odin GT. Manufacturer web page is here: http://www.gigabyte.com.tw/Products/PowerSupply/Products_Spec.aspx?ProductID=2490 If you buy one, be sure to let Gigabyte know you bought it because of the Linux support - they didn't want to give out any specs because they were worried it might send them out of business... >> If it would help I can post a gadgetfs userspace program I wrote to emulate >> the device. > > Yes, please post it together with explanations how to use it. If I can > emulate the device and test my libsensors patches myself, this should > be much faster. Okay, I'll tidy it up and get it ready. In order to run it you will need the following options enabled in your kernel (I have them all as modules): USB_GADGET (Device drivers, USB support, USB Gadget Support) USB_GADGET_DUMMY_HCD (USB Gadget Support, USB Peripheral Controller, Dummy HCD) USB_GADGETFS (USB Gadget Support, USB Gadget Drivers, Gadget Filesystem) I'll post instructions on what to do once the modules are loaded when I post the code shortly. Cheers, Adam. _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
