From: Paul Sokolovsky <pmiscml@gmail.com>
To: Marcin Juszkiewicz <openembedded@hrw.one.pl>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: MACHINE_ namespace
Date: Sun, 27 May 2007 22:28:20 +0300 [thread overview]
Message-ID: <277782266.20070527222820@gmail.com> (raw)
In-Reply-To: <200705271638.03886.openembedded@hrw.one.pl>
Hello Marcin,
Sunday, May 27, 2007, 5:38:03 PM, you wrote:
> During usage of progear device (now packed due to lack of space) I found
> a problems related to how we use machine configs and X11.
> 1. We have "alsa" as one of machine features but no way to control kernel
> modules for it - all are added into machine config as
> MACHINE_EXTRA_RRECOMMENDS. Same goes to other features.
> 2. Progear device use X.org instead of KDrive so I had to create own
> images for it because by default we do not have a way to tell which X
> drivers need to be present in images.
> Proposed solution is adding MACHINE_ namespaces:
> MACHINE_KERNEL_ALSA = "kernel-module-snd-ali5451"
> MACHINE_KERNEL_PCMCIA = "kernel-module-yenta-socket"
This sounds good, especially if we anticipate from the start
that there may be several modules there. And generally, we need to add
more modules into task-base subtasks, targetting at aim when machine
configs will truly contain only machine-specific bits (like hardware
drivers), while other modules will be in task-base.
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
prev parent reply other threads:[~2007-05-27 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 14:38 RFC: MACHINE_ namespace Marcin Juszkiewicz
2007-05-27 15:39 ` Koen Kooi
2007-05-27 19:28 ` Paul Sokolovsky [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=277782266.20070527222820@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded@hrw.one.pl \
/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