Nut upsdev - Dec 2008 - [nut-commits] svn commit r1589 - in trunk: . drivers

On Mon, Dec 1, 2008 at 7:43 PM, Alexander Gordeev
<agordeev-guest at alioth.debian.org> wrote:
> Author: agordeev-guest
> Date: Tue Dec  2 00:43:04 2008
> New Revision: 1589
>
> Log:
>  * added lakeview_usb driver.
Could we possibly rename this driver before it gets into 2.4?

As I mentioned in another thread, Lakeview Research is probably not
the manufacturer.

Note that this is the same VID/PID as on this example on the Lakeview
Research home page:

   http://www.lvr.com/usb_on_a_budget.htm

We can include the name "Lakeview Research" in the documentation, but
we shouldn't lead people astray here.

-- 
- Charles Lepple

Citeren Charles Lepple <clepple at gmail.com>:
> Note that this is the same VID/PID as on this example on the Lakeview
> Research home page:
>
>  http://www.lvr.com/usb_on_a_budget.htm
>
> We can include the name "Lakeview Research" in the documentation,
but
> we shouldn't lead people astray here.
Another thing, loosely related to this, is how we are going to deal  
with the 'generic' VID:PID combinations in some of the USB drivers,  
for example the megatec_usb and (new) blazer_usb drivers. At present,  
in the megatec_usb driver we have several VID:PID combinations for  
USB-to-serial converters that are commonly found in UPSes. But what  
happens if other totally unrelated (non-UPS) devices use the same  
controllers? Or that kernel level support becomes available for them?

Unless a VID:PID combination unambiguously identifies a USB device as  
a supported UPS, using it in a HAL addon is probably not a very good  
idea. Should we remove the 'hald-addon-megatec_usb' driver before  
releasing nut-2.4?

Best regards, Arjen
-- 
Please keep list traffic on the list