From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 3/4] beagleboard: upgrade the kernel to 3.10.x
Date: Tue, 10 Sep 2013 11:18:34 -0400 [thread overview]
Message-ID: <522F384A.4070702@windriver.com> (raw)
In-Reply-To: <20130910083634.GB5871@ad.chargestorm.se>
On 13-09-10 04:36 AM, Anders Darander wrote:
> * Bruce Ashfield <bruce.ashfield@windriver.com> [130910 10:16]:
>
>> On 13-09-10 04:08 AM, Anders Darander wrote:
>>> * Bruce Ashfield <bruce.ashfield@windriver.com> [130906 22:59]:
>>>> From: Liming Wang <liming.wang@windriver.com>
>
>>>> In 3.10.x linux kernel, uImage can't be compiled by default. But zImage
>>>> has been supported by the latest u-boot, so use zImage as the default kernel
>>>> image file. In u-boot command, use "bootz", instead of "bootm", to boot the kernel.
>
>>> NAK. (At least based on the info given above regarding the uImage to
>>> zImage transfer).
>
>>> I missed this patch earlier...
>
>>> What's the issue with uImage on 3.10.x?
>>> I'm running a kernel.org 3.10.x using linux-yocto-custom just fine here
>>> (although for another board).
>
>>> I suspect the issue (that I guess Liming had), is due to the powerpc
>>> being mixed into his build. (Bruce replied on the oe-core list to a
>>> path which corrected the path to the DTS).
>
>> No, that wasn't the issue. uImage requires a LOADADDR in many cases and
>> that isn't currently encoded in the machine configs.
>
> Ah, ok. Then I'll obviously redraw my NAK-wishes for this patch.
>
> I think the reason that uImage can't be compiled should have been stated
> in the commit log, though. If for nothing else, just to make it clear to
> everyone that there's no general uImage issue; rather an issue with the
> specific board setup.
We can do that. I also re-opened the bugzilla so it can be used for making
sure this is clear.
Bruce
>
> Cheers,
> Anders
>
>> zImage works fine, want to expand our coverage with the reference boards,
>> so no, there's no NAK of this. It's fine as is.
>
>> Other layers and BSPs are free to use uImage, just as this reference
>> is free to use the zImage.
>
>
next prev parent reply other threads:[~2013-09-10 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 20:58 [PATCH 0/4] meta-yocto-bsp: 3.10 updates Bruce Ashfield
2013-09-06 20:58 ` [PATCH 1/4] mpc8315e-rdb: update to the 3.10 kernel Bruce Ashfield
2013-09-06 20:58 ` [PATCH 2/4] meta-yocto-bsp: update h/w reference boards SRCREVs Bruce Ashfield
2013-09-06 20:58 ` [PATCH 3/4] beagleboard: upgrade the kernel to 3.10.x Bruce Ashfield
2013-09-10 8:08 ` Anders Darander
2013-09-10 8:16 ` Bruce Ashfield
2013-09-10 8:22 ` Bruce Ashfield
2013-09-10 8:36 ` Anders Darander
2013-09-10 15:18 ` Bruce Ashfield [this message]
2013-09-06 20:58 ` [PATCH 4/4] linux-yocto/3.10: update meta SRCREV for beagleboard config changes Bruce Ashfield
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=522F384A.4070702@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.