<br><br><div class="gmail_quote">2009/3/23 Kjell Claesson <span dir="ltr"><<a href="mailto:kjell.claesson@epost.tidanet.se">kjell.claesson@epost.tidanet.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
måndag 23 mars 2009 21:07:15 skrev Arjen de Korte:<br>
Hi Arjen,<br>
<div class="im">> Citeren Kjell Claesson <<a href="mailto:keyson-guest@alioth.debian.org">keyson-guest@alioth.debian.org</a>>:<br>
> > Author: keyson-guest<br>
> > Date: Mon Mar 23 17:37:37 2009<br>
> > New Revision: 1817<br>
> ><br>
> > Log:<br>
> > data/driver.list, add Eaton Powerware 9130 compatibility with bcmxcp<br>
> > and usbhid-ups.<br>
><br>
> 1) Is this really true? I would have expected that this device would<br>
> be supported through bcmxcp (serial) and bcmxcp_usb (USB), like other<br>
> Powerware (now Eaton) devices. I'm actually surprised that one unit<br>
> does support such vastly different protocols (but I have been<br>
> surprised before).<br>
><br>
</div>Yes this is a surprise to me to. But to quote our Eaton guy Arnaud.<br>
"yup, this model is an hybrid one:<br>
the right way is bcmxcp for the serial port or usbhid-ups for the USB port."<br>
<br>
And when I asked where I could put it in the driver.list:<br>
"Eaton, both with the serial (bcmxcp) and usb (usbhid-ups) please."<br>
<div class="im"></div></blockquote><div><br>I re confirm this assertion.<br>and also note that I was the first surprised by that hybridization!<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
> 2) If it indeed is a HID PDC UPS, what are the VID:PID that it uses?<br>
> Just adding it to the list may not work if we don't already use this<br>
> combination for another device. In any case, I would to see the report<br>
> descriptor and initial variable dump, to see what level of support we<br>
> can expect from it (I 'collect' report descriptors for verifying the<br>
> hidparser and libhid code).<br>
<br>
</div>You got me there, we don't know the VID:PID that it use!<br>
That was a bad mistake. Going to remove the usbhid-ups until it<br>
is confirmed.<br>
<font color="#888888"></font></blockquote><div><br>VID:PID => 0463:ffff <br></div></div>in fact, this is an MGE base (HID core + USB/HID com) but needed bcmxcp for compatibility with a big customer iirc.<br clear="all">
note that I would otherwise have added this info (lacking VID:PID) ;-)<br>I've also added for info the 2 upsc outputs (from bcmxcp and usbhid-ups).<br>If some need the drivers debug output, please let me know.<br><br>
Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>