On Wed, 2016-12-28 at 13:38 -0800, Ricardo Neri wrote:
> > do_install_class-target() {
> > -OVMF_DIR_SUFFIX="X64"
> > -if [ "${TARGET_ARCH}" != "x86_64" ] ; then
> > -OVMF_DIR_SUFFIX="Ia32" # Note the different capitalization
> > -fi
> > +# Traditional location.
> >
On Wed, 2016-12-28 at 20:27 +0100, Patrick Ohly wrote:
> > > fwiw, I've been maintaining acpica recipe in meta-oe, and will
> keep an
> > > eye here as well.
> > > meta-luv supports both x86* and arm*, and we have an interest in
> > > having the same features available and working for qemuaarch64.
On Wed, 2016-12-21 at 14:11 +0100, Patrick Ohly wrote:
> The recipe now compiles OVMF twice, once without Secure Boot, once
> with. This is the same approach as in
> https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec
Besides the fact that Fedora does it, is there a particular reason
On Wed, 2016-12-21 at 14:11 +0100, Patrick Ohly wrote:
> +# File name of a OVMF BIOS file, to be added with -drive
> if=pflash.
> +# Found in the same places as the rootfs, with or without one
> of
> +# these suffices: qcow2, bin.
> +# Setting one also adds "-vga
From: He Zhe
v1 to v2: Remove redundant tarball link in SRC_URI
v2 to v3: Address Alex's comments:
Remove kexec-aarch64.patch and kexec-x32.patch files
Correct Upstream-Status
Regenerate patch with git's rename detection enabled
He Zhe (1):
On 12/28/2016 08:15 PM, Alexander Kanavin wrote:
> On 12/27/2016 08:43 AM, zhe...@windriver.com wrote:
>> From: He Zhe
>>
>> Remove kexec-aarch64.patch since it has been merged upstream
>> Remove kexec-x32.patch since it has been reverted upstream
>> Backport patches for
From: He Zhe
Remove kexec-aarch64.patch since it has been merged upstream
Remove kexec-x32.patch since it has been reverted upstream
Add patches for kdump arm64 from upstream mailing list:
http://lists.infradead.org/pipermail/kexec/2016-November/017555.html
Signed-off-by:
Please ignore the below patch. The issue was actually fixed in master at
http://cgit.openembedded.org/openembedded-core/commit/meta/classes/extrausers.bbclass?id=fa541362e2d2cc0494a86a413b7b52dfe3eee908
BR,
Awais
From:
These patches should apply to master but are meant for current
ross/mut: ppp fails to build on musl when the 4.9 headers are used.
Thanks to Khem for the patch suggestion.
Jussi
The following changes since commit 1dc1894e05ef0f3aeeefa61ed89613f17bba2e83:
cairo: set license for cairo-doc
ppp no longer provides the duplicate if_pppox.h header so no need to patch that
out of the Makefile.
Signed-off-by: Jussi Kukkonen
---
...01-ppp-Fix-compilation-errors-in-Makefile.patch | 51 ++
1 file changed, 3 insertions(+), 48 deletions(-)
diff
Removing unused includes fixes the build.
Fixes [YOCTO #10853].
Signed-off-by: Jussi Kukkonen
---
.../ppp/ppp/0001-ppp-Remove-unneeded-include.patch | 43 ++
meta/recipes-connectivity/ppp/ppp_2.4.7.bb | 1 +
2 files changed, 44
On 12/27/2016 08:43 AM, zhe...@windriver.com wrote:
From: He Zhe
Remove kexec-aarch64.patch since it has been merged upstream
Remove kexec-x32.patch since it has been reverted upstream
Backport patches for kdump arm64 from:
The extrausers functionality requires base-passwd and shadow
to be installed before it can be leveraged. Otherwise while
using the features of the class we get into build errors
like the following
ERROR: core-image-minimal-initramfs-1.0-r0 do_rootfs:
core-image-minimal-initramfs: useradd command
This patchset extends and modifies the xml format of the test metadata report.
The goal is to make the data more comprehensive in slightly more consistent
format.
The following changes since commit 425afe2484707640ac71194885fdb263e95e9950:
lib/oe/utils: Drop python2 compatibility code
Put all host distro data under one element. In addition
take the data directly from /etc/os-release instead of the "lsb API".
The /etc/os-release file is virtually ubiquitous, now, and using its
field names and values provides a more standardized and extensible
format.
[YOCTO #10590]
Use the same format, based on /etc/os-release, as for host distro
information.
[YOCTO #10590]
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/utils/metadata.py | 17 ++---
scripts/oe-selftest | 4 ++--
2 files changed, 12
It's better just to not have the xml elements than to have elements with
faux data. One could have git branch named 'unknown', for example.
[YOCTO #10590]
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/utils/metadata.py | 7 +++
scripts/oe-selftest
Makes it easier to put the commits into a timeline.
[YOCTO #10590]
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/utils/metadata.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils/metadata.py
Revision is a bit vague and could point to a tag, for example. Git
commit objects are unambiguous and persistent so be explicit that the
element should contain git commit hash.
[YOCTO #10590]
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/utils/metadata.py |
Have the layer name as an attribute instead of of the name of the
element itself. That is, have instead of
. A bit better XML design.
[YOCTO #10590]
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/utils/metadata.py | 8 +---
1 file changed, 5
Always return a valid branch name, or, '(nobranch)' if the current HEAD
is detached. Also, always return the hash of the commit object that HEAD
is pointing to. Previous code returned an incorrect branch name (or
crashed) e.g. in the case of detached HEAD.
[YOCTO #10590]
Signed-off-by: Markus
[YOCTO #10590]
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/utils/metadata.py | 32 +++-
1 file changed, 19 insertions(+), 13 deletions(-)
diff --git a/meta/lib/oeqa/utils/metadata.py b/meta/lib/oeqa/utils/metadata.py
index
On Tue, 2016-12-27 at 18:56 -0800, Ricardo Neri wrote:
> On Wed, 2016-12-21 at 16:19 +0200, Fathi Boudra wrote:
> >
> > fwiw, I've been maintaining acpica recipe in meta-oe, and will keep an
> > eye here as well.
> > meta-luv supports both x86* and arm*, and we have an interest in
> > having the
On Wed, 2016-12-21 at 14:11 +0100, Patrick Ohly wrote:
> When used with '-drive if=pflash', qemu will store UEFI variables
> inside the firmware image file. That is unexpected for a file located in
> the sysroot, which should be read-only, while it is normal for image
> files in the deploy/images
24 matches
Mail list logo