public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Documentation for new Ethernet driver interface?
Date: Mon, 11 Dec 2000 13:22:00 -0000	[thread overview]
Message-ID: <20001211152555.A3841@visi.com> (raw)
In-Reply-To: <20001211125100.A3361@visi.com>

> I'm trying to get my Ethernet driver that works with 1.3.1 to
> work with CVS code, but I can't seem to find any documentation
> on the new Ethernet driver interface.  Can somebody lend me a
> clue?

A few specific questions (based on my perusal of the edb7xxx
driver):

1) The DSR that is called now seems to be a generic Ethernet
   DSR which then arranges for a future call to the "deliver"
   callback pointing to what used to be the driver DSR.

   The "deliver" callback is called from a thread context
   rather than a DSR context.
   
   Right?

2) What is the "poll" callback in ETH_DRV_SC for?  It seems to
   do almost the exact same thing that the deliver callback
   does.

3) What is done with the return value from the int_vector
   callback?  My driver uses three different interrupts, and
   I'm not sure which one to put here.  I'm guessing it's the
   interrupt number for the interrupt that calls the DSR that
   does mostly the same thing as the "deliver" callback?

4) The poll() and int_vector() callbacks seem not to be unused
   in "net/eth_drv.c" and are used only in stand_alone/eth_drv.c.
   Can I just put in stubs that do nothing for those two?

-- 
Grant Edwards
grante@visi.com

  reply	other threads:[~2000-12-11 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-11 10:48 Grant Edwards
2000-12-11 13:22 ` Grant Edwards [this message]
2000-12-11 13:49   ` Gary Thomas
2000-12-11 14:05     ` Grant Edwards

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=20001211152555.A3841@visi.com \
    --to=grante@visi.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).