| 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: Fri, 11 Apr 2014 09:51:39 +0200 From: Arend van Spriel <arend@...adcom.com> To: "Luis R. Rodriguez" <mcgrof@...not-panic.com> CC: Takashi Iwai <tiwai@...e.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Felix Fietkau <nbd@...nwrt.org>, "backports@...r.kernel.org" <backports@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Jiri Slaby <jslaby@...e.cz>, Mauro Carvalho Chehab <m.chehab@...sung.com> Subject: Re: Bumping required kernels to 3.0 for Linux backports ? On 10/04/14 20:56, Luis R. Rodriguez wrote: > On Thu, Apr 10, 2014 at 10:04 AM, Arend van Spriel <arend@...adcom.com> wrote: >> Ok, I guess my voice was cracking when I mentioned 2.6.38 as being used over >> here. I am probably alone in that desert. > > I thought broadcom didn't use backports? If they do can you explain > how? Also what drivers do you need enabled for your use case ? That was 2 years ago when you asked me ;-) Since then I have been using it to backport the brcm80211 mainline drivers to 1) Android kernel, ie. 3.4 kernel, and 2) Fedora 19 which is actually fixed to 3.11 kernel. So we use backports these days for enabling brcm80211 drivers on various test equipment that uses older kernels. Regards, Arend -- 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