From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757268Ab0ERMzy (ORCPT ); Tue, 18 May 2010 08:55:54 -0400 Received: from kroah.org ([198.145.64.141]:53514 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753281Ab0ERMzt (ORCPT ); Tue, 18 May 2010 08:55:49 -0400 Date: Tue, 18 May 2010 05:55:39 -0700 From: Greg KH To: CaT Cc: Linus Torvalds , bzolnier@gmail.com, stable@kernel.org, ben@decadent.org.uk, Linux Kernel Mailing List Subject: Re: Linux 2.6.34 (rt2860 regression) Message-ID: <20100518125539.GA23181@kroah.com> References: <20100518114426.GY2657@zip.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100518114426.GY2657@zip.com.au> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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