From: Jamie Lenehan <lenehan@twibble.org>
To: Marcin Juszkiewicz <openembedded@hrw.one.pl>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: handling of machine/distro features stuff
Date: Mon, 30 Oct 2006 09:10:06 +1100 [thread overview]
Message-ID: <20061029221005.GA27629@twibble.org> (raw)
In-Reply-To: <200610291528.40663.openembedded@hrw.one.pl>
On Sun, Oct 29, 2006 at 03:28:39PM +0100, Marcin Juszkiewicz wrote:
>
> Currently OpenEmbedded use overrides based on DISTRO, MACHINE, TARGET_ARCH
> and few others. I want to suggest start of using also
> {MACHINE,DISTRO}_FEATURES because we have some stuff in metadata which
> make sense only on some targets only - for example madwifi is limited to
> PCI devices only.
In general that sounds reasonable.
I've also run into problems before with things that depend on PCMCIA
which I don't have built into any of my kernels.
If you are going to do this it might be nice to make pci and mini-pci
separate features, since I don't want to build loads of pci device
and driver related stuff when my target devices only have mini-pci.
All my current mad-wifi cards for here are mini-pci.
[...]
> I remove madwifi stuff from wpa-supplicant recipe then I will get working
> version. But this cannot be pushed back into repo because NSLU2 related
> distros want version with madwifi support.
Yep. I need madwifi support in wpa-supplicant for my router distro
and associated target devices as well.
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2006-10-29 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 14:28 RFC: handling of machine/distro features stuff Marcin Juszkiewicz
2006-10-29 22:10 ` Jamie Lenehan [this message]
2006-10-30 1:32 ` Justin Patrin
2006-11-04 13:37 ` Leon Woestenberg
2006-11-17 0:01 ` Marcin Juszkiewicz
2006-11-17 9:25 ` Richard Purdie
2006-11-24 16:03 ` Marcin Juszkiewicz
2006-11-24 17:56 ` 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=20061029221005.GA27629@twibble.org \
--to=lenehan@twibble.org \
--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 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.