From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: paul@paulbristow.net (Paul Bristow)
Cc: linux-kernel@vger.kernel.org (linux kernel mailing list),
alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: ide-floppy [Fwd: Updated ATAPI FORMAT_UNIT patch.]
Date: Sat, 13 Jan 2001 23:59:32 +0000 (GMT) [thread overview]
Message-ID: <E14Haa7-0006oj-00@the-village.bc.nu> (raw)
In-Reply-To: <3A60DA06.936CE1F2@paulbristow.net> from "Paul Bristow" at Jan 13, 2001 11:43:18 PM
> One of my concerns is that we don't take the ide-floppy driver in a
> different direction to the other removeable media drives.
In general the others do it raw via scsi commands and sg.
> For Alan Cox, could you back out Sam's patch for now. It will be back
> soon.
When the new one is sorted. I'm not going to feed it to Linus anyhow. For
the moment there are quite a few people glad of it
> > > > * Ability to open the device even if there's no disk in the drive. This
> > > > is needed by the userspace app to probe the device. The open path sends a
Other devices allow this for O_NDELAY only.
> > 1) A separate minor device that will open whether or not there's a
> > formatted disk in the drive. I don't like this approach.
Ugly. Thats a lot of extra devices.
> > The O_EXCL trick seems the cleanest way to be able to access the device
Use the same O_NDELAY cdroms do
> > Suppose that two months from now the Clik drive gets new firmware that
> > reports a slightly different model ID, say "IOMEGA Clik! 80 CZ ATAPI".
> > Or, perhaps, it's a new model of the Clik drive, that shares the same
> > shortcomings.
>
> Yep. Looks extremely possible.
Nod. I've already suggested a seperate blacklist table of device id/flaws
as SCSI does
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-13 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 22:43 Paul Bristow
2001-01-13 23:59 ` Alan Cox [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=E14Haa7-0006oj-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paulbristow.net \
/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®