public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <james@spunkysoftware.com>
To: <linux-kernel@vger.kernel.org>
Subject: Creative 4-speed CDROM driver
Date: Tue, 29 May 2001 05:22:55 +0100	[thread overview]
Message-ID: <016601c0e7f7$0c7c8780$c1a5fea9@spunky> (raw)

Hello Kernel Hackers,

Bloody Minix doesn't have a CDROM driver for my CDROM, a Creative Quad
speed. I'm dual booting between Linux and Minix. Linux uses my CDROM no
problems. I am thinking a "generic" CDROM driver might fit the bill for this
CDROM (the system is an old 486DX2/66, 20MB RAM, 500MB HDD + 300MB HDD, 1MB
Diamond Stealth Pro Video card).

Either I can port the Linux CDROM driver to Minix or I have to write my own
device driver. Can anyone help, point me to a place where hackers get the
stuff they need to write device drivers? They obviously know all the
details, like status codes, I/O regions etc. I am not sure if I would use
DMA, but I suppose it doesn't matter all that much.

If anyone on the kernel list has written a driver for a CDROM please send me
mail about how you went about it, did you approach the manufacturer for the
documentation on the device, if I made a mistake could I ruin my hardware?
and stuff like that.

Thanks heaps.
James Buchanan
james@spunkysoftware.com



             reply	other threads:[~2001-05-28 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  4:22 james [this message]
2001-05-28 21:22 ` Creative 4-speed CDROM driver Alan Cox
2001-05-29  7:20   ` james
2001-05-28 22:21     ` Alan Cox
2001-05-29  7:35       ` james
2001-05-29 10:21         ` Francois Romieu
     [not found]           ` <015601c0e8de$0e936ba0$c1a5fea9@spunky>
     [not found]             ` <20010530094004.A14129@se1.cogenit.fr>
2001-05-30 17:21               ` james
2001-05-30 15:12                 ` Masoud Sharbiani

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='016601c0e7f7$0c7c8780$c1a5fea9@spunky' \
    --to=james@spunkysoftware.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