Skip to contentSkip to conversation

raspi3 vs raspi2

raspberrypi Herve Jourdain 3 participants 10 messages Nov 20, 2016 – Nov 22, 2016

lore
Share & tools
lore
#0 lore raw

Hi Khem, Trevor,

I've submitted part of it yesterday, the rest should come out today hopefully.
The 2 machine types - raspberrypi3 and raspberrypi3-64 - have been submitted to yocto/meta-raspberrypi.
They will need tune-cortexa53.inc - I've sent a version to oe-core, but I got it wrong again, so I will resend it hopefully again, along with a modified version of arch-armv8.inc.

I have some patches to support 64bits on Raspberrypi3 that should be pushed -hopefully - today. They're on 4.7.10, though.

Herve

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Khem Raj
Sent: samedi 19 novembre 2016 18:30
To: Trevor Woerner <[email protected]>
Cc: [email protected]
Subject: ***SPAM*** Re: [yocto] [raspberrypi] raspi3 vs raspi2

Quoted 5 lines · Trevor Woerner

Hi,

I was wondering if there were any plans to create a MACHINE=raspberrypi3 that treats the raspi3 like the CortexA53 that it is instead of generating images that are backwards compatible with the

CortexA7 that is the raspi2?

Thats a good question. I know few folks who have done 64bit port of OE on rpi3 so I would be interested in such patches where we add rpi3-64 machine type.
do you have patches to submit ? Please do

Quoted 8 lines

Best regards,
Trevor
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#1 lore raw

Herve

Quoted 9 lines · Herve Jourdain

Hi Khem, Trevor,

I've submitted part of it yesterday, the rest should come out today hopefully.
The 2 machine types - raspberrypi3 and raspberrypi3-64 - have been submitted to yocto/meta-raspberrypi.
They will need tune-cortexa53.inc - I've sent a version to oe-core, but I got it wrong again, so I will resend it hopefully again, along with a modified version of arch-armv8.inc.

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.

Quoted 3 lines

I have some patches to support 64bits on Raspberrypi3 that should be pushed -hopefully - today. They're on 4.7.10, though.

I think it will be better to rebase them to 4.8 and eventually 4.9 if they are not too intrusive.

Quoted 38 lines

Herve

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Khem Raj
Sent: samedi 19 novembre 2016 18:30
To: Trevor Woerner <[email protected]>
Cc: [email protected]
Subject: ***SPAM*** Re: [yocto] [raspberrypi] raspi3 vs raspi2

Quoted 5 lines · Trevor Woerner

Hi,

I was wondering if there were any plans to create a MACHINE=raspberrypi3 that treats the raspi3 like the CortexA53 that it is instead of generating images that are backwards compatible with the

CortexA7 that is the raspi2?

Thats a good question. I know few folks who have done 64bit port of OE on rpi3 so I would be interested in such patches where we add rpi3-64 machine type.
do you have patches to submit ? Please do

Quoted 8 lines

Best regards,
Trevor
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#2 lore raw

Wow, this is great news! Thanks, both of you :-)

Quoted 69 lines · Khem Raj

Herve

Quoted 9 lines · Herve Jourdain

Hi Khem, Trevor,

I've submitted part of it yesterday, the rest should come out today hopefully.
The 2 machine types - raspberrypi3 and raspberrypi3-64 - have been submitted to yocto/meta-raspberrypi.
They will need tune-cortexa53.inc - I've sent a version to oe-core, but I got it wrong again, so I will resend it hopefully again, along with a modified version of arch-armv8.inc.

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.

Quoted 3 lines

I have some patches to support 64bits on Raspberrypi3 that should be pushed -hopefully - today. They're on 4.7.10, though.

I think it will be better to rebase them to 4.8 and eventually 4.9 if they are not too intrusive.

Quoted 38 lines

Herve

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Khem Raj
Sent: samedi 19 novembre 2016 18:30
To: Trevor Woerner <[email protected]>
Cc: [email protected]
Subject: ***SPAM*** Re: [yocto] [raspberrypi] raspi3 vs raspi2

Quoted 5 lines · Trevor Woerner

Hi,

I was wondering if there were any plans to create a MACHINE=raspberrypi3 that treats the raspi3 like the CortexA53 that it is instead of generating images that are backwards compatible with the

CortexA7 that is the raspi2?

