public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Trenton D. Adams" <tadams@extremeeng.com>
To: "'eCos'" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] eth device drivers
Date: Wed, 13 Jun 2001 10:07:00 -0000	[thread overview]
Message-ID: <000d01c0f42a$cfb39330$090110ac@BURN> (raw)

I'm a little confused about writing device drivers for a wireless
modem/network card.

Do I have to write a driver for the actual modem, and one for the
network portion of it, or should it all be integrated into one?  Right
now I'm looking at "devs\eth\arm\edb7xxx\current\src\if_edb7xxx.c".  It
looks to me like it's the only driver file for that network device.  Is
this correct?

How do I go about understanding the driver?  For instance, what good
does it do to go

NETDEVTAB_ENTRY (edb7xxx_netdev, "edb7xxx", edb7xxx_cs8900_init,
&edb7xxx_sc);
???

Doesn't that device tab entry have to be put inside a table somewhere in
the kernel in order for the kernel to access it, or to even know it's
there?  Or does the CYG_HAL_TABLE_ENTRY part of the macro create a
string that "make" somehow parses, and automatically puts the entry into
an array somewhere in the kernel as it's being made and compiled?


Does ETH_DRV_SC create the edb7xxx_sc variable used by NETDEVTAB_ENTRY?
That's what it looks like in the eCos sources.  Is there documentation
for all this stuff, or does everyone have to look through the source
like me?  It would be nice to just have docs that say something like
"ETH_DRV_SC creates a structured vairable of the type 'eth_hwr_funs' and
fills it with all the function names, etc".  

With documentation like that, I wouldn't care about what the MACROS were
doing, I would just use them.


             reply	other threads:[~2001-06-13 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 10:07 Trenton D. Adams [this message]
2001-06-14 14:13 ` Jonathan Larmour
2001-06-14 14:41   ` Trenton D. Adams
2001-06-14 15:47     ` Jonathan Larmour
2001-06-13 23:51 rob.wj.jansen

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='000d01c0f42a$cfb39330$090110ac@BURN' \
    --to=tadams@extremeeng.com \
    --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).