All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH] linux-raspberrypi_4.9.bb: Update to 4.9.12
Date: Sat, 25 Feb 2017 18:00:00 -0800	[thread overview]
Message-ID: <20170226015948.GA9477@carbonA> (raw)
In-Reply-To: <CAMKF1srVyEa8_0BoS750zPoyNuhmVA6VEue4m--11petEqNj9g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]

On Sat, Feb 25, 2017 at 10:16:24AM -0800, Khem Raj wrote:
> On Sat, Feb 25, 2017 at 1:11 AM, Paul Barker <paul@paulbarker.me.uk> wrote:
> > On Fri, 24 Feb 2017 16:03:59 -0800
> > Khem Raj <raj.khem@gmail.com> wrote:
> >
> >> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >> ---
> >>  recipes-kernel/linux/linux-raspberrypi_4.9.bb | 4 ++--
> >>  1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> >> b/recipes-kernel/linux/linux-raspberrypi_4.9.bb index
> >> dcca369..b41a8ef 100644 ---
> >> a/recipes-kernel/linux/linux-raspberrypi_4.9.bb +++
> >> b/recipes-kernel/linux/linux-raspberrypi_4.9.bb @@ -1,8 +1,8 @@
> >>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
> >>
> >> -LINUX_VERSION ?= "4.9.10"
> >> +LINUX_VERSION ?= "4.9.12"
> >>
> >> -SRCREV = "095c4480e1f623bdc8a221a171ef13b2223706b1"
> >> +SRCREV = "c1271995832a090a94eb3b1c1678cb51b84ef1ca"
> >>  SRC_URI =
> >> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y
> >> \
> >> file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
> >> \ "
> >
> > rpi-4.9.y is now the default branch upstream and they've started
> > merging in new stable releases instead of rebasing. So how soon do we
> > want to make 4.9.y the default in meta-raspberrypi?
> >
> > I've already tested a 4.9 series kernel with u-boot on an rpi and an
> > rpi3 so I'm happy that it all looks good.
> >
> > I'm away this weekend so I can't send the patch right now myself. If
> > no-one else jumps on it I'll send a patch towards the end of the week
> > to change the default.
>
> Lets apply this patch so we get away from this rebasing business quickly.
> however I would like to wait for us to make it default may be a week or so
> I have some issues bringing up wlan0 with 4.9 and would like to see why I get
>
> ifup wlan0
> Successfully initialized wpa_supplicant
> rfkill: WLAN soft blocked
> Could not set interface wlan0 flags (UP): Operation not possible due to RF-kill

That is interesting. I've seen it on old kernel versions too. Everytime
disappeared by itself.

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2017-02-26  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25  0:03 [meta-raspberrypi][PATCH] linux-raspberrypi_4.9.bb: Update to 4.9.12 Khem Raj
2017-02-25  9:11 ` Paul Barker
2017-02-25 18:16   ` Khem Raj
2017-02-26  2:00     ` Andrei Gherzan [this message]
2017-02-26  6:19       ` Gary Thomas

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=20170226015948.GA9477@carbonA \
    --to=andrei@gherzan.ro \
    --cc=raj.khem@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.