On Fri, May 13, 2011 at 6:58 AM, Ben Hutchings <[email protected]> wrote: > On Wed, 2011-05-11 at 09:25 -0700, Walter Goldens wrote: >> > As mentioned by Jan, the device contains a RT3572 >> > chipset. Its entry >> > could moved into the section for known RT35XX devices (i.e. >> > "#ifdef >> > CONFIG_RT2800USB_RT35XX") as an alternative. >> > >> > Geoff >> >> This has already been done: >> http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=commitdiff;h=ce2919c9fffe2aa52f9c3e327176d03764dbf9b5 > > That's all very well, but that isn't going to get into a stable release > for another 3 months! Device ID updates that don't require new > supporting code should be sent upstream straight away (and cc'd to > [email protected]). > > I've cherry-picked this and the other two updates in rt2800usb that > aren't in Linus's tree, but that doesn't help the users of other > distributions that would benefit from them.
Well, as this moving of the USB ID to a different (now named) set of USB IDs in the code is not going to help the users, as rt2x00 currently does not have support for RT35xx devices yet. Some patches have been submitted for their support, but these haven't been accepted (and thus applied) yet. There's a reason why the Kconfig for these devices is stating that support for these devices is non-functional!!! That's why it didn't make sense to send this patch upstream immediately and sending it to stable made even less sense. --- Gertjan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
