From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev linux 2.6.22: Alix boards use bzImage kernels
Date: Mon, 20 Aug 2007 14:12:17 +0200 [thread overview]
Message-ID: <200708201412.18032.openembedded@hrw.one.pl> (raw)
In-Reply-To: <46C97EFE.2080007@dominion.kabel.utwente.nl>
Dnia poniedziałek, 20 sierpnia 2007, Koen Kooi napisał:
> Marcin Juszkiewicz schreef:
> > Dnia wtorek, 7 sierpnia 2007, Richard Purdie napisał:
> >> On Tue, 2007-08-07 at 15:56 +0200, hrw commit wrote:
> > Right - I looked at it and prepared patch. It removes
> > KERNEL_IMAGETYPE = "zImage" entries from kernel recipes and also sets
> > this variable into bzImage for x86 machines which already use that
> > type of kernels. Rest of machines are untouched (yet) - I can convert
> > them if we reach consensus about it.
> What about poking machine maintainer to start using linux.inc direcly
> as well instead of duplicating it?
Some parts of linux.inc stuff should probably go into kernel.bbclass so we
will get it included in all kernel recipes. Things like EABI/OABI
automagic for ARM, creating of archive with kernel modules are nice
addons.
But linux.inc is another thing then KERNEL_IMAGETYPE cleanup. But I have
to admit that I missed it during first part of cleaning.
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
I don't know what your problem is, but I'll bet it's hard to pronounce.
next prev parent reply other threads:[~2007-08-20 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1IIPXa-0005bT-C3@linuxtogo.org>
2007-08-07 15:16 ` [oe-commits] org.oe.dev linux 2.6.22: Alix boards use bzImage kernels Richard Purdie
2007-08-20 11:32 ` Marcin Juszkiewicz
2007-08-20 11:46 ` Koen Kooi
2007-08-20 12:12 ` Marcin Juszkiewicz [this message]
2007-08-20 13:43 ` Richard Purdie
2007-08-22 16:16 ` Marcin Juszkiewicz
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=200708201412.18032.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--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