[<prev] [next>] [day] [month] [year] [list]
Message-ID: <47FE9446.7010404@canonical.com>
Date: Thu, 10 Apr 2008 18:27:18 -0400
From: Stefan Bader <stefan.bader@...onical.com>
To: linux-usb@...r.kernel.org, netdev@...r.kernel.org
CC: Petko Manolov <petkan@...leusys.com>
Subject: [PATCH] Enhanced matching code for pegasus driver (was blacklist
support)
I have reworked the patch from using a blacklist to using the enhanced
matching macros. While certainly going into the right direction I got
one problem: although this certainly will prevent the bluetooth adapter
from loading I cannot tell (due to missing hardware) whether this will
not prevent the ethernet dongle from working.
So question is a) does the approach look good and b) has somebode a
Belkin usb ethernet adapter to verify the class, subclass and protocol?
Regards,
Stefan
> I have been working on a problem which arose from the fact that (at
> least one vendor) some vendors use the same vendor and model number for
> different pieces of hardware.
> In this case the Belkin bluetooth dongle uses the same numbers as the
> network adapter which causes machines to lock up as soon as the
> bluetooth dongle gets inserted.
> As far as I found there had been discussions about adding some sort of
> blacklisting support to the pegasus module before but I have not found
> any code doing so.
> This is what the attached patch does. There is possibly much room for
> improvement but at least it seems to work. Would it be possible to
> include something like this in the mainline driver?
View attachment "pegasus4.diff" of type "text/x-diff" (1736 bytes)
Powered by blists - more mailing lists