From: Thomas Kunze <thommycheck@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: kernel.bbclass and collie changes
Date: Fri, 25 Jul 2008 18:05:04 +0200 [thread overview]
Message-ID: <4889F9B0.5010103@gmx.de> (raw)
In-Reply-To: <20080725155551.GG4715@smtp.west.cox.net>
Tom Rini wrote:
> On Fri, Jul 25, 2008 at 10:09:04AM +0200, Andrea Adami wrote:
>
>>>> while you're there please weak-assign too:
>>>>
>>>> KERNEL_IMAGETYPE ?= "zImage"
>>>>
>>> Thats default set by kernel.bbclass
>>>
>> I meant in zaurus-2.6.inc
>>
>
> Er, isn't that at the level where you know what the board needs and do
> want to enforce build choices?
>
In theory yes. But if you replaced sharp bootloader with u-boot then you
need to change it.
But these changes can be done after the RFCed stuff is in.
next prev parent reply other threads:[~2008-07-25 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 23:56 RFC: kernel.bbclass and collie changes Thomas Kunze
2008-07-25 3:02 ` Tom Rini
2008-07-25 7:44 ` Andrea Adami
2008-07-25 7:56 ` Marcin Juszkiewicz
2008-07-25 8:09 ` Andrea Adami
2008-07-25 15:55 ` Tom Rini
2008-07-25 16:05 ` Thomas Kunze [this message]
2008-07-26 9:38 ` Phil Blundell
2008-07-26 9:48 ` Thomas Kunze
2008-07-26 10:40 ` Richard Purdie
2008-07-26 11:06 ` Thomas Kunze
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=4889F9B0.5010103@gmx.de \
--to=thommycheck@gmx.de \
--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