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

Message-ID: <20120426152310.GB26692@sirena.org.uk>
Date:	Thu, 26 Apr 2012 16:23:10 +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 Mon, Apr 23, 2012 at 03:56:03PM -0700, Greg KH wrote:

> You do realize just how old and obsolete your 3.0.8 kernel is, right?  I
> suggest you update to the latest version, or, if you are stuck with this
> kernel, go ask the vendor who provided it to you for support, as they
> are the best ones to help you out.

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.
--
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/