From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: What is task-base?
Date: Mon, 28 Aug 2006 11:31:30 +0200 [thread overview]
Message-ID: <200608281131.31893.openembedded@hrw.one.pl> (raw)
In-Reply-To: <1156715171.5536.60.camel@localhost.localdomain>
Dnia niedziela, 27 sierpnia 2006 23:46, Richard Purdie napisał:
> I've been asked to explain exactly what my last commits did. Basically,
> I broke us free from being tied to task-bootstrap by creating
> MACHINE_TASK_PROVIDER which you can set to the task-bootstrap like
> provider of your choice. It defaults to task-bootstrap so nothing
> changes in that respect.
I like that idea :) Will have to look at it and add to .oz354x branch so
it will be much easier to create working images for collie.
> Its not perfect yet but we needed to set the ball rolling somehow :)
I think that we lack "serial" in MACHINE_FEATURES - this would be needed
by "irda" feature but will be also useful for machines which have normal
serial (RS232/RS485) here we can put lrzsz.
"pcmcia" feature should recommend "serial", "bluetooth", "wifi" features
atleast. It also contain now hostap-cs without checking for "wifi".
"ext2" feature could be renamed to kind of "internal-storage" - most of
our supported devices use ext2 but not every of them has internal storage
with ext2.
"wifi" feature need some work too. There are machines which does not have
Prism based wifi cards (so no need for hostap-utils) or do not support
WPA (wpa-supplicant is not needed then). h4000 has internal wifi on
ACX100 chipset (iirc) so it need only wireless-tools to have it working
(chipset related packages should be listed in machine config).
--
JID: hrw-jabber.org
Palmtop: Sharp Zaurus C760
OpenEmbedded/OpenZaurus developer
Warning: Dates in calendar are closer than they appear.
next prev parent reply other threads:[~2006-08-28 9:33 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 [this message]
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
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=200608281131.31893.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 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.