linux-kernel - Re: [Rt2400-devel] [PATCH] rt2500usb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Oct 2007 18:33:54 -0400 (EDT)
From:	Parag Warudkar <kernel-stuff@...cast.net>
To:	Adam Baker <linux@...er-net.org.uk>
cc:	rt2400-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}



On Thu, 25 Oct 2007, Adam Baker wrote:

>
> Unfortunately Belkin have sold both RT73 and RT2500 devices with
> that USB ID. You don't say what distro you are runing or what version
> of RT2x00 it ships with but last time I checked with the git version of
> rt2x00 it tried to load both drivers but the rt2500 driver noticed it was the
> wrong hardware and shut down.

Like I said this did not work with 2.6.24-rc1 (latest git). My distro 
(Ubuntu 7.10) kernel 2.6.22-10 also has the same behavior.

> There are a few such devices but they are all cases where there are reliable
> reports of manufacturers shipping both device types with one USB ID. There
> are some cases where the alternate chipset with the same USB ID isn't even a
> ralink device but there isn't much we can do about those.
>

Ok, I failed to imagine the hardware makers' stupidity :) - In the case 
that you mentioned I agree that there is little that can be done based on 
device IDs. I'll check out subsequent releases to see if it gets fixed 
based on hardware characteristics (rt2500usb unloading and requesting the 
right one in my case for example).

Thanks

Parag
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/