[yocto] [raspberrypi] raspi3 vs raspi2
Herve Jourdain
herve.jourdain at neuf.fr
Mon Nov 21 22:14:36 PST 2016
Hi Trevor,
I've never tried with 4.8, but I sent patches to the list that add 64 bits support for 4.7.10 - and this one, I tested and it is working.
It's probably possible to port 64 bits to 4.4 as well, but I'm not sure if it's worth the effort.
I have 4.7 covered, there is some "built-in" level of support in 4.8 (but I don't know what's working or not there), and I'll sure work it for 4.9 soon.
Herve
-----Original Message-----
From: Trevor Woerner [mailto:twoerner at gmail.com]
Sent: mardi 22 novembre 2016 06:39
To: Khem Raj <raj.khem at gmail.com>
Cc: Herve Jourdain <herve.jourdain at neuf.fr>; yocto at yoctoproject.org
Subject: Re: [yocto] [raspberrypi] raspi3 vs raspi2
On Mon 2016-11-21 @ 04:09:50 PM, Khem Raj wrote:
> 4.4 does not support 64-bit pi3, do you set the PREFERRED_VERSION in
> local conf metadata ?
Yes, my conf/local.conf contains:
PREFERRED_VERSION_linux-raspberrypi = "4.8%"
If you clone git://github.com/raspberrypi/linux.git and checkout the 4.8.y branch, you'll see that there's no commit
ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7 anywhere in that branch. In fact there is no such commit anywhere in that repository:
$ git branch --contains ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7
error: no such commit ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7
>
> On 11/21/16 3:07 PM, Trevor Woerner wrote:
> > On Sun 2016-11-20 @ 11:28:48 AM, Khem Raj wrote:
> >> I gave a whirl at building and looking closely at them. As it seems
> >> the OE core patch is not needed since for armv8 we want to keep it
> >> like x86 ( common ) I have therefore made changes to your patches
> >> and staged them here.
> >>
> >> https://github.com/kraj/meta-raspberrypi/commits/kraj/master
> >>
> >> Which should work without any change in OE-Core, secondly I have
> >> further divided them and also fixed 4.8 to compile arm64.
> >
> > I tried giving this a whirl.
> >
> > Maybe the order of my layers in bblayers isn't correct, but by
> > default my build uses 4.4% instead of 4.8%.
> >
> > conf/machine/raspberrypi3-64.conf includes:
> > ...
> > include conf/machine/include/rpi-base.inc
> > ...
> > PREFERRED_VERSION_linux-raspberrypi ?= "4.8.%"
> >
> > conf/machine/include/rpi-base.inc contains:
> > ...
> > include conf/machine/include/rpi-default-versions.inc
> > ...
> >
> > conf/machine/include/rpi-default-versions.inc contains:
> > ...
> > PREFERRED_VERSION_linux-raspberrypi ?= "4.4.%"
> >
> > In any case when I try building with 4.4 I get:
> >
> > ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0 do_kernel_configme: No default configuration for raspberrypi3-64 / bcmrpi3_defconfig available.
> > ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0
> > do_kernel_configme: Function failed: do_kernel_configme (log file is
> > located at
> > /z/layerindex-master/raspi3-64/tmp-glibc/work/raspberrypi3_64-oe-lin
> > ux/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_k
> > ernel_configme.15498)
> >
> > When I switch to 4.8 explicitly in my conf/local.conf I get:
> >
> > ERROR: linux-raspberrypi-1_4.8.8+gitAUTOINC+ea6eeaff07-r0 do_fetch: Fetcher failure: Unable to find revision ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7 in branch rpi-4.8.y even from upstream
> > ERROR: linux-raspberrypi-1_4.8.8+gitAUTOINC+ea6eeaff07-r0 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y'. Unable to fetch URL from any source.
> >
> > My build configuration is:
> > Build Configuration:
> > BB_VERSION = "1.32.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "opensuse-42.1"
> > TARGET_SYS = "aarch64-oe-linux"
> > MACHINE = "raspberrypi3-64"
> > DISTRO = "nodistro"
> > DISTRO_VERSION = "nodistro.0"
> > TUNE_FEATURES = "aarch64"
> > TARGET_FPU = ""
> > meta-raspberrypi__kraj = "kraj/master:4735e7cde210b2b0b855bca1eb90ef4adca8019b"
> > meta = "master:a675b2c89e477af088faee9b3be96eae19a85f0b"
> > meta-oe
> > meta-gnome = "master:7f8915a6ecdd5c4b03c7e5b5f1fa903f89c2d560"
> >
>
More information about the yocto
mailing list