From: Mark Salter <msalter@redhat.com>
To: vijay.peshkar@wipro.com
Cc: jerzy.dyrda@kontron.pl, ecos-discuss@ecos.sourceware.org
Subject: RE: [ECOS] ixp42x NPE networking build issue.
Date: Tue, 18 Jul 2006 14:22:00 -0000 [thread overview]
Message-ID: <1153232538.10300.7.camel@sadr.localdomain> (raw)
In-Reply-To: <D6DA3A176076B2408E53467FC0B0056B0370D1DF@BLR-EC-MBX04.wipro.com>
On Tue, 2006-07-18 at 09:13 +0530, vijay.peshkar@wipro.com wrote:
> The intel site no longer maintains redboot for IXP425. Its all 2800 now.
http://developer.intel.com/design/network/products/npfamily/ixp425swr1.htm
After registration/login you can get to the NPE driver code (eCos .epk)
and microcode. The same driver works for all IXP4xx family. It is a
RedBoot-only driver, but I may have an opportunity to add interrupt
support (Jerzy did this for an earlier version) to the official Intel
package in the near future.
--Mark
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-07-18 14:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 3:44 vijay.peshkar
2006-07-18 14:22 ` Mark Salter [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 5:59 sumanth
2006-07-26 14:57 ` Mark Salter
2006-08-01 13:15 ` sumanth
2006-08-01 15:34 ` Mark Salter
2006-07-20 10:29 vijay.peshkar
2006-07-20 13:36 ` Mark Salter
2006-07-17 5:40 vijay.peshkar
2005-12-28 16:56 Karel Gardas
2005-12-28 17:10 ` Andrew Lunn
2005-12-28 17:15 ` Mark Salter
2005-12-28 18:35 ` Karel Gardas
2005-12-28 20:39 ` Karel Gardas
2005-12-28 21:05 ` Mark Salter
2005-12-28 21:14 ` Karel Gardas
2005-12-28 21:31 ` Andrew Lunn
2005-12-28 21:51 ` Karel Gardas
2005-12-28 22:00 ` Mark Salter
2006-01-09 10:07 ` jerzy dyrda
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=1153232538.10300.7.camel@sadr.localdomain \
--to=msalter@redhat.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jerzy.dyrda@kontron.pl \
--cc=vijay.peshkar@wipro.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).