From: Ingo Saitz <Ingo.Saitz@stud.uni-hannover.de>
To: linux-scsi@vger.kernel.org
Subject: Re: PROBLEM: 2.6.25: sr0 cdrom does not change medium size on medium change
Date: Tue, 13 May 2008 18:09:10 +0200 [thread overview]
Message-ID: <20080513160910.GA2554@schwan.zoo> (raw)
In-Reply-To: <20080512203422.GA2641@schwan.zoo>
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
Maybe this is related to a change in the logic of CDROM_DRIVE_STATUS.
Using test.c from http://marc.info/?l=linux-scsi&m=120231922209420&w=2
there is a big difference in the responses from 2.6.24 (working) and
2.6.25 (broken):
2.6.25 2.6.24
empty drive CDS_NO_DISC CDS_TRAY_OPEN
opening tray CDS_TRAY_OPEN CDS_TRAY_OPEN
inserting disc CDS_NO_DISC waits for drive to settle, then CDS_DISK_OK
drive setteled CDS_DISK_OK CDS_DISK_OK
Please tell me if you need more data...
Ingo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-13 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080508112108.GA2744@schwan.zoo>
2008-05-12 20:34 ` PROBLEM: 2.6.25: sr0 cdrom does not change medium size on medium change Ingo Saitz
2008-05-13 16:09 ` Ingo Saitz [this message]
2008-05-08 11:21 Ingo Saitz
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=20080513160910.GA2554@schwan.zoo \
--to=ingo.saitz@stud.uni-hannover.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox