Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Cc: angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] [RFC] Get rid of adhoc machine-specific	messing with kernel packages
Date: Thu, 28 Dec 2006 20:32:26 +0000	[thread overview]
Message-ID: <1167337946.5596.77.camel@localhost.localdomain> (raw)
In-Reply-To: <459403F2.4080102@dominion.kabel.utwente.nl>

On Thu, 2006-12-28 at 18:50 +0100, Koen Kooi wrote:
> Paul Sokolovsky schreef:
> > Hello angstrom-distro-devel,
> > 
> >   Thanks for providing pre-holiday 20061219 snapshots for testing.
> > They don't provide separate zImages, but well, that's ok - they are in
> > the images, after all.
> > 
> >   Well, not for hx4700, for example. Because:
> > 
> > ======== linux-handhelds-2.6.inc =====
> > FILES_kernel-image_hx4700 = ""
> > ALLOW_EMPTY_hx4700 = "1"
> > FILES_kernel-image_htcuniversal = ""
> > ALLOW_EMPTY_htcuniversal = "1"
> > ======================================
> > 
> >   Oops. Sources of such a special treatment of hx4700 and htcuniversal
> > would be unclear to outsider, but people who deal with (mis)features
> > of "ipaqs" know, that hx4700 has one (sic!, even if the most popular)
> > bootloader which doesn't use zImage in the image, but instead requires
> > adhoc means to install kernel, ditto for Universal, though bootloader
> > is another.
> > 
> >   So, what is tried here is to "save space". But there're few issues:
> 
> Those lines should go, but not before we have a way to exclude 'kernel-image' from the
> rootfs *and* kernel-module-foo doesn't depend kernel-image anymore.

The accepted approach is to make the kernel-image file empty which
solves both those problems. This is the same as the Zaurus which also
requires an external zImage file (and this code is handled in
linux-rp.inc in the same way as the above but for all machines).

Arguably, the machine files should perhaps set this...

The only other solution probably involves a nasty anonymous function
acting on a setting of EXTERNAL_KERNEL_IMAGE = "1" in kernel.bbclass.

Richard




  reply	other threads:[~2006-12-28 20:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53610736.20061228191750@gmail.com>
2006-12-28 17:50 ` [Angstrom-devel] [RFC] Get rid of adhoc machine-specific messing with kernel packages Koen Kooi
2006-12-28 20:32   ` Richard Purdie [this message]
2006-12-29  2:05     ` Paul Sokolovsky
2006-12-29 11:34       ` Richard Purdie
2007-01-04 19:03         ` [Angstrom-devel] [RFC] Get rid of adhoc machine-specific messing with [linux-handhelds-2.6] " Paul Sokolovsky
2007-01-04 20:55           ` Richard Purdie
2007-01-04 21:22             ` Koen Kooi
2007-01-04 21:33               ` Richard Purdie
2007-01-04 21:38             ` Paul Sokolovsky
2007-01-05  8:41           ` Marcin Juszkiewicz
2007-01-05  9:15             ` Koen Kooi
2007-01-05 10:15               ` pHilipp Zabel
2007-01-06 10:26             ` Paul Sokolovsky
2006-12-29  1:30   ` [Angstrom-devel] [RFC] Get rid of adhoc machine-specific messing with " Paul Sokolovsky

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=1167337946.5596.77.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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