From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED
Date: Mon, 19 Mar 2018 12:31:20 +0200 [thread overview]
Message-ID: <5420e82b-7ca0-5dea-659c-208e26e5bc32@linux.intel.com> (raw)
In-Reply-To: <835df47e-ef32-61a7-f856-eee8dac4610c@gmail.com>
On 03/19/2018 12:08 PM, Marek Vasut wrote:
>>>> I'm not sure how to solve it - perhaps you can simply take the email as
>>>> a reminder to update the whole set on your machine manually?
>>>
>>> I was hoping the tool will take care of that, now that I've finally
>>> plucked all the extra patches out.
>>
>> You can automate most of the upgrade by running 'devtool upgrade u-boot'
>> though. Extra patches are not a problem for automatic updates. If U-BOOT
>> and qemu can be made friends, that's even better.
>
> So what's the problem with qemu and u-boot ? I don't see why it couldn't
> be built for qemu targets.
Maybe, but right now it's not working, and it's something the u-boot
experts should tackle and test.
ak@kanavin-desktop:~/development/poky/build$ bitbake u-boot
Loading cache: 100%
|##########################################################################################################################################################################################################################|
Time: 0:00:00
Loaded 1310 entries from dependency cache.
ERROR: Nothing PROVIDES 'u-boot'
u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in
the qemux86 machine configuration.
I do see that u-boot has qemu configs though:
http://git.denx.de/?p=u-boot.git;a=tree;f=configs;h=a6603a9f312f1e86fa233adf21a51a2c7cf46653;hb=HEAD
Alex
next prev parent reply other threads:[~2018-03-19 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180316092125.64DD7440071@auh.yoctoproject.org>
2018-03-17 16:27 ` [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED Marek Vasut
2018-03-19 8:50 ` Alexander Kanavin
2018-03-19 9:55 ` Marek Vasut
2018-03-19 9:57 ` Alexander Kanavin
2018-03-19 10:08 ` Marek Vasut
2018-03-19 10:31 ` Alexander Kanavin [this message]
2018-03-19 10:53 ` Marek Vasut
2018-03-19 10:53 ` Alexander Kanavin
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=5420e82b-7ca0-5dea-659c-208e26e5bc32@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--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