Re: [yocto] [meta-raspberrypi][morty][PATCH 4/6] linux-raspberrypi: Drop v4.8
On Fri, 20 Jan 2017 10:21:12 -0800 Khem Raj wrote: > On Fri, Jan 20, 2017 at 8:25 AM, Andrei Gherzan > wrote: > > On Fri, Jan 20, 2017 at 6:49 AM, Khem Raj > > wrote: > >> 4.8 will build until rpi kernel folks rebase the branch :( moving > >> forward, we should only keep stable branches which they dont rebase > >> hopefully and 1 more recipe called linux-raspberrypi_dev.bb to > >> track the latest upstream release, so it will be clear that this > >> is a dev kernel. > > > > I like this idea. So you mean having two kernel recipes from now on: > > 1. one current default of ilnux-raspberrypi > > 2. and the latest one as linux-raspberrypi-dev > > ? > > yes. We can have multiple stable kernel recipes if needed but I would > like to avoid that too if possible. This sounds like a great idea. I'd have an overlap period of a month or so when moving to a new stable release to give people time to move over. But after that I'd agree we should just keep a single stable kernel recipe in meta-raspberrypi, unless there's someone in the community heavily invested in the old version and willing to maintain it and update it. What we don't want is releases like 4.1 hanging around long after they've been broken by changes elsewhere. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Changing over to systemd (no dhcp)
Hello Mike, On Fri, Jan 20, 2017 at 3:27 PM, Mike Looijmans wrote: > An no one (except one of the systemd folks) has come up with a program > that just waits for the the processes to finish (with a timeout) and only > uses the "-9" double barrel shotgun to finish only the ones that didn't > respond? > (though doing that is rather pointless if the system power is about to be > cut anyway...) > > What lesser-brain-dead "one of the systemd folks" solution is that? Regards, Leon. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Changing over to systemd (no dhcp)
Hi Colin, On Fri, Jan 20, 2017 at 2:59 PM, wrote: > > DISTRO_FEATURES_remove = " sysvinit" > > I suspect there’s also some de-cluttering needed e.g. init.d scripts still > being installed as well as a .service. > I wouldn't expect these to be installed. Which ones specifically? Regards, Leon. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Override machine conf settings
Hi Khem,
Thanks for the hints but unfortunately I got the following error :
~/Projects/yocto/build$ MACHINE=raspberrypi bitbake -f virtual/kernel
WARNING: Duplicate inclusion for /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf in /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf
WARNING: Duplicate inclusion for /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf in /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf
WARNING: Duplicate inclusion for /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf in /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf
WARNING: Duplicate inclusion for /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf in /home/zak/Projects/yocto/meta-
something/conf/machine/raspberrypi.conf
ERROR: Unable to parse /home/zak/Projects/yocto/bitbake/lib/bb/data_smart.py
Traceback (most recent call last):
File "/home/zak/Projects/yocto/bitbake/lib/bb/data_smart.py", line 400,
in DataSmart.expandWithRefs(s='/home/zak/Projects/yocto/meta-
poky:${TOPDIR}:/home/zak/Projects/yocto/meta:/home/zak/
Projects/yocto/meta-yocto-bsp:/home/zak/Projects/yocto/meta-
yocto-bsp:/home/zak/Projects/yocto/meta-something:/home/
zak/Projects/yocto/meta-raspberrypi:/home/zak/Projects/yocto/meta-openembedded/meta-oe',
varname='BBPATH'):
except Exception as exc:
>raise ExpansionError(varname, s, exc) from exc
bb.data_smart.ExpansionError: Failure expanding variable BBPATH, expression
was /home/zak/Projects/yocto/meta-poky:${TOPDIR}:/home/zak/
Projects/yocto/meta:/home/zak/Projects/yocto/meta-yocto-bsp:
/home/zak/Projects/yocto/meta-yocto-bsp:/home/zak/Projects/
yocto/meta-something:/home/zak/Projects/yocto/meta-raspberrypi:/home/zak/
Projects/yocto/meta-openembedded/meta-oe which triggered exception
RecursionError: maximum recursion depth exceeded while calling a Python
object
2017-01-12 21:39 GMT+01:00 Khem Raj :
> On Thu, Jan 12, 2017 at 10:37 AM, Ayoub Zaki
> wrote:
> > Hello,
> >
> > I'm trying to figure out how can I override machine settings, for
> example in
> > raspberrypi I want to change default kernel version from 4.4.x to 4.1.x
> for
> > that I created in my layer meta-somelayer/conf/machine/raspberrypi.conf
> :
>
> there is a machine config with same name in meta-raspberrypi layer and
> thats taking
> precedence over your layer see conf/layer.conf where it sets the
> PRIORITY and also ensure
> the BBPATHs are prefixed for your layer to be in front of
> meta-raspberrypi layer. So that
> it uses your layer and falls back to meta-raspberrypi to do the filler
> work.
>
>
> >
> > require conf/machine/raspberrypi.conf
> > PREFERRED_VERSION_linux-raspberrypi = "4.1.%"
> >
> >
> > when I ran bitbake it gives:
> >
> > $ MACHINE=raspberrypi bitbake virtual/kernel
> >
> > NOTE: Tainting hash to force rebuild of task
> > /home/zak/Projects/yocto/meta-somelayer/recipes-kernel/linux/
> linux-raspberrypi_4.4.bb,
> > do_compile
> >
> > so it seems that bitbake ignored my override settings !
> >
> > I'm using morty branch and my layer meta-somelayer has higher priority
> than
> > meta-rapberrypi :
> >
> > $ bitbake-layers show-layers
> > layer path priority
> >
> ==
> > meta /home/zak/Projects/yocto/meta5
> > meta-yocto-bsp/home/zak/Projects/yocto/meta-yocto-bsp 5
> > meta-poky /home/zak/Projects/yocto/meta-poky 5
> > meta-yocto-bsp/home/zak/Projects/yocto/meta-yocto-bsp 5
> > meta-raspberrypi /home/zak/Projects/yocto/meta-raspberrypi 9
> > meta-somelayer/home/zak/Projects/yocto/meta-somelayer 5
> >
> >
> > when I tried to override the setting in rpi.conf instead of
> raspberrypi.conf
> > in meta-somelayer/conf/machine/rpi.conf:
> >
> > MACHINEOVERRIDES = "raspberrypi:${MACHINE}"
> > require conf/machine/raspberrypi.conf
> >
> > PREFERRED_VERSION_linux-raspberrypi = "4.1.%"
> >
> > and running bitbake with :
> >
> >
> > $ MACHINE=rpi bitbake virtual/kernel
> > NOTE: Tainting hash to force rebuild of task
> > /home/zak/Projects/yocto/meta-somelayer/recipes-kernel/linux/
> linux-raspberrypi_4.1.bb,
> > do_compile
> >
> > it worked !
> >
> > My objective however is to override the machine settings and keep the
> same
> > MACHINE name.
> >
> > Any Ideas?
> >
> >
> > Regards,
> >
> >
> >
> >
> >
> > --
> > ___
> > 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][morty][PATCH 1/6] linux-raspberrypi: Drop v4.1
On Fri, Jan 20, 2017 at 9:40 AM, Andrei Gherzan wrote:
> On Thu, Jan 19, 2017 at 11:50 AM, Andrei Gherzan wrote:
>> From: Paul Barker
>>
>> The linux-raspberrypi 4.1 recipe has been broken for a while, probably since
>> 09b76a43f6f6852406de385a45f472c52b6a8571. It should now be safe to drop this
>> version.
>>
>> Signed-off-by: Paul Barker
>> ---
>> .../0001-dts-add-overlay-for-pitft22.patch | 110
>> -
>> ...ove-unused-sm_cache_map_vector-definition.patch | 31 --
>> .../linux-raspberrypi-4.1/0003-fix-gcc6.patch | 78 ---
>> recipes-kernel/linux/linux-raspberrypi_4.1.bb | 12 ---
>> 4 files changed, 231 deletions(-)
>> delete mode 100644
>> recipes-kernel/linux/linux-raspberrypi-4.1/0001-dts-add-overlay-for-pitft22.patch
>> delete mode 100644
>> recipes-kernel/linux/linux-raspberrypi-4.1/0002-vmcs-Remove-unused-sm_cache_map_vector-definition.patch
>> delete mode 100644
>> recipes-kernel/linux/linux-raspberrypi-4.1/0003-fix-gcc6.patch
>> delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.1.bb
>>
>> diff --git
>> a/recipes-kernel/linux/linux-raspberrypi-4.1/0001-dts-add-overlay-for-pitft22.patch
>>
>> b/recipes-kernel/linux/linux-raspberrypi-4.1/0001-dts-add-overlay-for-pitft22.patch
>> deleted file mode 100644
>> index e6e0a84..000
>> ---
>> a/recipes-kernel/linux/linux-raspberrypi-4.1/0001-dts-add-overlay-for-pitft22.patch
>> +++ /dev/null
>> @@ -1,110 +0,0 @@
>> -From a28bd410022b32a64e208f04b45add6326990332 Mon Sep 17 00:00:00 2001
>> -From: =?UTF-8?q?Petter=20Mab=C3=A4cker?=
>> -Date: Fri, 8 Jan 2016 09:02:44 +0100
>> -Subject: [PATCH] dts: add overlay for pitft22
>> -MIME-Version: 1.0
>> -Content-Type: text/plain; charset=UTF-8
>> -Content-Transfer-Encoding: 8bit
>> -
>> -Upstream-Status: Pending
>> -
>> -Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
>> -https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
>> -
>> -Signed-off-by: Petter Mabäcker
>>
>> - arch/arm/boot/dts/overlays/Makefile| 1 +
>> - arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69
>> ++
>> - 2 files changed, 70 insertions(+)
>> - create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
>> -
>> -diff --git a/arch/arm/boot/dts/overlays/Makefile
>> b/arch/arm/boot/dts/overlays/Makefile
>> -index 1a60e9c..a2535a2 100644
>> a/arch/arm/boot/dts/overlays/Makefile
>> -+++ b/arch/arm/boot/dts/overlays/Makefile
>> -@@ -37,6 +37,7 @@ dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb
>> - dtb-$(RPI_DT_OVERLAYS) += mz61581-overlay.dtb
>> - dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
>> - dtb-$(RPI_DT_OVERLAYS) += piscreen2r-overlay.dtb
>> -+dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb
>> - dtb-$(RPI_DT_OVERLAYS) += pitft28-capacitive-overlay.dtb
>> - dtb-$(RPI_DT_OVERLAYS) += pitft28-resistive-overlay.dtb
>> - dtb-$(RPI_DT_OVERLAYS) += pps-gpio-overlay.dtb
>> -diff --git a/arch/arm/boot/dts/overlays/pitft22-overlay.dts
>> b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
>> -new file mode 100755
>> -index 000..894ba22
>> /dev/null
>> -+++ b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
>> -@@ -0,0 +1,69 @@
>> -+/*
>> -+ * Device Tree overlay for pitft by Adafruit
>> -+ *
>> -+ */
>> -+
>> -+/dts-v1/;
>> -+/plugin/;
>> -+
>> -+/ {
>> -+compatible = "brcm,bcm2835", "brcm,bcm2708", "brcm,bcm2709";
>> -+
>> -+fragment@0 {
>> -+target = <&spi0>;
>> -+__overlay__ {
>> -+status = "okay";
>> -+
>> -+spidev@0{
>> -+status = "disabled";
>> -+};
>> -+
>> -+spidev@1{
>> -+status = "disabled";
>> -+};
>> -+};
>> -+};
>> -+
>> -+fragment@1 {
>> -+target = <&gpio>;
>> -+__overlay__ {
>> -+pitft_pins: pitft_pins {
>> -+brcm,pins = <25>;
>> -+brcm,function = <1>; /* out */
>> -+brcm,pull = <0>; /* none */
>> -+};
>> -+};
>> -+};
>> -+
>> -+fragment@2 {
>> -+target = <&spi0>;
>> -+__overlay__ {
>> -+/* needed to avoid dtc warning */
>> -+#address-cells = <1>;
>> -+#size-cells = <0>;
>> -+
>> -+pitft: pitft@0{
>> -+compatible = "ilitek,ili9340";
>> -+reg = <0>;
>> -+pinctrl-names = "default";
>> -+pinctrl-0 = <&pitft_pins>;
>> -+
>> -+spi-max-frequency = <3200>;
>> -+rotate = <90>;
>> -+
