mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: CaT <cat@zip.com.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	bzolnier@gmail.com, stable@kernel.org, ben@decadent.org.uk,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.34 (rt2860 regression)
Date: Tue, 18 May 2010 06:33:36 -0700	[thread overview]
Message-ID: <20100518133336.GA23591@kroah.com> (raw)
In-Reply-To: <20100518131706.GZ2657@zip.com.au>

On Tue, May 18, 2010 at 11:17:06PM +1000, CaT wrote:
> On Tue, May 18, 2010 at 05:55:39AM -0700, Greg KH wrote:
> > 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?
> 
> Well, the driver used to work and appears to be useless without it. I guess
> I'm wondering why it was kept out of the firmware directory where all the
> other firmware lives (and so allow the driver to simply continue to work
> and allow it to be compiled in).

Because we are not adding new firmware to the kernel tree wherever
possible, but instead, putting it in the separate linux-firmware tree.

> At the moment all the change appears to have done is break things that have
> been working without issue since before the driver was even in staging.

Just update the linux-firmware package and all will be working again.
We've been moving the firmware out of the staging drivers for a while
now, as they don't belong in the kernel tree.

thanks,

greg k-h

  reply	other threads:[~2010-05-18 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-16 21:39 Linux 2.6.34 Linus Torvalds
2010-05-17  3:00 ` Bill Davidsen
2010-05-18 11:44 ` Linux 2.6.34 (rt2860 regression) CaT
2010-05-18 12:55   ` Greg KH
2010-05-18 13:17     ` CaT
2010-05-18 13:33       ` Greg KH [this message]
2010-05-18 14:13         ` CaT
2010-05-18 14:43           ` Greg KH
2010-05-18 15:06           ` Nick Bowler
2010-05-18 16:59         ` Bill Davidsen
2010-05-18 18:37           ` Ben Hutchings
2010-05-18 20:13             ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100518133336.GA23591@kroah.com \
    --to=greg@kroah.com \
    --cc=ben@decadent.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome