From: Arend van Spriel <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felix Fietkau <nbd@openwrt.org>,
"backports@vger.kernel.org" <backports@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiri Slaby <jslaby@suse.cz>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: Bumping required kernels to 3.0 for Linux backports ?
Date: Fri, 11 Apr 2014 09:51:39 +0200 [thread overview]
Message-ID: <53479F0B.6070909@broadcom.com> (raw)
In-Reply-To: <CAB=NE6Wpa4gG14+XYVkT_=_t-cZXvO0FD_Q1T7tB1yiSmNBraw@mail.gmail.com>
On 10/04/14 20:56, Luis R. Rodriguez wrote:
> On Thu, Apr 10, 2014 at 10:04 AM, Arend van Spriel <arend@broadcom.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
next prev parent reply other threads:[~2014-04-11 7:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 1:03 Bumping required kernels to 3.0 for Linux backports ? Luis R. Rodriguez
2014-04-09 9:18 ` Felix Fietkau
2014-04-09 18:28 ` Luis R. Rodriguez
2014-04-09 19:12 ` Greg Kroah-Hartman
2014-04-09 20:01 ` Luis R. Rodriguez
2014-04-09 20:22 ` Greg Kroah-Hartman
2014-04-09 20:52 ` Luis R. Rodriguez
2014-04-09 21:06 ` Greg Kroah-Hartman
2014-04-10 7:31 ` Johannes Berg
2014-04-10 7:44 ` Takashi Iwai
2014-04-10 16:59 ` Luis R. Rodriguez
2014-04-10 17:04 ` Arend van Spriel
2014-04-10 17:11 ` Luis R. Rodriguez
2014-04-10 18:56 ` Luis R. Rodriguez
2014-04-11 7:51 ` Arend van Spriel [this message]
2014-04-11 18:18 ` Luis R. Rodriguez
2014-04-10 17:16 ` Johannes Berg
2014-04-10 17:26 ` Felix Fietkau
2014-04-10 17:35 ` Johannes Berg
2014-04-09 10:59 ` Arend van Spriel
2014-04-09 18:25 ` Luis R. Rodriguez
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=53479F0B.6070909@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mcgrof@do-not-panic.com \
--cc=nbd@openwrt.org \
--cc=tiwai@suse.de \
/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