From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] CDC_MMC_WR
Date: 06 Nov 2003 10:44:06 -0700 [thread overview]
Message-ID: <1068140646.23487.119.camel@patrh9> (raw)
In-Reply-To: <1068136355.23487.44.camel@patrh9>
> Does the ->writeable bit exist for ide-cd devices, or only for sr
> devices?
I'm guessing only sr devices, since grep writeable fails in drivers/ide/
and in drivers/cdrom/.
> When cdrom.ko decides a device is not writable, how does cdrom.ko name
> that bit, else how does cdrom.ko call into ide-cd/sr to clear that bit?
Call back into sr from cdrom may occur via the cdrom_device_ops.
We define cdrom_ioctl CDROM_GET_CAPABILITY but no SET of capability,
though we do define CDROM_SET_OPTIONS.
Maybe we're telling me to add a call back to the cdrom_device_ops for
cdrom to notify ide-cd/sr that the capabilities have changed. ide-cd
could ignore that notification, sr could set
scsi_cd->scsi_device->writeable accordingly.
> Have "the ->writeable bit actually be set if the device is writeable".
grep is failing to find code for me that fetches this bit.
Is this bit ever fetched?
http://lxr.linux.no/ident?v=2.6.0-test7&i=writeable
no hits.
http://lxr.linux.no/search?v=2.6.0-test7&string=writeable
over seventy hits. Apparently none relevant, except to say scsi_scan
sets this bit for sd, clears this bit for sr, and sr sometimes sets and
fetches this bit until I patch sr to branch on CDC_MMC_WR instead.
Pat LaVarre
next prev parent reply other threads:[~2003-11-06 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 0:51 [PATCH] CDC_MMC_WR Pat LaVarre
2003-11-01 1:22 ` [PATCH] Backport CDC_MMC_WR Pat LaVarre
2003-11-06 16:32 ` [PATCH] CDC_MMC_WR Pat LaVarre
2003-11-06 17:44 ` Pat LaVarre [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-12 19:19 Pat LaVarre
2003-10-12 15:02 Pat LaVarre
2003-10-12 13:33 Pat LaVarre
2003-10-11 0:38 Pat LaVarre
2003-10-11 8:21 ` Jens Axboe
2003-10-13 15:02 ` Pat LaVarre
2003-10-20 22:58 ` Pat LaVarre
2003-10-27 20:40 ` Pat LaVarre
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=1068140646.23487.119.camel@patrh9 \
--to=p.lavarre@ieee.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.