From: Marek Vasut <marek.vasut@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
"Burton, Ross" <ross.burton@intel.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 23:20:39 +0200 [thread overview]
Message-ID: <b791ecd2-619b-ab33-b474-e2d7630eb80d@gmail.com> (raw)
In-Reply-To: <0df38331-afdf-b47c-410e-6640c74e8b14@linux.intel.com>
On 05/17/2018 03:04 PM, Alexander Kanavin wrote:
> On 05/17/2018 01:33 PM, Marek Vasut 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 ?
>
> Determining the latest upstream version, performing the recipe upgrade,
> and testing that the upgraded version builds are all done by calling
> bitbake. Which of course requires that MACHINE is set to something
> specific, in this case qemux86. As u-boot is disabled there, it gets
> skipped. I could special-case u-boot, but I do think it's better to
> enable it on qemu, which would also allow better AB testing across
> architectures and during runtime (booting images) for instance.
Let's see how this works:
https://patchwork.ozlabs.org/patch/915781/
Once this gets mainline, we should then be able to enable u-boot for
qemux86/qemux86-64 . I have a patch ready for that too, but let's wait
until the U-Boot patch discussion is over.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-05-17 21:20 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 [this message]
2018-05-18 14:06 ` Alexander Kanavin
2018-05-17 14:01 ` Tom Rini
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=b791ecd2-619b-ab33-b474-e2d7630eb80d@gmail.com \
--to=marek.vasut@gmail.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=auh@auh.yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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