From: "Mark Gollahon" <golly@stellarwerx.com>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: machine customized ixp4xx NPE firmware
Date: Wed, 16 May 2007 10:32:20 -0400 (EDT) [thread overview]
Message-ID: <1179325940.4167@gatekeeper.stellarwerx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Richard Purdie wrote ..
>
> 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
I want to second this approach as I tried awhile back to build OE for an IXP4XX-based machine that came into my possession and, during that time, ended up patching several IXP-specific .bb's to add my new machine. My work would have been much easier had IXPMACHINES existed.
(NOTE: I did get it almost completely working, the only problem ended up being the networking ports didn't work, which, for a firewall machine, meant the device was useless. There is an IC175 switch chip sitting between the IXP's two network ports and the physical ports and I couldn't figure out how to hack the IXP net driver to get the IC175 to pass eth frames.)
Regards,
-Mark Gollahon
next reply other threads:[~2007-05-16 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 14:32 Mark Gollahon [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=1179325940.4167@gatekeeper.stellarwerx.com \
--to=golly@stellarwerx.com \
--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 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.