From: Tony Breeds <tony@bakeyournoodle.com>
To: "Calin A. Culianu" <calin@ajvar.org>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: Stupid question re: register_cdrom()
Date: Tue, 6 Apr 2004 07:03:51 +0800 [thread overview]
Message-ID: <20040405230351.GR3445@bakeyournoodle.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0404051649510.16268-100000@rtlab.med.cornell.edu>
On Mon, Apr 05, 2004 at 04:53:16PM -0400, Calin A. Culianu wrote:
>
> Let's say I was coding a cdrom emulator in software for kernel 2.4. I
> am unclear about register_cdrom(). Does register_cdrom() in
> cdrom.c take care of telling the kernel that my kdev_t major/minor
> combination in fact leads to a real driver? Or do I need to take care of
> that outside of regsiter_cdrom()?
>
> If not.. how do I tell the kernel data structures that my driver's major
> number does in fact point to a cdrom driver. Basically, I want my
> driver's major number to show up in /proc/devices..
>
> This might be a stupid question, but I am not a linux kernel expert...
Neither am I, therefore I hope you get a reply from someone else
refuting or acknowledging my claims.
I looks to me that the code that does the actual registration of the
driver is in drivers/ide/ide-cd.c NOT cdrom.c. Specifically
ide_cdrom_attach(). Said function eventually calls the register_cdrom()
you ask about.
For writing a cdrom emulator You may want to look more closely at the
non-IDE/SCSI devices as they seem to register their driver data
themselves I had a quick read of aztcd.c, I think between cdrom.c and
aztcd.c you should be able to piece together what you want.
Also Try reading http://www.xml.com/ldd/chapter/book/ for details on 2.4
drivers
Yours Tony
linux.conf.au http://lca2005.linux.org.au/
Apr 18-23 2005 The Australian Linux Technical Conference!
next prev parent reply other threads:[~2004-04-05 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 20:53 Calin A. Culianu
2004-04-05 23:03 ` Tony Breeds [this message]
2004-04-06 3:03 ` Calin A. Culianu
2004-04-06 18:45 ` Calin A. Culianu
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=20040405230351.GR3445@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=calin@ajvar.org \
--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
all inboxes | Powered by JetHome®