From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: machine customized ixp4xx NPE firmware
Date: Wed, 16 May 2007 11:44:45 +0100 [thread overview]
Message-ID: <1179312285.5854.2.camel@localhost.localdomain> (raw)
In-Reply-To: <464A5D37.4030401@whitby.id.au>
On Wed, 2007-05-16 at 10:54 +0930, Rod Whitby wrote:
> Robin Farine wrote:
> > Another but somewhat related point is the COMPATIBLE_MACHINE
> > variable. If
> > my machine's name does not start with nslug or ixp4xx, I am forced
> > to
> > change many package recipes (I suspect it is a FAQ but I do not seem
> > to
> > able to access the mailing-list archive at the moment), perhaps a
> > COMPATIBLE_ARCH variable would be help here ?
>
> Which machine/arch are you using? We can easily extend that
> compatibility to include any other machines/archs that will use it.
A neat way to handle this might be to define:
IXPMACHINES = "nslu2|ixp4xx|whatever"
and then the ixp specific .bb's check IXPMACHINES rather than a specific
list. The list would then be maintained in one place and is easily
updated if anyone adds a new ixp like machine.
I've not looked at the specifics, its just a random idea I had...
Cheers,
Richard
next prev parent reply other threads:[~2007-05-16 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 11:22 RFC: machine customized ixp4xx NPE firmware Robin Farine
2007-05-15 18:38 ` Leon Woestenberg
2007-05-15 20:17 ` Robin Farine
2007-05-16 1:24 ` Rod Whitby
2007-05-16 8:56 ` Robin Farine
2007-05-16 10:44 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-16 14:32 Mark Gollahon
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=1179312285.5854.2.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox