public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Mike at VirginNet" <mister.chips@virgin.net>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] building RedBoot for a PC with an NIC other than 82559 or 82544
Date: Mon, 08 Dec 2003 13:24:00 -0000	[thread overview]
Message-ID: <002601c3bd8e$73032ee0$93456551@imaging> (raw)
In-Reply-To: <m3llpnd2gx.fsf@miso.calivar.com>

Hi,

I have been trying to introduce the eCos 21443 ethernet driver into the PC
build of RedBoot.  I tried working on the config of the RedBoot package in
configtool, but there doesn't seem to be a mechanism for importing an
existing device driver into a platform.

I can imagine that there may well be some tailoring of the source code
necessary, given that the 21143 driver was presumably not developed for a pc
target.  But there doesn't seem to be a defined process for it.

Also I have picked up the NE2000 driver which was posted some time back, and
I've 'added' it to the i386 driver set, but there is no instruction on how
to add it to the pc platform. Presumably the same instructions will apply
here.

Cheers,

Mike






---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 22/10/03


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-12-08 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08  5:30 [ECOS] [Fwd: Re: [ECOS] Eathernet support] Giri
2003-12-08 10:02 ` Mike at VirginNet
2003-12-08 10:32   ` Nick Garnett
2003-12-08 13:24     ` Mike at VirginNet [this message]
2003-12-08 13:50       ` [ECOS] building RedBoot for a PC with an NIC other than 82559 or 82544 Nick Garnett
2003-12-08 15:58         ` Mike at VirginNet
2003-12-08 16:06           ` Eric Doenges
2003-12-08 16:10           ` Nick Garnett
2003-12-09 17:52             ` Mike at VirginNet
2003-12-10  7:25               ` Eric Doenges

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='002601c3bd8e$73032ee0$93456551@imaging' \
    --to=mister.chips@virgin.net \
    --cc=ecos-discuss@sources.redhat.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).