netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hendrik Wiese <7.e.Q@syncro-community.de>
To: netdev@oss.sgi.com
Subject: VME IP Driver Development - some questions
Date: Tue, 16 Nov 2004 08:44:52 +0100	[thread overview]
Message-ID: <4199AFF4.60407@syncro-community.de> (raw)

Hello,

I have got some questions about driver development on Linux 2.6:

Is there somebody who can explain, what is meant with wait_event and 
wake_up? Does it mean,
when I run "ifconfig", and the driver says "wait_event", is "ifconfig" 
blocked until my driver which
is continuing his work says "wake_up"? Have I explained this correctly?

If I give wait_event a condition, is it right that the driver continues 
its work and ifconfig is
blocked until the driver does something that sets this condition true?

Something else: we need a driver, which establishes an IP layer on top 
of the VME bus
to transfer data via a network device (called dpn). On the other side 
this driver must be
able to communicate with passive modules inside the vme-rack by polling 
their shared
memory for data.

Is it possible to create two kernel modules which run with the same 
hardware? One
module for the communication with the active VME modules via IP and 
another one
for the communication with the passive VME modules by polling their 
shared memory?

Many questions, I know. But I am an absolute newbie in driver 
development. And I
hope you can help me.

If somebody knows a source of informations regarding this topic, which 
is held in
german, please tell me.

Thanks a lot

kind regards
Hendrik (Germany)

             reply	other threads:[~2004-11-16  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16  7:44 Hendrik Wiese [this message]
2004-11-19  6:28 ` MOD_[INC|DEC]_USE_COUNT & Kernel 2.6 Hendrik Wiese

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=4199AFF4.60407@syncro-community.de \
    --to=7.e.q@syncro-community.de \
    --cc=netdev@oss.sgi.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 NNTP newsgroup(s).