[oe] What is task-base?

pHilipp Zabel philipp.zabel at gmail.com
Wed Sep 27 16:49:41 UTC 2006


On 9/27/06, Koen Kooi <koen at dominion.kabel.utwente.nl> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> pHilipp Zabel schreef:
> > On 9/1/06, Koen Kooi <koen at dominion.kabel.utwente.nl> wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Koen Kooi schreef:
> >>> Marcin Juszkiewicz schreef:
> >>> <snip>
> >>>
> >>>
> >>>>> "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).
> >>> Which leads to the question: "how should they be listed?". At the moment a lot of machines
> >>> just put those modules in BOOTSTRAP_*, which isn't going to work for things that don't use
> >>> task-bootstrap (the Ångström distribution for example). A few weeks ago I introduced the
> >>> 'BOOT_MODULES' variable for that, should we add that to all machines, or is there a nicer
> >>> way to do that?
> >> And I ask again, before wasting my time implementing it: "should we add that to all
> >> machines, or is there a nicer way to do that?"
> >
> > I wonder if this shouldn't be modularized a bit, the modules could be
> > assigned to different base tasks. The ipaq-pxa270.conf puts the
> > following modules into BOOTMODULES_RRECOMMENDS currently:
> >
> > PXA270_MODULES = "g_ether g_file_storage g_serial gadgetfs pxa27x_udc \
> >                   snd_pcm_oss snd_mixer_oss evdev mmc_block pcmcia hidp \
> >                   nls_cp437 nls_iso8859-1 nls_utf8 af_key"
> > HX4700_MODULES = "i2c-pxa hx4700_voltage acx hx4700_acx snd_hx4700_audio"
> >
> > g_ether, g_file_storage, g_serial and gadgetfs are already in
> > task-base-usbgadget-rrecommends.
> > snd_pcm_oss and snd_mixer_oss are in task-base-alsa-rrecommends.
> > hidp is in task-base-bluetooth-rrecommends
> >
> > This leaves us with
> >
> > pxa27x_udc evdev mmc_block pcmcia nls_cp437 nls_iso8859-1 nls_utf8 af_key
> > i2c-pxa hx4700_voltage acx hx4700_acx snd_hx4700_audio
> >
> > I propose to put pxa27x_udc in task-base-usbgadget-rrecommends (similar to
> > task-base-irda-rrecommends containing kernel-module-pxaficp-ir).
> > But what about the rest?
>
> Yes, what about the rest?

kernel-module-pxa27x_udc: task-base-usbgadget-rrecommends
kernel-module-pcmcia: task-base-pcmcia-rrecommends

Compile in evdev, mmc_block, i2c-pxa and af_key and be done with it?

kernel modules could rrecommend evdev if it was
compiled as a module, same goes for mmc_block
(let pxamci and asic3_mmc rrecommend it) and i2c-pxa.

kernel-module-pcmcia: task-base-pcmcia-rrecommends

regards
Philipp




More information about the Openembedded-devel mailing list