[yocto] [meta-raspberrypi][morty][PATCH 1/8] linux-raspberrypi_4.9: Bump to 4.9.21
From: Andrei Gherzan Signed-off-by: Andrei Gherzan --- 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 3aba67b..c0e8b83 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.13" +LINUX_VERSION ?= "4.9.21" -SRCREV = "28ea32b9afb5d813986c4ab940c26fe298d80ed2" +SRCREV = "5e4ee836560d4c0371e109bf469e1ad808ae7a44" SRC_URI = "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \ " require linux-raspberrypi.inc -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 5/8] raspberrypi3-64.conf: Specifiy rpi3-64bit dtbs
From: Khem Raj Signed-off-by: Khem Raj --- conf/machine/raspberrypi3-64.conf | 23 +++ 1 file changed, 23 insertions(+) diff --git a/conf/machine/raspberrypi3-64.conf b/conf/machine/raspberrypi3-64.conf index cdcd726..e7d9af2 100644 --- a/conf/machine/raspberrypi3-64.conf +++ b/conf/machine/raspberrypi3-64.conf @@ -9,6 +9,29 @@ MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430" require conf/machine/include/arm/arch-armv8.inc include conf/machine/include/rpi-base.inc +KERNEL_DEVICETREE = " \ +broadcom/bcm2710-rpi-3-b.dtb \ +broadcom/bcm2837-rpi-3-b.dtb \ +\ +overlays/hifiberry-amp.dtbo \ +overlays/hifiberry-dac.dtbo \ +overlays/hifiberry-dacplus.dtbo \ +overlays/hifiberry-digi.dtbo \ +overlays/i2c-rtc.dtbo \ +overlays/iqaudio-dac.dtbo \ +overlays/iqaudio-dacplus.dtbo \ +overlays/lirc-rpi.dtbo \ +overlays/pitft22.dtbo \ +overlays/pitft28-resistive.dtbo \ +overlays/pps-gpio.dtbo \ +overlays/rpi-ft5406.dtbo \ +overlays/w1-gpio.dtbo \ +overlays/w1-gpio-pullup.dtbo \ +overlays/pi3-disable-bt.dtbo \ +overlays/pi3-miniuart-bt.dtbo \ +overlays/vc4-kms-v3d.dtbo \ +" + SERIAL_CONSOLE = "115200 ttyS0" VC4_CMA_SIZE ?= "cma-256" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 3/8] Add raspberrypi3-64.conf
From: Herve Jourdain Signed-off-by: Herve Jourdain Signed-off-by: Khem Raj --- conf/machine/raspberrypi3-64.conf | 15 +++ 1 file changed, 15 insertions(+) create mode 100644 conf/machine/raspberrypi3-64.conf diff --git a/conf/machine/raspberrypi3-64.conf b/conf/machine/raspberrypi3-64.conf new file mode 100644 index 000..5598e50 --- /dev/null +++ b/conf/machine/raspberrypi3-64.conf @@ -0,0 +1,15 @@ +#@TYPE: Machine +#@NAME: RaspberryPi 3 Development Board +#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64 bits mode + +MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}" + +MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430" + +require conf/machine/include/arm/arch-armv8.inc +include conf/machine/include/rpi-base.inc + +SERIAL_CONSOLE = "115200 ttyS0" +VC4_CMA_SIZE ?= "cma-256" + +UBOOT_MACHINE = "rpi_3_config" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 2/8] linux-raspberrypi: Add defconfig for raspberrypi3-64
From: Khem Raj Signed-off-by: Khem Raj --- recipes-kernel/linux/linux-raspberrypi.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-kernel/linux/linux-raspberrypi.inc b/recipes-kernel/linux/linux-raspberrypi.inc index 98229d9..d196d8e 100644 --- a/recipes-kernel/linux/linux-raspberrypi.inc +++ b/recipes-kernel/linux/linux-raspberrypi.inc @@ -18,6 +18,7 @@ PV = "${LINUX_VERSION}+git${SRCPV}" # NOTE: For now we pull in the default config from the RPi kernel GIT tree. KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig" KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig" +KERNEL_DEFCONFIG_raspberrypi3-64 ?= "bcmrpi3_defconfig" # CMDLINE for raspberrypi CMDLINE = "dwc_otg.lpm_enable=0 console=serial0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 8/8] rpi-config: Specify bcm2710-rpi-3-b dtb for 64bit rpi3
From: Khem Raj Let config.txt explicitly specify it Signed-off-by: Khem Raj --- recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++ 1 file changed, 6 insertions(+) diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb b/recipes-bsp/bootfiles/rpi-config_git.bb index f610718..20ec343 100644 --- a/recipes-bsp/bootfiles/rpi-config_git.bb +++ b/recipes-bsp/bootfiles/rpi-config_git.bb @@ -112,6 +112,12 @@ do_deploy() { fi } +do_deploy_append_raspberrypi3-64() { +# Device Tree support +echo "# Load correct Device Tree for Aarch64" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt +echo "device_tree=bcm2710-rpi-3-b.dtb" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt +} + addtask deploy before do_package after do_install do_deploy[dirs] += "${DEPLOYDIR}/bcm2835-bootfiles" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 7/8] sdcard: Use kernel8.img for 64bit kernel image name
From: Khem Raj This helps the firmware to identify the kernel as 64bit image Signed-off-by: Khem Raj --- classes/sdcard_image-rpi.bbclass | 1 + 1 file changed, 1 insertion(+) diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass index 116d5e8..79ab53a 100644 --- a/classes/sdcard_image-rpi.bbclass +++ b/classes/sdcard_image-rpi.bbclass @@ -35,6 +35,7 @@ KERNEL_INITRAMFS ?= "" # Kernel image name SDIMG_KERNELIMAGE_raspberrypi ?= "kernel.img" SDIMG_KERNELIMAGE_raspberrypi2 ?= "kernel7.img" +SDIMG_KERNELIMAGE_raspberrypi3-64 ?= "kernel8.img" # Boot partition volume id BOOTDD_VOLUME_ID ?= "${MACHINE}" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 4/8] raspberrypi3-64.conf: Use 4.9 as default kernel
From: Khem Raj Signed-off-by: Khem Raj --- conf/machine/raspberrypi3-64.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/machine/raspberrypi3-64.conf b/conf/machine/raspberrypi3-64.conf index 5598e50..cdcd726 100644 --- a/conf/machine/raspberrypi3-64.conf +++ b/conf/machine/raspberrypi3-64.conf @@ -13,3 +13,5 @@ SERIAL_CONSOLE = "115200 ttyS0" VC4_CMA_SIZE ?= "cma-256" UBOOT_MACHINE = "rpi_3_config" + +PREFERRED_VERSION_linux-raspberrypi ?= "4.9.%" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 0/8] Stable branch backports
* Upgrade linux-raspberrypi 4.9 recipe * Add support for raspberrypi3-64 MACHINE Boot tested on raspberrypi, raspberrypi3 and raspberrypi3-64 using the 4.9 series kernel. These patches were tested on top of Andrei's latest series of backports. The exact series tested can be found at: https://gitlab.com/oryx/meta-raspberrypi/commits/pbarker/morty-next-2017-04-18 Andrei Gherzan (1): linux-raspberrypi_4.9: Bump to 4.9.21 Herve Jourdain (1): Add raspberrypi3-64.conf Khem Raj (5): linux-raspberrypi: Add defconfig for raspberrypi3-64 raspberrypi3-64.conf: Use 4.9 as default kernel raspberrypi3-64.conf: Specifiy rpi3-64bit dtbs sdcard: Use kernel8.img for 64bit kernel image name rpi-config: Specify bcm2710-rpi-3-b dtb for 64bit rpi3 Paul Barker (1): raspberrypi3-64: Override rpi-default-versions.inc classes/sdcard_image-rpi.bbclass | 1 + conf/machine/raspberrypi3-64.conf | 41 +++ recipes-bsp/bootfiles/rpi-config_git.bb | 6 recipes-kernel/linux/linux-raspberrypi.inc| 1 + recipes-kernel/linux/linux-raspberrypi_4.9.bb | 4 +-- 5 files changed, 51 insertions(+), 2 deletions(-) create mode 100644 conf/machine/raspberrypi3-64.conf -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 6/8] raspberrypi3-64: Override rpi-default-versions.inc
Signed-off-by: Paul Barker --- conf/machine/raspberrypi3-64.conf | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/conf/machine/raspberrypi3-64.conf b/conf/machine/raspberrypi3-64.conf index e7d9af2..7e99da1 100644 --- a/conf/machine/raspberrypi3-64.conf +++ b/conf/machine/raspberrypi3-64.conf @@ -6,6 +6,9 @@ MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}" MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430" +# Set this early so it overrides rpi-default-versions.inc +PREFERRED_VERSION_linux-raspberrypi ?= "4.9.%" + require conf/machine/include/arm/arch-armv8.inc include conf/machine/include/rpi-base.inc @@ -36,5 +39,3 @@ SERIAL_CONSOLE = "115200 ttyS0" VC4_CMA_SIZE ?= "cma-256" UBOOT_MACHINE = "rpi_3_config" - -PREFERRED_VERSION_linux-raspberrypi ?= "4.9.%" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Task dependencies
Hi, On 2017-04-13 11:24, Gary Thomas wrote: On 2017-04-13 09:34, Gary Thomas wrote: I'm trying to understand why 'perl' is being built for my target even though I don't mention it in any of the package recipes used to build that target. When I used 'taskexp', I found that 'perl:do_build' only has a single dependent task, namely 'my-image:do_build' note: no perl packages end up in my image. This is just one example where it seems bitbake is doing a lot of unnecessary (certainly un-asked-for) work. How can I unravel this mystery? Thanks for any pointers Did you have a look at the dependency explorer? bitbake -g -u depexp core-image-sato-sdk There you see also reverse dependencies (who depends e.g. on perl) Regards, Robert -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/3] udev: Create rules file to generate serial0/1
On Tue, Apr 18, 2017 at 11:13 AM, Andrei Gherzan wrote: > Signed-off-by: Andrei Gherzan > --- > recipes-core/udev/udev-rules-rpi.bb | 12 > recipes-core/udev/udev-rules-rpi/99-com.rules | 21 perhaps a bbappend to udev-extraconf recipe is better ? + > 2 files changed, 33 insertions(+) > create mode 100644 recipes-core/udev/udev-rules-rpi.bb > create mode 100644 recipes-core/udev/udev-rules-rpi/99-com.rules > > diff --git a/recipes-core/udev/udev-rules-rpi.bb > b/recipes-core/udev/udev-rules-rpi.bb > new file mode 100644 > index 000..20443d3 > --- /dev/null > +++ b/recipes-core/udev/udev-rules-rpi.bb > @@ -0,0 +1,12 @@ > +DESCRIPTION = "udev rules for Raspberry Pi Boards" > +LICENSE = "MIT" > +LIC_FILES_CHKSUM = > "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" > + > +SRC_URI = " file://99-com.rules" > + > +S = "${WORKDIR}" > + > +do_install () { > +install -d ${D}${sysconfdir}/udev/rules.d > +install -m 0644 ${WORKDIR}/99-com.rules ${D}${sysconfdir}/udev/rules.d/ > +} > diff --git a/recipes-core/udev/udev-rules-rpi/99-com.rules > b/recipes-core/udev/udev-rules-rpi/99-com.rules > new file mode 100644 > index 000..6bf019b > --- /dev/null > +++ b/recipes-core/udev/udev-rules-rpi/99-com.rules > @@ -0,0 +1,21 @@ > +KERNEL=="ttyAMA[01]", PROGRAM="/bin/sh -c '\ > + ALIASES=/proc/device-tree/aliases; \ > + if cmp -s $ALIASES/uart0 $ALIASES/serial0; then \ > + echo 0;\ > + elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then \ > + echo 1; \ > + else \ > + exit 1; \ > + fi\ > +'", SYMLINK+="serial%c" > + > +KERNEL=="ttyS0", PROGRAM="/bin/sh -c '\ > + ALIASES=/proc/device-tree/aliases; \ > + if cmp -s $ALIASES/uart1 $ALIASES/serial0; then \ > + echo 0; \ > + elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then \ > + echo 1; \ > + else \ > + exit 1; \ > + fi \ > +'", SYMLINK+="serial%c" > -- > 2.12.2 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 4/7] linux-raspberrypi_4.9: Bump to 4.9.21
On Tue, Apr 18, 2017 at 7:11 PM, Paul Barker wrote: > On Tue, Apr 18, 2017 at 7:07 PM, Andrei Gherzan wrote: >> On Tue, Apr 18, 2017 at 6:23 PM, Paul Barker wrote: >>> >>> I'll have a go at backporting the addition of the extra machines. I >>> can test raspberrypi3-64 on hardware myself but I don't have a >>> raspberrypi0-wifi to test on. >> >> I already pushed a PR for rpi0 wifi for morty and I'm testing it now. > > I must have missed that. Still getting used to switching email systems! > > It looks like you've got rpi0 wifi and firmware upgrades. I'll send > patches for the kernel upgrade and rpi3 64 once I've given them a > spin. Probably late tonight or early tomorrow. > Sounds good. I added some more tweaks now for morty. Let's see if I get some feedback until tomorrow. Otherwise I"ll merge them. -- Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 3/3] raspberrypi*.conf: Be able to overwrite SERIAL_CONSOLE
Signed-off-by: Andrei Gherzan --- conf/machine/raspberrypi.conf | 2 +- conf/machine/raspberrypi0-wifi.conf | 2 +- conf/machine/raspberrypi0.conf | 2 +- conf/machine/raspberrypi2.conf | 2 +- conf/machine/raspberrypi3.conf | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/conf/machine/raspberrypi.conf b/conf/machine/raspberrypi.conf index ad3b061..ddd3801 100644 --- a/conf/machine/raspberrypi.conf +++ b/conf/machine/raspberrypi.conf @@ -7,7 +7,7 @@ DEFAULTTUNE ?= "arm1176jzfshf" require conf/machine/include/tune-arm1176jzf-s.inc include conf/machine/include/rpi-base.inc -SERIAL_CONSOLE = "115200 ttyAMA0" +SERIAL_CONSOLE ?= "115200 ttyAMA0" UBOOT_MACHINE = "rpi_config" VC4_CMA_SIZE_raspberrypi ?= "cma-64" diff --git a/conf/machine/raspberrypi0-wifi.conf b/conf/machine/raspberrypi0-wifi.conf index 2b7cea4..41be06b 100644 --- a/conf/machine/raspberrypi0-wifi.conf +++ b/conf/machine/raspberrypi0-wifi.conf @@ -7,5 +7,5 @@ include conf/machine/raspberrypi.conf MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430" -SERIAL_CONSOLE = "115200 ttyS0" +SERIAL_CONSOLE ?= "115200 ttyS0" VC4_CMA_SIZE ?= "cma-128" diff --git a/conf/machine/raspberrypi0.conf b/conf/machine/raspberrypi0.conf index 7c2b811..3bd9e95 100644 --- a/conf/machine/raspberrypi0.conf +++ b/conf/machine/raspberrypi0.conf @@ -5,5 +5,5 @@ MACHINEOVERRIDES = "raspberrypi:${MACHINE}" include conf/machine/raspberrypi.conf -SERIAL_CONSOLE = "115200 ttyAMA0" +SERIAL_CONSOLE ?= "115200 ttyAMA0" VC4_CMA_SIZE ?= "cma-128" diff --git a/conf/machine/raspberrypi2.conf b/conf/machine/raspberrypi2.conf index 9b4c02a..a17289c 100644 --- a/conf/machine/raspberrypi2.conf +++ b/conf/machine/raspberrypi2.conf @@ -7,7 +7,7 @@ DEFAULTTUNE ?= "cortexa7thf-neon-vfpv4" require conf/machine/include/tune-cortexa7.inc include conf/machine/include/rpi-base.inc -SERIAL_CONSOLE = "115200 ttyAMA0" +SERIAL_CONSOLE ?= "115200 ttyAMA0" UBOOT_MACHINE = "rpi_2_config" VC4_CMA_SIZE ?= "cma-256" diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf index 1ac5928..b15621d 100644 --- a/conf/machine/raspberrypi3.conf +++ b/conf/machine/raspberrypi3.conf @@ -7,5 +7,5 @@ include conf/machine/raspberrypi2.conf MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430" -SERIAL_CONSOLE = "115200 ttyS0" +SERIAL_CONSOLE ?= "115200 ttyS0" VC4_CMA_SIZE ?= "cma-256" -- 2.12.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 2/3] rpi-base.inc: Recommend udev-rules-rpi
Signed-off-by: Andrei Gherzan --- conf/machine/include/rpi-base.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc index dc98099..50eebb4 100644 --- a/conf/machine/include/rpi-base.inc +++ b/conf/machine/include/rpi-base.inc @@ -57,3 +57,6 @@ IMAGE_BOOT_FILES ?= "bcm2835-bootfiles/* ${KERNEL_IMAGETYPE};${SDIMG_KERNELIMAGE # The kernel image is installed into the FAT32 boot partition and does not need # to also be installed into the rootfs. RDEPENDS_kernel-base = "" + +# Extra udev rules +MACHINE_EXTRA_RRECOMMENDS += "udev-rules-rpi" -- 2.12.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][morty][PATCH 1/3] udev: Create rules file to generate serial0/1
Signed-off-by: Andrei Gherzan --- recipes-core/udev/udev-rules-rpi.bb | 12 recipes-core/udev/udev-rules-rpi/99-com.rules | 21 + 2 files changed, 33 insertions(+) create mode 100644 recipes-core/udev/udev-rules-rpi.bb create mode 100644 recipes-core/udev/udev-rules-rpi/99-com.rules diff --git a/recipes-core/udev/udev-rules-rpi.bb b/recipes-core/udev/udev-rules-rpi.bb new file mode 100644 index 000..20443d3 --- /dev/null +++ b/recipes-core/udev/udev-rules-rpi.bb @@ -0,0 +1,12 @@ +DESCRIPTION = "udev rules for Raspberry Pi Boards" +LICENSE = "MIT" +LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" + +SRC_URI = " file://99-com.rules" + +S = "${WORKDIR}" + +do_install () { +install -d ${D}${sysconfdir}/udev/rules.d +install -m 0644 ${WORKDIR}/99-com.rules ${D}${sysconfdir}/udev/rules.d/ +} diff --git a/recipes-core/udev/udev-rules-rpi/99-com.rules b/recipes-core/udev/udev-rules-rpi/99-com.rules new file mode 100644 index 000..6bf019b --- /dev/null +++ b/recipes-core/udev/udev-rules-rpi/99-com.rules @@ -0,0 +1,21 @@ +KERNEL=="ttyAMA[01]", PROGRAM="/bin/sh -c '\ + ALIASES=/proc/device-tree/aliases; \ + if cmp -s $ALIASES/uart0 $ALIASES/serial0; then \ + echo 0;\ + elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then \ + echo 1; \ + else \ + exit 1; \ + fi\ +'", SYMLINK+="serial%c" + +KERNEL=="ttyS0", PROGRAM="/bin/sh -c '\ + ALIASES=/proc/device-tree/aliases; \ + if cmp -s $ALIASES/uart1 $ALIASES/serial0; then \ + echo 0; \ + elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then \ + echo 1; \ + else \ + exit 1; \ + fi \ +'", SYMLINK+="serial%c" -- 2.12.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 3/3] raspberrypi*.conf: Be able to overwrite SERIAL_CONSOLE
Signed-off-by: Andrei Gherzan --- conf/machine/raspberrypi.conf | 2 +- conf/machine/raspberrypi0-wifi.conf | 2 +- conf/machine/raspberrypi0.conf | 2 +- conf/machine/raspberrypi2.conf | 2 +- conf/machine/raspberrypi3.conf | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/conf/machine/raspberrypi.conf b/conf/machine/raspberrypi.conf index ad3b061..ddd3801 100644 --- a/conf/machine/raspberrypi.conf +++ b/conf/machine/raspberrypi.conf @@ -7,7 +7,7 @@ DEFAULTTUNE ?= "arm1176jzfshf" require conf/machine/include/tune-arm1176jzf-s.inc include conf/machine/include/rpi-base.inc -SERIAL_CONSOLE = "115200 ttyAMA0" +SERIAL_CONSOLE ?= "115200 ttyAMA0" UBOOT_MACHINE = "rpi_config" VC4_CMA_SIZE_raspberrypi ?= "cma-64" diff --git a/conf/machine/raspberrypi0-wifi.conf b/conf/machine/raspberrypi0-wifi.conf index 2b7cea4..41be06b 100644 --- a/conf/machine/raspberrypi0-wifi.conf +++ b/conf/machine/raspberrypi0-wifi.conf @@ -7,5 +7,5 @@ include conf/machine/raspberrypi.conf MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430" -SERIAL_CONSOLE = "115200 ttyS0" +SERIAL_CONSOLE ?= "115200 ttyS0" VC4_CMA_SIZE ?= "cma-128" diff --git a/conf/machine/raspberrypi0.conf b/conf/machine/raspberrypi0.conf index 7c2b811..3bd9e95 100644 --- a/conf/machine/raspberrypi0.conf +++ b/conf/machine/raspberrypi0.conf @@ -5,5 +5,5 @@ MACHINEOVERRIDES = "raspberrypi:${MACHINE}" include conf/machine/raspberrypi.conf -SERIAL_CONSOLE = "115200 ttyAMA0" +SERIAL_CONSOLE ?= "115200 ttyAMA0" VC4_CMA_SIZE ?= "cma-128" diff --git a/conf/machine/raspberrypi2.conf b/conf/machine/raspberrypi2.conf index 9b4c02a..a17289c 100644 --- a/conf/machine/raspberrypi2.conf +++ b/conf/machine/raspberrypi2.conf @@ -7,7 +7,7 @@ DEFAULTTUNE ?= "cortexa7thf-neon-vfpv4" require conf/machine/include/tune-cortexa7.inc include conf/machine/include/rpi-base.inc -SERIAL_CONSOLE = "115200 ttyAMA0" +SERIAL_CONSOLE ?= "115200 ttyAMA0" UBOOT_MACHINE = "rpi_2_config" VC4_CMA_SIZE ?= "cma-256" diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf index 1ac5928..b15621d 100644 --- a/conf/machine/raspberrypi3.conf +++ b/conf/machine/raspberrypi3.conf @@ -7,5 +7,5 @@ include conf/machine/raspberrypi2.conf MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430" -SERIAL_CONSOLE = "115200 ttyS0" +SERIAL_CONSOLE ?= "115200 ttyS0" VC4_CMA_SIZE ?= "cma-256" -- 2.12.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 2/3] rpi-base.inc: Recommend udev-rules-rpi
Signed-off-by: Andrei Gherzan --- conf/machine/include/rpi-base.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc index dc98099..50eebb4 100644 --- a/conf/machine/include/rpi-base.inc +++ b/conf/machine/include/rpi-base.inc @@ -57,3 +57,6 @@ IMAGE_BOOT_FILES ?= "bcm2835-bootfiles/* ${KERNEL_IMAGETYPE};${SDIMG_KERNELIMAGE # The kernel image is installed into the FAT32 boot partition and does not need # to also be installed into the rootfs. RDEPENDS_kernel-base = "" + +# Extra udev rules +MACHINE_EXTRA_RRECOMMENDS += "udev-rules-rpi" -- 2.12.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 1/3] udev: Create rules file to generate serial0/1
Signed-off-by: Andrei Gherzan --- recipes-core/udev/udev-rules-rpi.bb | 12 recipes-core/udev/udev-rules-rpi/99-com.rules | 21 + 2 files changed, 33 insertions(+) create mode 100644 recipes-core/udev/udev-rules-rpi.bb create mode 100644 recipes-core/udev/udev-rules-rpi/99-com.rules diff --git a/recipes-core/udev/udev-rules-rpi.bb b/recipes-core/udev/udev-rules-rpi.bb new file mode 100644 index 000..20443d3 --- /dev/null +++ b/recipes-core/udev/udev-rules-rpi.bb @@ -0,0 +1,12 @@ +DESCRIPTION = "udev rules for Raspberry Pi Boards" +LICENSE = "MIT" +LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" + +SRC_URI = " file://99-com.rules" + +S = "${WORKDIR}" + +do_install () { +install -d ${D}${sysconfdir}/udev/rules.d +install -m 0644 ${WORKDIR}/99-com.rules ${D}${sysconfdir}/udev/rules.d/ +} diff --git a/recipes-core/udev/udev-rules-rpi/99-com.rules b/recipes-core/udev/udev-rules-rpi/99-com.rules new file mode 100644 index 000..6bf019b --- /dev/null +++ b/recipes-core/udev/udev-rules-rpi/99-com.rules @@ -0,0 +1,21 @@ +KERNEL=="ttyAMA[01]", PROGRAM="/bin/sh -c '\ + ALIASES=/proc/device-tree/aliases; \ + if cmp -s $ALIASES/uart0 $ALIASES/serial0; then \ + echo 0;\ + elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then \ + echo 1; \ + else \ + exit 1; \ + fi\ +'", SYMLINK+="serial%c" + +KERNEL=="ttyS0", PROGRAM="/bin/sh -c '\ + ALIASES=/proc/device-tree/aliases; \ + if cmp -s $ALIASES/uart1 $ALIASES/serial0; then \ + echo 0; \ + elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then \ + echo 1; \ + else \ + exit 1; \ + fi \ +'", SYMLINK+="serial%c" -- 2.12.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 4/7] linux-raspberrypi_4.9: Bump to 4.9.21
On Tue, Apr 18, 2017 at 7:07 PM, Andrei Gherzan wrote: > On Tue, Apr 18, 2017 at 6:23 PM, Paul Barker wrote: >> >> I'll have a go at backporting the addition of the extra machines. I >> can test raspberrypi3-64 on hardware myself but I don't have a >> raspberrypi0-wifi to test on. > > I already pushed a PR for rpi0 wifi for morty and I'm testing it now. I must have missed that. Still getting used to switching email systems! It looks like you've got rpi0 wifi and firmware upgrades. I'll send patches for the kernel upgrade and rpi3 64 once I've given them a spin. Probably late tonight or early tomorrow. Cheers, -- Paul Barker Co-Founder & Principal Engineer Togán Labs Ltd -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 4/7] linux-raspberrypi_4.9: Bump to 4.9.21
On Tue, Apr 18, 2017 at 6:23 PM, Paul Barker wrote: > On Tue, Apr 18, 2017 at 1:58 PM, Andrei Gherzan wrote: >> On Tue, Apr 18, 2017 at 12:10:47PM +0100, Paul Barker wrote: >>> On Fri, Apr 14, 2017 at 9:13 PM, Andrei Gherzan wrote: >>> > >>> > -LINUX_VERSION ?= "4.9.13" >>> > +LINUX_VERSION ?= "4.9.21" >>> > >>> > >>> >>> I'm going to backport this to morty and test this week. Any other >>> patches worth testing for morty at the same time? >>> >> >> I would probably want to have 64b rpi3 too in morty. And yes, 4.9 >> defaulted for kernel? >> > > I'd support adding extra machines if we can (raspberrypi0-wifi and > raspberrypi3-64) and having those use Linux 4.9. However, I'd be > reticent to change the default kernel version for existing machines on > a stable branch. I agree. > > I'll have a go at backporting the addition of the extra machines. I > can test raspberrypi3-64 on hardware myself but I don't have a > raspberrypi0-wifi to test on. I already pushed a PR for rpi0 wifi for morty and I'm testing it now. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 4/7] linux-raspberrypi_4.9: Bump to 4.9.21
On Tue, Apr 18, 2017 at 1:58 PM, Andrei Gherzan wrote: > On Tue, Apr 18, 2017 at 12:10:47PM +0100, Paul Barker wrote: >> On Fri, Apr 14, 2017 at 9:13 PM, Andrei Gherzan wrote: >> > >> > -LINUX_VERSION ?= "4.9.13" >> > +LINUX_VERSION ?= "4.9.21" >> > >> > >> >> I'm going to backport this to morty and test this week. Any other >> patches worth testing for morty at the same time? >> > > I would probably want to have 64b rpi3 too in morty. And yes, 4.9 > defaulted for kernel? > I'd support adding extra machines if we can (raspberrypi0-wifi and raspberrypi3-64) and having those use Linux 4.9. However, I'd be reticent to change the default kernel version for existing machines on a stable branch. I'll have a go at backporting the addition of the extra machines. I can test raspberrypi3-64 on hardware myself but I don't have a raspberrypi0-wifi to test on. Cheers, Paul -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Status WW16’17
Current Dev Position: YP 2.3 M4 Next Deadline: YP 2.3 M4 Cutoff is April 10, 2017 *** FEATURE FREEZE for 2.3 is now in effect. *** SWAT team rotation: Cal -> Joshua on April 14, 2017. SWAT team rotation: Joshua -> Armin on April 21, 2017. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: ·YP 2.3 M3 rc2 was released last Friday. ·2.3 M4 rc1 has not been built yet but the build is imminent. There are a handful of bugs we’re hoping to resolve before the build happens and those are actively being worked. ·Thanks to everyone who has helped sort out the remaining issues we had in M4. We were able to resolve the problems with the build and unblock patch merging. There were some key fixes such as the useradd and runqemu ones. ·Since we’re well into the stabilization phase of 2.3, planning for 2.4 has begun and we’re entering 2.4 ideas and enhancements in to bugzilla. If you have suggestions for 2.4, please ensure they are in bugzilla. Proposed upcoming dot releases: YP 2.1.3 Cut off May 15, 2017 YP 2.1.3 Release by May 26, 2017 YP 2.2.2 Cut off May 29, 2017 YP 2.2.2 Release by June 9, 2017 Key YP 2.3 Dates: YP 2.3 M3 Release is Mar. 10, 2017 (Will be a few weeks late.) YP 2.3 M4 Cutoff is April 10, 2017 YP 2.3 M4 Release is May 5, 2017 Tracking Metrics: WDD 2561 (last week 2678) (https://wiki.yoctoproject.org/charts/combo.html) Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 • Work Telephone:(503) 712-0534 •Cell: (208) 244-4460 • Email:stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] OPKG package management issue
Hi Abhishek, Can you please create this directory and see if opkg will work after that? Thanks, Ulf From: on behalf of Abhishekh Awanti Date: Tuesday, April 18, 2017 at 4:15 AM To: "yocto@yoctoproject.org" Subject: [yocto] OPKG package management issue Hi, I am trying to install .ipk with opkg in yocto. If i run below command opkg install *.ipk I am getting the below error:- Collected errors: * opkg_conf_load: Could not create lock file /var/lib/opkg/lock: No such file or directory. I did some research and followed this link http://wiki.hioproject.org/index.php?title=Yocto:_Opkg_Package_Management_System_Set_Up I came to know that one should add in the conf/local.conf EXTRA_IMAGE_FEATURES = "package-management" IMAGE_INSTALL_append = " opkg " PACKAGE_CLASSES = "package_ipk" Even though i am getting the same error. "/var/lib/opkg/" is existed in my image build directory, but after installing the image to the target device the "/var/lib/opkg/" is not appearing. I am guessing that, the disappearance of the /var/lib/opkg folder may be causing the opkg error. Can anybody please help me on this problem. Thank you, Abhishek -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 4/7] linux-raspberrypi_4.9: Bump to 4.9.21
On Tue, Apr 18, 2017 at 12:10:47PM +0100, Paul Barker wrote: > On Fri, Apr 14, 2017 at 9:13 PM, Andrei Gherzan wrote: > > Signed-off-by: Andrei Gherzan > > --- > > 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 3aba67b..c0e8b83 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.13" > > +LINUX_VERSION ?= "4.9.21" > > > > -SRCREV = "28ea32b9afb5d813986c4ab940c26fe298d80ed2" > > +SRCREV = "5e4ee836560d4c0371e109bf469e1ad808ae7a44" > > SRC_URI = > > "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \ > > " > > require linux-raspberrypi.inc > > -- > > 2.12.1 > > > > I'm going to backport this to morty and test this week. Any other > patches worth testing for morty at the same time? > > Cheers, > Paul I would probably want to have 64b rpi3 too in morty. And yes, 4.9 defaulted for kernel? -- Andrei Gherzan gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto cups serial port support
Hello, I checked /usr/lib/cups/backend not inclued "serial" backend. How can enable cups serial port ? Thanks. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Noobie questions
On 17/04/2017 13:59, Gary Thomas wrote: (...) Probably best to use morty which is the upcoming 2.3 release Morty is the current 2.2 release. I would say it is the best starting point to get experience with Yocto. New developments might use master or start with Morty and migrate to 2.3 when it comes out. Bas. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] OPKG package management issue
Hi, I am trying to install *.ipk* with *opkg* in yocto. If i run below command *opkg install *.ipk* I am getting the below error:- * Collected errors: * opkg_conf_load: Could not create lock file /var/lib/opkg/lock: No such file or directory.* I did some research and followed this link http://wiki.hioproject.org/index.php?title=Yocto:_Opkg_Package_Management_System_Set_Up I came to know that one should add in the *conf/local.conf* *EXTRA_IMAGE_FEATURES = "package-management"* > > *IMAGE_INSTALL_append = " opkg "* > > *PACKAGE_CLASSES = "package_ipk"* > Even though i am getting the same error. *"/var/lib/opkg/"* is existed in my image build directory, but after installing the image to the target device the *"/var/lib/opkg/"* is not appearing. I am guessing that, the disappearance of the */var/lib/opkg* folder may be causing the opkg error. Can anybody please help me on this problem. Thank you, Abhishek -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 4/7] linux-raspberrypi_4.9: Bump to 4.9.21
On Fri, Apr 14, 2017 at 9:13 PM, Andrei Gherzan wrote: > Signed-off-by: Andrei Gherzan > --- > 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 3aba67b..c0e8b83 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.13" > +LINUX_VERSION ?= "4.9.21" > > -SRCREV = "28ea32b9afb5d813986c4ab940c26fe298d80ed2" > +SRCREV = "5e4ee836560d4c0371e109bf469e1ad808ae7a44" > SRC_URI = > "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \ > " > require linux-raspberrypi.inc > -- > 2.12.1 > I'm going to backport this to morty and test this week. Any other patches worth testing for morty at the same time? Cheers, Paul -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] package.bbclass: Changed PACKAGESPLITFUNCS execution order
Fixes [YOCTO #11343] I've added runtime PACKAGESPLITFUNCS value modification in the context of do_package() function so that populate_packages_updatealternatives function is allways executed before populate_packages_updatercd Signed-off-by: Oleksandr Poznyak --- meta/classes/package.bbclass | 5 + 1 file changed, 5 insertions(+) diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass index cc466bd..149a185 100644 --- a/meta/classes/package.bbclass +++ b/meta/classes/package.bbclass @@ -2110,6 +2110,11 @@ python do_package () { cpath = oe.cachedpath.CachedPath() +# modify PACKAGESPLITFUNCS order +if "populate_packages_updatealternatives" in d.getVar("PACKAGESPLITFUNCS", True): +d.setVar("PACKAGESPLITFUNCS", "populate_packages_updatealternatives %s" \ +% d.getVar("PACKAGESPLITFUNCS", True).replace("populate_packages_updatealternatives", "")) + for f in (d.getVar('PACKAGESPLITFUNCS') or '').split(): bb.build.exec_func(f, d) -- 2.1.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux
Ping. > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of jackie.hu...@windriver.com > Sent: Wednesday, February 22, 2017 14:45 > To: yocto@yoctoproject.org > Subject: [yocto] [meta-selinux][PATCH] systemd: no need to inherit enable- > selinux > > From: Jackie Huang > > The selinux PACKAGECONFIG is properly handled in > the recipe in oe-core, no need to inherit the > enable-selinux bbclass. > > Signed-off-by: Jackie Huang > --- > recipes-core/systemd/systemd_%.bbappend | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/recipes-core/systemd/systemd_%.bbappend b/recipes- > core/systemd/systemd_%.bbappend > index 8d9029b..f1bdaf8 100644 > --- a/recipes-core/systemd/systemd_%.bbappend > +++ b/recipes-core/systemd/systemd_%.bbappend > @@ -1,2 +1 @@ > inherit enable-audit > -inherit enable-selinux > -- > 2.8.3 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto