linux-kernel - Re: Linux 2.6.34 (rt2860 regression)

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:	Tue, 18 May 2010 05:55:39 -0700
From:	Greg KH <greg@...ah.com>
To:	CaT <cat@....com.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>, bzolnier@...il.com,
	stable@...nel.org, ben@...adent.org.uk,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.34 (rt2860 regression)

On Tue, May 18, 2010 at 09:44:26PM +1000, CaT wrote:
> On Sun, May 16, 2010 at 02:39:36PM -0700, Linus Torvalds wrote:
> > So 2.6.34 is out, and the merge window is thus officially open. As usual, 
> > I probably won't do any real pulls for a day or two, in the (probably 
> > futile) hope that we'll have more people running plain 2.6.34 for a while. 
> > But you can certainly start sending me pull requests.
> > 
> > Go forth and test,
> 
> Whilst I realise this is for a staging driver... On 2010/3/4 the firmware
> for the rt2860 driver (amongst others) was removed as part of a patch
> to get the driver to use request_firmware(). See:
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c22202faade08b6b45f14fd86bfb57f79d73464c
> 
> The firmware is in the linux-firmware.git repository and has been for a
> while (at least I think that's the right firmware):
> 
> http://git.kernel.org/?p=linux/kernel/git/airlied/linux-firmware.git;a=history;f=rt2860.bin;h=778a771716aff389c79fec3b245ed00beba23a67;hb=HEAD
> 
> Is there any chance of this making it into 2.6.34.1/35 so that the driver
> works again as it once did?

I do not understand.  The firmware is now part of the linux-firmware
tree, and if you install that, it is working just fine, right?  We moved
the firmware out of the kernel tree on purpose.

So what is the problem here?

confused,

greg k-h
--
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/