public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Doenges <Eric.Doenges@DynaPel.com>
To: Mike at VirginNet <mister.chips@virgin.net>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] building RedBoot for a PC with an NIC other than 82559 or 82544
Date: Wed, 10 Dec 2003 07:25:00 -0000	[thread overview]
Message-ID: <3FD6CA76.8030106@DynaPel.com> (raw)
In-Reply-To: <00fa01c3be7c$f9719ae0$db516251@imaging>

Mike at VirginNet wrote:

[ ... ]

> If there is something in the documentation that covers the procedure for
> adding hardware support - and thus describes what I need to do - then please
> point me at it.

I don't think there is any 'official' documentation for this. Here is an
excerpt from the RealTek 8139 driver (see
<...>/packages/devs/eth/rltk/8139/current/doc/README for the full text):

<--- SNIP --->

This driver follows the customization model used by many other drivers
to separate those parts of the code that are device specific from those
that are platform specific by requiring two packages to actually use the
driver -- the driver itself and a platform glue package that contains
only a .cdl and an .inl file (see the devs/i386/pc/rltk8139 package for
an example).

Both the driver and the glue packages must be added to the package
database before you can use them. My entries look like this:

package CYGPKG_DEVS_ETH_RLTK_8139 {
   alias     { "RealTek 8139 ethernet driver"
               devs_eth_rltk_8139 8139_eth_driver }
   hardware
   directory devs/eth/rltk/8139
   script    rltk_8139_eth_drivers.cdl
         description     "Ethernet driver for RealTek 8139 NIC."
}

and

package CYGPKG_DEVS_ETH_I386_RLTK8139 {
   alias     { "Standard PC with RealTek 8139 ethernet device"
               devs_eth_i386_pc_rltk8139 }
   hardware
   directory devs/eth/i386/pc/rltk8139
   script    i386_pc_rltk8139_eth_drivers.cdl
   description "Ethernet driver for the RealTek 8139 family of chips."
}

Finally, you will need to create a new target that includes the RealTek
driver. The easiest way to this is copy an existing target and add the
two packages defined above (and removing the Intel 82259 packages in case
of an i386 pc target).

<--- SNIP --->

Basically, you should take a look at how other drivers are integrated
with specific targets - I recommend looking at the Intel 82559 and
the 16550 UART drivers for examples (or the RealTek driver mentioned
above).
-- 
--------------------------------------------------------------------
|     Eric Doenges              |     DynaPel Laboratories GmbH    |
|     Tel: +49 89 962428 23     |     Fraunhoferstrasse 9/2        |
|     Fax: +49 89 962428 90     |     D - 85737 Ismaning, Germany  |
--------------------------------------------------------------------


-- 
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-10  7:25 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     ` [ECOS] building RedBoot for a PC with an NIC other than 82559 or 82544 Mike at VirginNet
2003-12-08 13:50       ` 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 [this message]

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=3FD6CA76.8030106@DynaPel.com \
    --to=eric.doenges@dynapel.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=mister.chips@virgin.net \
    /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).