linux-kernel - Re: [PATCH 00/33] Staging: rt{286,287,307}0: merge rt3070 with rt2870

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:	Sun, 30 Aug 2009 14:28:27 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	Marcin Slusarz <marcin.slusarz@...il.com>
Cc:	"Greg Kroah-Hartman" <gregkh@...e.de>, devel@...verdev.osuosl.org,
	Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/33] Staging: rt{286,287,307}0: merge rt3070 with rt2870

On Sunday 23 August 2009 19:33:24 Marcin Slusarz wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > Hi,
> > 
> > The final part of rt2870 and rt3070 merge.
> > 
> > It adds RT3070 chipset support to rt2870 driver and removes no longer needed
> > rt3070 driver (yes, it means one Ralink driver less in the staging tree!).
> > 
> > [ in the process many bugs in all Ralink drivers were fixed, RT2870 chipset
> >   support was converted to use the new firmware and ~1.5 KLOC were removed ]
> > 
> > I tested it on RT2860 and RT3070 chipsets already but I would need some help
> > from people with RT2870 hardware to verify those changes (Mike? Marcin?).
> 
> I tested this patchset on WUSB54GC-V3 (1737:0077) and it works fine so far.
> Unfortunately it's not rt2870 you are looking for. With rt2800usb driver I get:
> phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 1600, rf: 0006, rev: 30700200.
> so it's rt3070 chipset.

Thanks, more testing for all Ralink changes that went into staging tree
is still needed and appreciated.
--
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/