From: Martyn Welch <martyn.welch@ge.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: u-boot ready initrds
Date: Tue, 09 Mar 2010 16:09:27 +0000 [thread overview]
Message-ID: <4B9672B7.2030204@ge.com> (raw)
In-Reply-To: <1268071514.16526.6.camel@trini-m4400>
Tom Rini wrote:
> On Mon, 2010-03-08 at 08:43 +0100, Steffen Sledz wrote:
>
>> Steffen Sledz wrote:
>>
>>> Initrds need to be prepared with mkimage to be usable from u-boot.
>>> The following patch introduces an additional IMAGE_FSTYPE .cpio.gz.u-boot
>>> for this (at the moment just for hipox machine).
>>>
>>> Is this the way it should be done?
>>>
>>> Should this better become part of conf/bitbake.conf?
>>>
>> Ping
>>
>
> I don't know why patchwork didn't see this. That said, mkimage -A arm
> is bad. UBOOT_ARCH is right, and comes from kernel-arch.bbclass. So, I
> think a full patch would need to add in changes to image.bbclass to
> inherit kernel-arch so that UBOOT_ARCH will be evaluated.
>
> And yes, this I think should be in bitbake.conf with the rest of the
> image magics
>
We'd like to see this as well. We have a class which we inherit to do
the same thing that I have been meaning to try and push, but this is a
much better way of doing it.
Martyn
--
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms | Wales (3828642) at 100
T +44(0)127322748 | Barbirolli Square, Manchester,
E martyn.welch@ge.com | M2 3AB VAT:GB 927559189
prev parent reply other threads:[~2010-03-09 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 13:18 u-boot ready initrds Steffen Sledz
2010-03-03 13:20 ` [PATCH] hipox: introducing IMAGE_FSTYPES cpio.gz.u-boot for hipox machine Steffen Sledz
2010-03-08 7:43 ` u-boot ready initrds Steffen Sledz
2010-03-08 18:05 ` Tom Rini
2010-03-09 14:41 ` Steffen Sledz
2010-03-09 17:47 ` Tom Rini
2010-03-10 9:30 ` [PATCH] bitbake.conf: introducing new image fstype .cpio.gz.u-boot Steffen Sledz
2010-03-10 13:20 ` Steffen Sledz
2010-03-10 13:29 ` Martyn Welch
2010-03-10 15:09 ` Tom Rini
2010-03-10 15:59 ` Steffen Sledz
2010-03-09 16:09 ` Martyn Welch [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=4B9672B7.2030204@ge.com \
--to=martyn.welch@ge.com \
--cc=openembedded-devel@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