From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [meta-yocto-bsp] [dylan] linux-yocto_3.2 version mismatch
Date: Sat, 13 Jul 2013 10:52:04 -0400 [thread overview]
Message-ID: <51E16994.5040809@windriver.com> (raw)
In-Reply-To: <CANyK_8f=m4k8AD63z8YT8ebi0Ayz_nJdH5codGWHVkDpW1iw=Q@mail.gmail.com>
On 13-07-13 10:27 AM, Paul Barker wrote:
> I'm building from the dylan branch with:
>
> DISTRO = "poky"
> MACHINE = "beagleboard"
> PREFERRED_VERSION_linux-yocto = "3.2%"
>
> BBLAYERS = " \
> .../poky/meta \
> .../poky/meta-yocto \
> .../poky/meta-yocto-bsp \
> .../meta-openembedded/meta-oe \
> .../meta-udaq \
> "
>
> (meta-udaq is my private layer for this device)
>
> I'm getting a file in tmp/deploy/images named
> "uImage--3.2.32+git0+e7f2fdc48f8808887175f0328274a2668084738c_40bde7a43ef3cd85729ab02464a7ecdf71e522a6-r4.1.4-beagleboard-20130712125255.bin":
> note the 3.2.32 version.
>
> When running on the Beagleboard, uname -a reports version 3.2.18.
>
> The commit hash 40bde7a43ef3cd85729ab02464a7ecdf71e522a6 is set in
> .../poky/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.2.bbappend
> and checking the git log for linux-yocto-3.2, this does refer to
> version .18.
>
> So my guess is we should do one of the following:
> a) Modify PV (or LINUX_VERSION) in the bbappend to reflect the correct version?
> b) Bump the git commit hash used for beagleboard to 3.2.32?
(b) is the right solution. Bump the hash to match the PV. The qemu* BSPs
in the branch would likely show .32 and that's the tested version, but
clearly the bb needs an update as well.
Bruce
>
> I know 3.2 is old, but the APIs I'm using for my kernel driver were
> ditched in the 3.3 kernel release and 3.2 has a predicted upstream EOL
> of 2016.
>
> Thanks,
>
> --
> Paul Barker
>
> Email: paul@paulbarker.me.uk
> http://www.paulbarker.me.uk
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-07-13 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 14:27 [meta-yocto-bsp] [dylan] linux-yocto_3.2 version mismatch Paul Barker
2013-07-13 14:52 ` Bruce Ashfield [this message]
2013-07-13 14:56 ` Paul Barker
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=51E16994.5040809@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=paul@paulbarker.me.uk \
--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.