linux-kernel - Re: what determines how firmware is loaded? (Q. on request

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] [day] [month] [year] [list]

Message-ID: <20120426154844.GL3207@opensource.wolfsonmicro.com>
Date:	Thu, 26 Apr 2012 16:48:45 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	George Nychis <gnychis@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: what determines how firmware is loaded? (Q. on request_firmware
 details)

On Thu, Apr 26, 2012 at 08:27:42AM -0700, Greg KH wrote:
> On Thu, Apr 26, 2012 at 04:23:10PM +0100, Mark Brown wrote:

> > Unfortunately 3.0 is what ICS is based off so the overwhelming majority
> > of vendor code is going to be based on it until the next Android
> > release.  With my vendor hat on I have to say that we find our upstream
> > first policy extremely effective so we shouldn't be part of the issue.

> That's great, and understandable, but the original poster said they were
> using an old Ubuntu release, and the ability for the community to
> support bugs in older kernel releases like this is very difficult as you
> well know.

Oh, I missed that bit of the thread - if they're using a desktop distro 
then upgrading should be much less painful than it would be with a
typical vendor kernel.

> The next Android release should be "any day now" so hopefully we move on
> from 3.0 soon...

Well, by the end of the summer or something - even when the release
drops there's always lag while the releases propagate out to the wider
market.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)