Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: machine customized ixp4xx NPE firmware
Date: Wed, 16 May 2007 10:54:07 +0930	[thread overview]
Message-ID: <464A5D37.4030401@whitby.id.au> (raw)
In-Reply-To: <200705151322.39110.robin.farine@terminus.org>

Robin Farine wrote:
> The platform I am working on is using NPE-B and NPE-C as Ethernet
> interfaces. The ixp4xx-npe package from the OE snapshot I am 
> currently
> using builds firmware for NPE-B only and the firmware type is 
> hard-coded
> in "IxNpeMicrocode.h".
> 
> The patch below proposes a means of letting the machine 
> configuration file
> decide which NPE firmware to build.

Thanks.  We'll be very happy to apply that patch.  I'll take a close
look at it tonight.

> 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.

-- Rod



  parent reply	other threads:[~2007-05-16  1:26 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 [this message]
2007-05-16  8:56   ` Robin Farine
2007-05-16 10:44   ` Richard Purdie
  -- 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=464A5D37.4030401@whitby.id.au \
    --to=rod@whitby.id.au \
    --cc=openembedded-devel@lists.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