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: [email protected]
http://www.paulbarker.me.uk
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