Thats a good question. I know few folks who have done 64bit port of OE on rpi3 so I would be interested in such patches where we add rpi3-64 machine type.
do you have patches to submit ? Please do

Quoted 8 lines

Best regards,
Trevor
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#3 lore raw
In reply to Khem Raj
Quoted 10 lines · Khem Raj

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-linux/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_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"

#4 lore raw

4.4 does not support 64-bit pi3, do you set the PREFERRED_VERSION in local conf metadata ?

Quoted 58 lines · Trevor Woerner
Quoted 10 lines · Khem Raj

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-linux/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_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"

#5 lore raw
Quoted 2 lines · Khem Raj

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
Quoted 61 lines · Trevor Woerner
Quoted 58 lines · Khem Raj
Quoted 10 lines

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-linux/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_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"

#6 lore raw

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:[email protected]]
Sent: mardi 22 novembre 2016 06:39
To: Khem Raj <[email protected]>
Cc: Herve Jourdain <[email protected]>; [email protected]
Subject: Re: [yocto] [raspberrypi] raspi3 vs raspi2

Quoted 2 lines · Khem Raj

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
Quoted 65 lines · Trevor Woerner
Quoted 62 lines · Khem Raj
Quoted 9 lines

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"

#7 lore raw
In reply to Trevor Woerner
Quoted 8 lines · Trevor Woerner
Quoted 2 lines · Khem Raj

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%"

Quoted 8 lines

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

Did you take

https://github.com/kraj/meta-raspberrypi/commit/361757b9c1538b0a15577d75308ecef93db55965

as well?

Quoted 64 lines
Quoted 61 lines · Trevor Woerner
Quoted 58 lines · Khem Raj
Quoted 10 lines

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-linux/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_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"

#8 lore raw
Quoted 5 lines · Khem Raj

Did you take

https://github.com/kraj/meta-raspberrypi/commit/361757b9c1538b0a15577d75308ecef93db55965

as well?

Yes, I'm using the following as of 4735e7cde210b2b0b855bca1eb90ef4adca8019b, which includes 361757b9c1538b0a15577d75308ecef93db55965.

Quoted 16 lines
Quoted 16 lines
Quoted 16 lines
Quoted 16 lines

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"

What's even more odd is commit 361757b9c1538b0a15577d75308ecef93db55965 switched the SRCREV from 6abac13566786086cd912d87e4f1a922e2a391b2 to ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7, but neither of those are found in
git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y (or in that repository at all).

	commit 361757b9c1538b0a15577d75308ecef93db55965
	Author: Khem Raj <[email protected]>
	Date:   Sat Nov 12 11:32:56 2016 -0800

	    linux-raspberrypi-4.8: Update to 4.8.8
	    
	    Signed-off-by: Khem Raj <[email protected]>

	diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
	index 4664249..323b0ea 100644
	--- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
	+++ b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
	@@ -1,8 +1,8 @@
	 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
	 
	-LINUX_VERSION ?= "4.8.6"
	+LINUX_VERSION ?= "4.8.8"
	 
	-SRCREV = "6abac13566786086cd912d87e4f1a922e2a391b2"
	+SRCREV = "ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7"
	 SRC_URI = "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y \
	 "
	 require linux-raspberrypi.inc

I'm currently trying 3ce7378bb505825f492615bd71d19a2339e5bf55, which is the current HEAD of the 4.8.y branch of the raspi kernel repository.

#9 lore raw
Quoted 2 lines · Trevor Woerner

I'm currently trying 3ce7378bb505825f492615bd71d19a2339e5bf55, which is the current HEAD of the 4.8.y branch of the raspi kernel repository.

It builds if I:

	diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
	index 323b0ea..cbb8a50 100644
	--- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
	+++ b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
	@@ -1,8 +1,8 @@
	 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
	 
	-LINUX_VERSION ?= "4.8.8"
	+LINUX_VERSION ?= "4.8.9"
	 
	-SRCREV = "ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7"
	+SRCREV = "3ce7378bb505825f492615bd71d19a2339e5bf55"
	 SRC_URI = "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y \
	 "
	 require linux-raspberrypi.inc

but it doesn't (appear to) boot.

Is there a way to enable the console of the bootloader? I don't get anything on the console (which I do if I load a raspi2 image), and no lights are blinking (which occurs with a raspi2 image).