| 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
| ||
|
Date: Thu, 26 Apr 2012 08:27:42 -0700 From: Greg KH <gregkh@...uxfoundation.org> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> 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 04:23:10PM +0100, Mark Brown wrote: > 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. 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. The next Android release should be "any day now" so hopefully we move on from 3.0 soon... thanks, 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/
Powered by blists - more mailing lists