Re: [yocto] Unusual RPM / Smart Bug When Changing Architecture
On Wed, 2016-11-16 at 11:35 -0800, Darcy Watkins wrote: > > Is this a known issue? Has it been fixed in a newer branch? If so, > which one? I can only say that I've encountered this (when using IPK), too. It doesn't seem to be related to RPM specifically, unless opkg and rpm just happen to implement similar semantics. It seems something always prefers the more specific package rather than the newer version. Cheers, Andre' -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-swupd][PATCH] bsdiff: update to latest version
From: André Draszik
This allows us to completely remove the build time
depenency on libcheck when not needed, reducing
overall build time, and in addition tests can be
converted into a PACKAGECONFIG to enable them if
needed.
Signed-off-by: André Draszik
---
recipes-devtools/bsdiff/bsdiff_git.bb | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/recipes-devtools/bsdiff/bsdiff_git.bb
b/recipes-devtools/bsdiff/bsdiff_git.bb
index 8eb7271..ca0c4c8 100644
--- a/recipes-devtools/bsdiff/bsdiff_git.bb
+++ b/recipes-devtools/bsdiff/bsdiff_git.bb
@@ -6,14 +6,15 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=0dbe7a50f028269750631fcbded3846a"
SRC_URI = "git://github.com/clearlinux/bsdiff.git;protocol=https"
PV = "1.0.1+git${SRCPV}"
-SRCREV = "8c0a87b7c9eb5b22ed4e03a4eb42b32bd390df14"
+SRCREV = "fb5ced7c2cd6aeab0231f0cc3dee6bef72ddfb1e"
S = "${WORKDIR}/git"
-DEPENDS = "xz bzip2 zlib libcheck"
+DEPENDS = "xz bzip2 zlib"
inherit pkgconfig autotools
-EXTRA_OECONF = "--disable-tests"
+PACKAGECONFIG ??= ""
+PACKAGECONFIG[tests] = "--enable-tests, --disable-tests, libcheck"
BBCLASSEXTEND = "native"
--
2.10.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] uninative workflow
On 18 November 2016 at 21:30, Trevor Woerner wrote: > To be honest, I'm not entirely sure what the uninative stuff is > (explanations > or pointers to explanations appreciated!) but I'm trying to figure out how > to > work with it. It's a prebuild glibc designed to remove the differences between host distros, meaning that native sstate objects can be shared between host distros. It used to be opt-in for convenience but there's a nasty build failure. > Previously, generating an eSDK didn't require a uninative-tarball, but now, > apparently, it does? Any idea why? > b59eee7bebd413c7abe5626f69508e1fe47dd0ac: classes/populate_sdk_ext: require uninative It seems that possibly due to OE-Core commit ac59063bee0e32d0737340974f657341717a6abe, binaries produced without uninative aren't compatible with the uninative glibc. I did try earlier to ensure that the eSDK could work without uninative since the default configuration in OE-Core does not enable it, but it seems like I didn't go far enough. Given the practical considerations, just give up and require uninative to be enabled in order to build the eSDK. I'm not particularly happy about this, but I don't seem much of an alternative. Fixes [YOCTO #10566]. ac59063bee0e32d0737340974f657341717a6abe: uninative: Add a fix for icu-native to use the correct ABI If no -std= option is passed to icu's configure, it defaults to CXX11. This isn't what we want for uninative, so pass an explicit option which selects an older ABI on newer versions of g++. This avoids the __cxa_bad_array_new_length@CXXABI_1.3.8 symbol being used. > So now, in addition to building the uninative-tarball before being able to > build an eSDK, it also appears that I have to edit my local.conf to tell > the > build that I'm using it, where to find it, and its md5sum. The weird thing > is, > I could do "bitbake uninative-tarball" all day long, and every invocation > of > that command will generate a tarball with a different md5sum even though > the > configuration for each build is exactly the same! > You're Doing It Wrong. Generate the uninative tarball once, put it somewhere central, update configuration file. Or, just do what poky does: require conf/distro/include/yocto-uninative.inc INHERIT += "uninative" That uses the uninative tarball that is hosted on the yoctoproject site, so you only need to build your own if you don't want to trust external binaries. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-swupd][PATCH] swupd-client: do out-of-tree builds
From: André Draszik
Backport a patch that fixes out-of-tree builds, and at
the same time switch to using autotools.bbclass rather
than autotools-brokensep.bbclass
Signed-off-by: André Draszik
---
.../0001-build-allow-out-of-tree-builds.patch | 57 ++
recipes-core/swupd-client/swupd-client_git.bb | 5 +-
2 files changed, 59 insertions(+), 3 deletions(-)
create mode 100644
recipes-core/swupd-client/swupd-client/0001-build-allow-out-of-tree-builds.patch
diff --git
a/recipes-core/swupd-client/swupd-client/0001-build-allow-out-of-tree-builds.patch
b/recipes-core/swupd-client/swupd-client/0001-build-allow-out-of-tree-builds.patch
new file mode 100644
index 000..ae7b8e0
--- /dev/null
+++
b/recipes-core/swupd-client/swupd-client/0001-build-allow-out-of-tree-builds.patch
@@ -0,0 +1,57 @@
+From aab90416caac1c581f0de6814b5e43491407bce4 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Andr=C3=A9=20Draszik?=
+Date: Wed, 16 Nov 2016 10:55:23 +
+Subject: [PATCH] build: allow out of tree builds
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+When doing out-of-tree builds, the distributed
+scripts are in different directory than where
+the build is happening. This doesn't work:
+
+ make install-exec-hook
+ make[2]: Entering directory ''
+ perl scripts/findstatic.pl */*.o | grep -v Checking ||:
+ Can't open perl script "scripts/findstatic.pl": No such file or directory
+ make[2]: Leaving directory ''
+
+We therefore need to give perl the full path
+of the perl-script to run using the standard
+automake variable top_srcdir:
+
+ make install-exec-hook
+ make[2]: Entering directory ''
+ perl ../../../../../../../../tmp/swupd-client.git/scripts/findstatic.pl
*/*.o | grep -v Checking ||:
+'bin_paths' is unique to src/search.o, should be static? (initialised
variable)
+'do_search' is unique to src/search.o, should be static? (function)
+'download_manifests' is unique to src/search.o, should be static?
(function)
+'file_search' is unique to src/search.o, should be static? (function)
+'lib_paths' is unique to src/search.o, should be static? (initialised
variable)
+'report_find' is unique to src/search.o, should be static? (function)
+'scope' is unique to src/search.o, should be static? (initialised
variable)
+'search_type' is unique to src/search.o, should be static? (initialised
variable)
+ make[2]: Leaving directory ''
+
+Signed-off-by: André Draszik
+---
+Upstream-Status: Backport
[https://github.com/clearlinux/swupd-client/commit/b89d002a7d0f168354d9138207943b62138aa70a]
+ Makefile.am | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/Makefile.am b/Makefile.am
+index d485e00..f1a5b72 100644
+--- a/Makefile.am
b/Makefile.am
+@@ -126,7 +126,7 @@ distclean-local:
+ rm -rf aclocal.m4 ar-lib autom4te.cache config.guess config.h.in
config.h.in~ config.sub configure depcomp install-sh ltmain.sh m4 Makefile.in
missing compile
+
+ install-exec-hook:
+- perl scripts/findstatic.pl */*.o | grep -v Checking ||:
++ perl $(top_srcdir)/scripts/findstatic.pl */*.o | grep -v Checking ||:
+
+
+ TEST_EXTENSIONS = .bats
+--
+2.10.2
+
diff --git a/recipes-core/swupd-client/swupd-client_git.bb
b/recipes-core/swupd-client/swupd-client_git.bb
index 8df89a1..fd4716f 100644
--- a/recipes-core/swupd-client/swupd-client_git.bb
+++ b/recipes-core/swupd-client/swupd-client_git.bb
@@ -11,6 +11,7 @@ SRC_URI = "\
file://Change-systemctl-path-to-OE-systemctl-path.patch \
file://0001-Add-configure-option-to-re-enable-updating-of-config.patch \
file://Make-pinned-pubkey-configurable.patch \
+file://0001-build-allow-out-of-tree-builds.patch \
"
SRCREV = "f4000c5b22be47ec1af2f8748fd71a36148b5dc4"
@@ -20,9 +21,7 @@ RDEPENDS_${PN}_append_class-target = " oe-swupd-helpers
bsdtar"
# We check /etc/os-release for the current OS version number
RRECOMMENDS_${PN}_class-target = "os-release"
-# TODO: we inherit autotools-brokensep because the Makefile calls a perl script
-# in ${S} during one of its steps.
-inherit pkgconfig autotools-brokensep systemd
+inherit pkgconfig autotools systemd
EXTRA_OECONF = "\
--with-systemdsystemunitdir=${systemd_system_unitdir} \
--
2.10.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] uninative workflow
Excellent! Thanks, Ross, for the explanations :-) On Mon, Nov 21, 2016 at 9:40 AM, Burton, Ross wrote: > > On 18 November 2016 at 21:30, Trevor Woerner wrote: >> >> To be honest, I'm not entirely sure what the uninative stuff is >> (explanations >> or pointers to explanations appreciated!) but I'm trying to figure out how >> to >> work with it. > > > It's a prebuild glibc designed to remove the differences between host > distros, meaning that native sstate objects can be shared between host > distros. It used to be opt-in for convenience but there's a nasty build > failure. > >> >> Previously, generating an eSDK didn't require a uninative-tarball, but >> now, >> apparently, it does? Any idea why? > > > b59eee7bebd413c7abe5626f69508e1fe47dd0ac: > classes/populate_sdk_ext: require uninative > > It seems that possibly due to OE-Core commit > ac59063bee0e32d0737340974f657341717a6abe, binaries produced without > uninative aren't compatible with the uninative glibc. I did try earlier > to ensure that the eSDK could work without uninative since the default > configuration in OE-Core does not enable it, but it seems like I didn't > go far enough. Given the practical considerations, just give up and > require uninative to be enabled in order to build the eSDK. I'm not > particularly happy about this, but I don't seem much of an alternative. > > Fixes [YOCTO #10566]. > > ac59063bee0e32d0737340974f657341717a6abe: > uninative: Add a fix for icu-native to use the correct ABI > > If no -std= option is passed to icu's configure, it defaults to CXX11. > This isn't what we want for uninative, so pass an explicit option > which selects an older ABI on newer versions of g++. > > This avoids the __cxa_bad_array_new_length@CXXABI_1.3.8 symbol > being used. > >> >> So now, in addition to building the uninative-tarball before being able to >> build an eSDK, it also appears that I have to edit my local.conf to tell >> the >> build that I'm using it, where to find it, and its md5sum. The weird thing >> is, >> I could do "bitbake uninative-tarball" all day long, and every invocation >> of >> that command will generate a tarball with a different md5sum even though >> the >> configuration for each build is exactly the same! > > > You're Doing It Wrong. Generate the uninative tarball once, put it > somewhere central, update configuration file. > > Or, just do what poky does: > > require conf/distro/include/yocto-uninative.inc > INHERIT += "uninative" > > That uses the uninative tarball that is hosted on the yoctoproject site, so > you only need to build your own if you don't want to trust external > binaries. > > Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [raspberrypi] raspi3 vs raspi2
Wow, this is great news! Thanks, both of you :-) On Sun, Nov 20, 2016 at 2:28 PM, Khem Raj wrote: > Herve > > On Sun, Nov 20, 2016 at 12:00 AM, Herve Jourdain > wrote: >> 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. > >> >> 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. > >> >> Herve >> >> -Original Message- >> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] >> On Behalf Of Khem Raj >> Sent: samedi 19 novembre 2016 18:30 >> To: Trevor Woerner >> Cc: yocto@yoctoproject.org >> Subject: ***SPAM*** Re: [yocto] [raspberrypi] raspi3 vs raspi2 >> >> On Fri, Nov 18, 2016 at 1:20 PM, Trevor Woerner wrote: >>> 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 >> >>> >>> Best regards, >>> Trevor >>> -- >>> ___ >>> yocto mailing list >>> yocto@yoctoproject.org >>> https://lists.yoctoproject.org/listinfo/yocto >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-swupd][PATCH 1/2] oe-swupd-helpers: convert scripts to posix shell
From: André Draszik These scripts don't do much and there's no reason for them to require bash as interpreter. Signed-off-by: André Draszik --- recipes-core/swupd-client/oe-swupd-helpers/clr_pre_update.sh | 2 +- recipes-core/swupd-client/oe-swupd-helpers/kernel_updater.sh | 2 +- recipes-core/swupd-client/oe-swupd-helpers/systemdboot_updater.sh | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/recipes-core/swupd-client/oe-swupd-helpers/clr_pre_update.sh b/recipes-core/swupd-client/oe-swupd-helpers/clr_pre_update.sh index 6302090..835948d 100755 --- a/recipes-core/swupd-client/oe-swupd-helpers/clr_pre_update.sh +++ b/recipes-core/swupd-client/oe-swupd-helpers/clr_pre_update.sh @@ -1,4 +1,4 @@ -#!/bin/bash +#!/bin/sh set -u ### diff --git a/recipes-core/swupd-client/oe-swupd-helpers/kernel_updater.sh b/recipes-core/swupd-client/oe-swupd-helpers/kernel_updater.sh index b0d5335..98e12c2 100755 --- a/recipes-core/swupd-client/oe-swupd-helpers/kernel_updater.sh +++ b/recipes-core/swupd-client/oe-swupd-helpers/kernel_updater.sh @@ -1,4 +1,4 @@ -#!/bin/bash +#!/bin/sh ### # This script will be called after an updated kernel has been installed diff --git a/recipes-core/swupd-client/oe-swupd-helpers/systemdboot_updater.sh b/recipes-core/swupd-client/oe-swupd-helpers/systemdboot_updater.sh index 470cd6e..19f025d 100755 --- a/recipes-core/swupd-client/oe-swupd-helpers/systemdboot_updater.sh +++ b/recipes-core/swupd-client/oe-swupd-helpers/systemdboot_updater.sh @@ -1,4 +1,4 @@ -#!/bin/bash +#!/bin/sh ### # systemd bootloader installer -- 2.10.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf
On Sun, Nov 20, 2016 at 9:21 PM, Herve Jourdain wrote:
> Hi Khem,
>
> For cortexa53 in aarch32, the problem is to figure out if we want to cover
> all cases or not.
> Raspberrypi3 is one case of CortexA53 that has crc support, but no crypto
> support. So I could define a cortexa53-32 as being just that.
> But then, there are other CortexA53-based SoCs that do have the crypto
> extension, and I thought that, since I was going to modify it, I'd rather
> cover all possible cases/options...
>
> The one thing that could be scrapped is the hf option, if we decide that all
> cortexa53 aarch32 will be hf only.
> Then that would avoid the hf duplication of the aarch32 tunes, leaving only 2
> tunes for cortexa53 aarch32 + 1 tune for cortexa53 aarch64.
>
> Please advise what you would prefer me to do.
is there an advantage of having crc and crypto as systemwide tune
options or is it more beneficial to apply them surgically to needed
apps
via MACHINE_FEATURES
>
> Herve
>
> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: dimanche 20 novembre 2016 20:30
> To: Herve Jourdain
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf
> and add raspberrypi3-64.conf
>
> Herve,
>
> There is no need to create so many variants for a53 32 bit mode. We can keep
> using whatever we have its only 64bit that needs to be added as a new machine.
>
> On Sun, Nov 20, 2016 at 4:06 AM, Herve Jourdain
> wrote:
>> Hi Khem,
>>
>> FYI, I am sending a slightly modified version (cortexa53hf-32 instead
>> of
>> cortexa53-32 for raspberrypi3.conf).
>> They still depend on modifications in oe-core (heavier this time than
>> before), also posted to the list.
>>
>> Herve
>>
>> -Original Message-
>> From: Khem Raj [mailto:raj.k...@gmail.com]
>> Sent: samedi 19 novembre 2016 19:19
>> To: Herve Jourdain ; yocto@yoctoproject.org
>> Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify
>> raspberrypi3.conf and add raspberrypi3-64.conf
>>
>> Nevermind, I managed to apply it, there are some CR changes I guess
>> which was freaking git
>>
>> On 11/19/16 5:03 AM, Herve Jourdain wrote:
>>> Signed-off-by: Herve Jourdain
>>> ---
>>> conf/machine/raspberrypi3-64.conf | 19 +++
>>> conf/machine/raspberrypi3.conf| 8 ++--
>>> 2 files changed, 25 insertions(+), 2 deletions(-) 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..a5ceddb
>>> --- /dev/null
>>> +++ b/conf/machine/raspberrypi3-64.conf
>>> @@ -0,0 +1,19 @@
>>> +#@TYPE: Machine
>>> +#@NAME: RaspberryPi 3 Development Board
>>> +#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64
>>> +bits mode
>>> +
>>> +DEFAULTTUNE ?= "cortexa53-64"
>>> +
>>> +MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}"
>>> +
>>> +MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
>>> +
>>> +PREFERRED_VERSION_linux-raspberrypi_raspberrypi3-64 ?= "4.7.%"
>>> +
>>> +require conf/machine/include/tune-cortexa53.inc
>>> +include conf/machine/include/rpi-base.inc
>>> +
>>> +SERIAL_CONSOLE = "115200 ttyS0"
>>> +VC4_CMA_SIZE ?= "cma-256"
>>> +
>>> +UBOOT_MACHINE = "rpi_3_config"
>>> diff --git a/conf/machine/raspberrypi3.conf
>>> b/conf/machine/raspberrypi3.conf index 9820209..f142323 100644
>>> --- a/conf/machine/raspberrypi3.conf
>>> +++ b/conf/machine/raspberrypi3.conf
>>> @@ -2,12 +2,16 @@
>>> #@NAME: RaspberryPi 3 Development Board
>>> #@DESCRIPTION: Machine configuration for the RaspberryPi 3
>>>
>>> -MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
>>> +DEFAULTTUNE ?= "cortexa53-32"
>>> +
>>> +MACHINEOVERRIDES = "raspberrypi2:raspberrypi:${MACHINE}"
>>>
>>> MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
>>>
>>> -include conf/machine/raspberrypi2.conf
>>> +require conf/machine/include/tune-cortexa53.inc
>>> +include conf/machine/include/rpi-base.inc
>>>
>>> SERIAL_CONSOLE = "115200 ttyS0"
>>> VC4_CMA_SIZE ?= "cma-256"
>>>
>>> +UBOOT_MACHINE = "rpi_3_config"
>>>
>>
>>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-swupd][PATCH 2/2] swupd-client: don't unconditionally depend on bash
From: André Draszik
The swupd client itself does not depend on bash anymore since
version 3.3.0. Any posix shell is fine. So let's move the
runtime dependency to the appropriate place.
If some layer's oe-swupd-helpers.bbappend does introduce
a bash dependency, it should just state that dependency
itself.
As the shell now be provided by bash or busybox, also add
an appropriate entry to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS.
Signed-off-by: André Draszik
---
conf/layer.conf| 1 +
recipes-core/swupd-client/oe-swupd-helpers.bb | 3 +--
recipes-core/swupd-client/swupd-client_2.87.bb | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index 2998949..50e7558 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -13,4 +13,5 @@ LAYERVERSION_meta-swupd = "1"
SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += "\
oe-swupd-helpers->bash \
+ oe-swupd-helpers->busybox \
"
diff --git a/recipes-core/swupd-client/oe-swupd-helpers.bb
b/recipes-core/swupd-client/oe-swupd-helpers.bb
index 4690f21..9a5a8dd 100644
--- a/recipes-core/swupd-client/oe-swupd-helpers.bb
+++ b/recipes-core/swupd-client/oe-swupd-helpers.bb
@@ -35,5 +35,4 @@ do_install () {
done
}
-RDEPENDS_${PN} += "bash"
-FILES_${PN} += "${systemd_system_unitdir}"
\ No newline at end of file
+FILES_${PN} += "${systemd_system_unitdir}"
diff --git a/recipes-core/swupd-client/swupd-client_2.87.bb
b/recipes-core/swupd-client/swupd-client_2.87.bb
index 96e7a10..09d09a4 100644
--- a/recipes-core/swupd-client/swupd-client_2.87.bb
+++ b/recipes-core/swupd-client/swupd-client_2.87.bb
@@ -24,7 +24,7 @@ SRC_URI[md5sum] = "5d272c62edb8a9c576005ac5e1182ea3"
SRC_URI[sha256sum] =
"45df259a7dc2fed985ee9961e112120fc46670dd75476c3262fc6804b1c66fb8"
DEPENDS = "glib-2.0 curl openssl libarchive"
-RDEPENDS_${PN}_append_class-target = " oe-swupd-helpers bsdtar"
+RDEPENDS_${PN}_append_class-target = " oe-swupd-helpers bash bsdtar"
# We check /etc/os-release for the current OS version number
RRECOMMENDS_${PN}_class-target = "os-release"
--
2.10.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] populate_sdk_ext: Unable to locate package nativesdk-buildtools-perl-dummy
> From: "Paul Eggleton" > Sent: Friday, 18 November, 2016 2:46:07 AM > I think the issue is this hasn't really been tested with deb > packaging. You > have hit a genuine bug though - would you mind filing a bug at > http://bugzilla.yoctoproject.org? I still don't fully understand the problem, so I don't know where to file the bug! But I think apt-native and buildtools-tarball are OK. Right now I believe this is related to the ARCH value of the dummy debian packages. It is "allarch" (in the filename and the Packages corresponding summary file) whereas similar packages have the "all" arch. I'm trying to understand why there is such a difference... If someone has some knowledge on the subject to help me, it'd be great :-) Cheers Michel -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] populate_sdk_ext: Unable to locate package nativesdk-buildtools-perl-dummy
On Mon, 21 Nov 2016 18:22:10 Michel D'HOOGE wrote: > > From: "Paul Eggleton" > > Sent: Friday, 18 November, 2016 2:46:07 AM > > > > I think the issue is this hasn't really been tested with deb > > packaging. You > > have hit a genuine bug though - would you mind filing a bug at > > http://bugzilla.yoctoproject.org? > > I still don't fully understand the problem, so I don't know where to file > the bug! But I think apt-native and buildtools-tarball are OK. > > Right now I believe this is related to the ARCH value of the dummy debian > packages. It is "allarch" (in the filename and the Packages corresponding > summary file) whereas similar packages have the "all" arch. > I'm trying to understand why there is such a difference... I suspect it has to do with the arch mapping that goes on in meta/classes/package_deb.bbclass; it probably doesn't understand the dummy architecture we're giving it. The thing is even if it were to be "corrected" to fall back to "all" instead of "allarch" that probably still wouldn't work properly because the architecture of the perl packages would be a higher priority than "all" and thus the dummy package wouldn't take precedence. In any case feel free to file a bug under "OE-Core -> Core" in bugzilla, that would be a reasonable category for this issue. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [raspberrypi] raspi3 vs raspi2
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-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" -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [raspberrypi] raspi3 vs raspi2
4.4 does not support 64-bit pi3, do you set the PREFERRED_VERSION in local conf metadata ? 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-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" > signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Yocto Project 2.1.2 (Krogoth 15.0.2) Released
Hello, The latest release of the Yocto Project 2.1.2 (krogoth-15.0.2) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/poky-krogoth-15.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.1.2/poky-krogoth-15.0.2.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/RELEASENOTES Full pass test report is available at: https://wiki.yoctoproject.org/wiki/WW46_-_2016-11-10_-_Test_Cycle_2.1.2_rc1 Thanks go out to everyone for all their hard work during this release! Sincerely, Tracy Graydon Yocto Project Build and Release -- yocto-2.1.2 Errata -- Please note that we have added support for Eclipse Neon and have removed Luna support, as reflected below. Release Name: eclipse-poky-mars-krogoth-15.0.2 Branch: mars/krogoth Tag: mars/krogoth-15.0.2 Hash: 92aa0e79e8b01c56f0670af3cd8296ec68b43350 md5: 10c736f97fd1e7c519e27d9c987173c2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/eclipse-poky-mars-krogoth-15.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.1.2/eclipse-poky-mars-krogoth-15.0.2.tar.bz2 Release Name: eclipse-poky-neon-krogoth-15.0.2 Branch: neon/krogoth Tag: neon/krogoth-15.0.2 Hash: a751bfdcb095bdc7bf8008b205b06adfdaad294f md5: e9613760c1b4b71eae120e53f9b21f57 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/eclipse-poky-neon-krogoth-15.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.1.2/eclipse-poky-neon-krogoth-15.0.2.tar.bz2 Release Name: meta-qt3-krogoth-15.0.2 Branch: krogoth Tag: krogoth-15.0.2 Hash: d5d5225ef78e403301a429d0f64bd4a262b0fa4d md5: c854634cf76c2e0a21d3f941684e6af6 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/meta-qt3-krogoth-15.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.1.2/meta-qt3-krogoth-15.0.2.tar.bz2 Release Name: meta-qt4-krogoth-15.0.2 Branch: krogoth Tag: krogoth-15.0.2 Hash: 92a72a790a427af5f85ce86fea4fce86a72c7b58 md5: 8ec0b619765d7caa3d514c5e4141e5ba Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/meta-qt4-krogoth-15.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.1.2/meta-qt4-krogoth-15.0.2.tar.bz2 Release Name: poky-krogoth-15.0.2 Branch: krogoth Tag: krogoth-15.0.2 Hash: cca8dd15c8096626052f6d8d25ff1e9a606104a3 md5: 8c1821e1c4b1b06e6114eab4f7544a0f Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1.2/poky-krogoth-15.0.2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.1.2/poky-krogoth-15.0.2.tar.bz2 --- Known Issues --- N/A --- Security Fixes --- python3: Security fix CVE-2016-1000110 python: Security fix CVE-2016-1000110 perl: fix CVE-2016-1238 openssl: Security fix CVE-2016-6306 openssl: Security fix CVE-2016-6304 openssl: Security fix CVE-2016-6303 openssl: Security fix CVE-2016-6302 openssl: Security fix CVE-2016-2182 openssl: Security fix CVE-2016-2181 openssl: Security fix CVE-2016-2180 openssl: Security fix CVE-2016-2179 openssl: Security fix CVE-2016-2178 cracklib: Apply patch to fix CVE-2016-6318 wpa_supplicant: Security Advisory-CVE-2016-4477 wpa_supplicant: Security Advisory-CVE-2016-4476 perl: fix CVE-2015-8607 perl: fix CVE-2016-6185 perl: fix CVE-2016-2381 qemu: Secuirty fix for CVE-2016-5403 qemu: Security fix for CVE-2016-4002 qemu: Security fix CVE-2016-6351 qemu: Security fix CVE-2016-4439 qemu: Security Fix CVE-2016-3712 qemu: Security Fix CVE-2016-3710 util-linux: Security fix for CVE-2016-5011 wget: Security fix CVE-2016-4971 openssh: Security fix CVE-2015-8325 openssh: Security fix CVE-2016-5615 openssh: Security fix CVE-2016-6210 curl: security fix for CVE-2016-7141 sudo: CVE-2015-8239 tiff: Security fix CVE-2016-5323 tiff: Security fix CVE-2016-5321 tiff: Security fix CVE-2016-3186 tiff: Security fix CVE-2015-8784 tiff: Security fix CVE-2015-8781 curl: security fix for CVE-2016-5421 curl: security fix for CVE-2016-5420 curl: security fix for CVE-2016-5419 --- Fixes --- bsp-guide: Updated the yocto-bsp create selections in the example. yocto-project-qs: Fixed Minnow MAX build example yocto-project-qs: Altered MinnowBoard MAX example bsp-guide: Fixed the yocto-bsp create example output binutils: fix AR issue when opkg is unpacking IPKs containing empty entries multilib_header: avoid sstate checksum issues for -nativesdk recipes tzdata: update to 2016g tzcode-native: Update to 2016g pulseaudio: Disable unit tests pigz: Update SRC_URI useradd: Fix infinite build loop libarchive: respect disable-acl configuration option useradd.bbclass: Strip trailing ';' in cmd params useradd: use bindir_native for pseudo PATH oeqa/buildiptables: Switch from netfilter.org to yoctoproject.org mirror python3: Fixes several python3 dependency problems documentation: Changes to support a 2.1.2 krogoth release. tif
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-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" > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [raspberrypi] raspi3 vs raspi2
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:twoer...@gmail.com] Sent: mardi 22 novembre 2016 06:39 To: Khem Raj Cc: Herve Jourdain ; yocto@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" > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [raspberrypi] raspi3 vs raspi2
On 11/21/16 9:39 PM, Trevor Woerner wrote: > 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 > Did you take https://github.com/kraj/meta-raspberrypi/commit/361757b9c1538b0a15577d75308ecef93db55965 as well? >> >> 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-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" >>> >> > > > signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf
Hi Khem,
I believe it would be more appropriate to have it "system-wide", because at
some point it should not be something the apps need to worry about.
Plus, it's really a SoC thing, some armv8 SoCs do implement those options, some
don't (when I say "option" there, I mean it's a HW block that may or may not be
implemented in the SoC, it's not just a compilation switch that would work for
all revisions of armv8).
So I believe those HW options should indeed be defined in arch-armv8.inc, and
each soc-specific file should select the options that are possible for it.
For instance, cortex-a53 has "by definition" the crc HW included, but the
crypto HW block may or may not be implemented. For Raspberrypi3, BCM2837 does
not have it. Most other Cortex-A53 I know of have it, though.
Therefore, the definition of the "crypto" variant for cortexa53-32, in addition
with the sf/hf variants for aarch32.
For aarch64, the floating point abi is hf, so that's less variants, but I
should also add cortexa53crypto-64, to be exhaustive... It's not going to be
useful for RPI3, but it might be for all future
armv8/cortex-a53/cortex-a57/cortex-a72/cortex-a73 based SoCs that will have to
be supported in the future.
So we could add it all now, or we could add it in the future as needs emerge.
Herve
-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: lundi 21 novembre 2016 17:35
To: Herve Jourdain
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and
add raspberrypi3-64.conf
On Sun, Nov 20, 2016 at 9:21 PM, Herve Jourdain wrote:
> Hi Khem,
>
> For cortexa53 in aarch32, the problem is to figure out if we want to cover
> all cases or not.
> Raspberrypi3 is one case of CortexA53 that has crc support, but no crypto
> support. So I could define a cortexa53-32 as being just that.
> But then, there are other CortexA53-based SoCs that do have the crypto
> extension, and I thought that, since I was going to modify it, I'd rather
> cover all possible cases/options...
>
> The one thing that could be scrapped is the hf option, if we decide that all
> cortexa53 aarch32 will be hf only.
> Then that would avoid the hf duplication of the aarch32 tunes, leaving only 2
> tunes for cortexa53 aarch32 + 1 tune for cortexa53 aarch64.
>
> Please advise what you would prefer me to do.
is there an advantage of having crc and crypto as systemwide tune options or is
it more beneficial to apply them surgically to needed apps via MACHINE_FEATURES
>
> Herve
>
> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: dimanche 20 novembre 2016 20:30
> To: Herve Jourdain
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify
> raspberrypi3.conf and add raspberrypi3-64.conf
>
> Herve,
>
> There is no need to create so many variants for a53 32 bit mode. We can keep
> using whatever we have its only 64bit that needs to be added as a new machine.
>
> On Sun, Nov 20, 2016 at 4:06 AM, Herve Jourdain
> wrote:
>> Hi Khem,
>>
>> FYI, I am sending a slightly modified version (cortexa53hf-32 instead
>> of
>> cortexa53-32 for raspberrypi3.conf).
>> They still depend on modifications in oe-core (heavier this time than
>> before), also posted to the list.
>>
>> Herve
>>
>> -Original Message-
>> From: Khem Raj [mailto:raj.k...@gmail.com]
>> Sent: samedi 19 novembre 2016 19:19
>> To: Herve Jourdain ; yocto@yoctoproject.org
>> Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify
>> raspberrypi3.conf and add raspberrypi3-64.conf
>>
>> Nevermind, I managed to apply it, there are some CR changes I guess
>> which was freaking git
>>
>> On 11/19/16 5:03 AM, Herve Jourdain wrote:
>>> Signed-off-by: Herve Jourdain
>>> ---
>>> conf/machine/raspberrypi3-64.conf | 19 +++
>>> conf/machine/raspberrypi3.conf| 8 ++--
>>> 2 files changed, 25 insertions(+), 2 deletions(-) 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..a5ceddb
>>> --- /dev/null
>>> +++ b/conf/machine/raspberrypi3-64.conf
>>> @@ -0,0 +1,19 @@
>>> +#@TYPE: Machine
>>> +#@NAME: RaspberryPi 3 Development Board
>>> +#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64
>>> +bits mode
>>> +
>>> +DEFAULTTUNE ?= "cortexa53-64"
>>> +
>>> +MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}"
>>> +
>>> +MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
>>> +
>>> +PREFERRED_VERSION_linux-raspberrypi_raspberrypi3-64 ?= "4.7.%"
>>> +
>>> +require conf/machine/include/tune-cortexa53.inc
>>> +include conf/machine/include/rpi-base.inc
>>> +
>>> +SERIAL_CONSOLE = "115200 ttyS0"
>>> +VC4_CMA_SIZE ?= "cma-256"
>>> +
>>> +UBOOT_MACHINE = "rpi_3_config"
>>> diff --git a/conf/machine/raspberrypi3.conf
>>> b/conf/machine/raspberrypi3.conf index 9820209..f142323 100644
>>> --- a/c
Re: [yocto] [raspberrypi] raspi3 vs raspi2
On Mon 2016-11-21 @ 10:29:18 PM, Khem Raj wrote:
> 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.
>
> >>> 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
Date: Sat Nov 12 11:32:56 2016 -0800
linux-raspberrypi-4.8: Update to 4.8.8
Signed-off-by: Khem Raj
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.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
