From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: What is task-base?
Date: Mon, 16 Oct 2006 08:17:46 +0100 [thread overview]
Message-ID: <1160983066.5565.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1160951360.8144.2.camel@lieve>
On Mon, 2006-10-16 at 00:29 +0200, Koen Kooi wrote:
> Op ma, 16-10-2006 te 01:02 +0300, schreef Paul Sokolovsky:
>
> > If it can be made so clean, why do we have so tangled configs for
> > many machines, at least for PocketPC-based?
>
> Historical reason, and we'd welcome a cleanup
Agreed.
> > For example, I doubt it's good idea to have IMAGE_FSTYPES
> > in machine configs - how that can be machine's property?
>
> Some bootloaders can be quite demanding, like the one for the spitz
> machine only likes tar.gz, not tar.bz2. It should be overridable,
> though.
Most of the Zaurus machines set that and its valid as the image type is
the one supported by the bootloader. Its not something I'd recommend in
general but makes sense there. (tar.gz for spitz, jffs2 for c7x0,
poodle, akita). After the machine sets it the distro and/or the user in
local.conf is free to alter or probably best of all append to the
variable.
Richard
prev parent reply other threads:[~2006-10-16 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 21:46 What is task-base? Richard Purdie
2006-08-28 9:31 ` Marcin Juszkiewicz
2006-08-28 9:40 ` Koen Kooi
2006-09-01 14:18 ` Koen Kooi
2006-09-01 15:06 ` pHilipp Zabel
2006-09-27 12:27 ` Koen Kooi
2006-09-27 16:49 ` pHilipp Zabel
2006-09-27 17:01 ` Koen Kooi
2006-09-01 14:56 ` pHilipp Zabel
2006-09-01 15:10 ` Koen Kooi
2006-10-15 13:44 ` Marcin Juszkiewicz
2006-10-15 22:02 ` Paul Sokolovsky
2006-10-15 22:29 ` Koen Kooi
2006-10-16 2:24 ` Paul Sokolovsky
2006-10-16 7:17 ` Richard Purdie [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=1160983066.5565.3.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--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 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.