<br><div><span class="gmail_quote">2005/9/25, Peter Selinger <<a href="mailto:selinger@mathstat.dal.ca">selinger@mathstat.dal.ca</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Arnaud Quette wrote:<br>><br>> Some more points while you're at it:<br>> - newhidups will have to be renamed. My aimed was to let the name until we<br>> can superceed hidups. Then remove hidups, and rename newhidups to usbhid-ups
<br>> (name proposition welcomed, but should match the fact that it's for USB/HID<br>> compliant devices, not USB only).<br><br>It seems that some combination of "nut", "ups", "usb", and "hid" is
<br>needed. The name should also be reasonably short and pronouncable.<br><br>How about "nuthid"? I personally would prefer the name to contain<br>"USB", because "HID" is a technical term from the USB specification
<br>that does not mean anything to users. But I understand the need to<br>indicate somehow that the driver does not work for all USB devices.<br>Your "usbhid-ups" also achieves this goal, as does "nut-hidusb" or
<br>"nut_generic_usb" etc. A conservative choice would be to rename<br>"newhidups" as "nuthidups".</blockquote><div><br>
the best choice IMO is to have:<br>
- "usb" as it's an USB driver<br>
- "hid" is it only support HID compliant (not only capable ;-) UPSs<br>
- "ups" for consistency with other meta drivers (snmp-ups and genericups (=>should be renamed to generic-ups?)).<br>
<br>
So usbhid-ups seems the best. Postponed to svn switch<br>
</div><br>
Another big step will be the switch to libhid. IIRC, I have something... somewhere on my disk. Just got to find it back!<br>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> - if you have a bit more time to check for the hotplug detection (linux<br>> only) / files installation (the files
libhid.usermap and libhidups, under<br>> scripts/hotplug ).<br><br>Last time I checked this, it worked fine.</blockquote><div><br>
It was more a "please, check for completion of .usermap" ;-)<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> These two files should also be renamed to something more<br>> generall. IIRC, Charles tripplite_usb driver also use libusb, so renaming
<br>> these to nut / nut.usermap, or ups / ups.usermap should be fine<br><br>Sure, why not?</blockquote><div><br>
I'm still unsure about the final name here: nut or nutusbups?</div>arguments welcome...<br>
Anyhow, postponed to svn switch<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Note that there seems to be some hotplug-ng (now binary) underway. So maybe<br>> some hotplug files changes too... To be digged.
<br><br>I would keep the current files in any case. In the future, one can add<br>a scripts/hotplug-ng directory, if the need arises (and somebody is<br>willing to contribute the scripts).</blockquote><div><br>
that was also implied ;-)<br>
We must always keep a transition period in nut, as with 1.x and 2.x, except with the driver names ;-)<br>
<br>
Arnaud</div></div><a href="http://arnaud.quette.free.fr/"></a>