Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: auh@auh.yoctoproject.org,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [AUH] u-boot-mkimage: upgrading to 2018.05 FAILED
Date: Thu, 17 May 2018 10:01:14 -0400	[thread overview]
Message-ID: <20180517140114.GD9871@bill-the-cat.ec.rr.com> (raw)
In-Reply-To: <8c49ac0d-e52e-505b-d6c2-688ca7b3fb6e@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

On Thu, May 17, 2018 at 12:33:24PM +0200, Marek Vasut wrote:
> On 05/17/2018 11:53 AM, Alexander Kanavin wrote:
> > On 05/17/2018 12:56 PM, Burton, Ross wrote:
> >> Looks like AUH runs as a x86 machine, which is why it doesn't catch
> >> u-boot.
> > 
> > Also we have already discussed this 2 month ago. Marek, as the u-boot
> > maintainer, can you look into enabling u-boot on qemu please?
> 
> Wouldn't it make more sense to fix the AUH so it handles U-Boot and
> similar packages correctly even without the qemu dependency ?

Note that in U-Boot we run (and run test.py on) qemu-x86 and qemux86-64
so there's no reason these days to mask U-Boot out.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2018-05-17 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180517021314.0C556440002@auh.yoctoproject.org>
2018-05-17  9:40 ` [AUH] u-boot-mkimage: upgrading to 2018.05 FAILED Marek Vasut
2018-05-17  9:56   ` Burton, Ross
2018-05-17  9:53     ` Alexander Kanavin
2018-05-17 10:33       ` Marek Vasut
2018-05-17 12:17         ` Burton, Ross
2018-05-17 13:04         ` Alexander Kanavin
2018-05-17 21:20           ` Marek Vasut
2018-05-18 14:06             ` Alexander Kanavin
2018-05-17 14:01         ` Tom Rini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180517140114.GD9871@bill-the-cat.ec.rr.com \
    --to=trini@konsulko.com \
    --cc=auh@auh.yoctoproject.org \
    --cc=marek.vasut@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox