From: corbet@lwn.net (Jonathan Corbet)
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about creating char device in 2.4
Date: Wed, 05 Feb 2003 15:32:56 -0700 [thread overview]
Message-ID: <20030205223256.17078.qmail@eklektix.com> (raw)
In-Reply-To: Your message of "Wed, 05 Feb 2003 17:03:30 EST." <3E418A32.2010308@nortelnetworks.com>
> How would you go about hooking in to the 2.4 char device code to do
> something equivalent?
Linux Device Drivers has a great deal of discussion on portability between
2.2 and 2.4; it also has example code which could be easily adapted to
create your "finite capacity bit bucket" device. It's available online at
http://www.xml.com/ldd/chapter/book/index.html, but, of course, you'll want
to go and buy at least three copies for your desk...
jon
Jonathan Corbet
Executive editor, LWN.net
corbet@lwn.net
prev parent reply other threads:[~2003-02-05 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 22:03 question about creating char device in 2.4 Chris Friesen
2003-02-05 22:32 ` Jonathan Corbet [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=20030205223256.17078.qmail@eklektix.com \
--to=corbet@lwn.net \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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