From: Krzysztof Halasa <khc@pm.waw.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: IDE CDROM tail read errors
Date: Sun, 02 Apr 2006 12:50:48 +0200 [thread overview]
Message-ID: <m3lkuotfnb.fsf@defiant.localdomain> (raw)
In-Reply-To: <1143717489.29388.32.camel@localhost.localdomain> (Alan Cox's message of "Thu, 30 Mar 2006 12:18:09 +0100")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> 1342256 (looks like it has been adjusted to .iso image size / 512 when
>> the first I/O error occured)
>
> The SCSI layer does this bit for everyone. Its actually not libata or
> the PATA drivers that have done the work here. You should find ide-scsi
> does the same.
I see. I wonder if TOC track (in 2KB sectors) longer than ISO image
is a (recording) bug.
> I patched the old IDE driver a bit to try and deal with this and if you
> want the patch to hack on and tidy up further feel free.
Thanks but... now I've converted my last machine to PATA-libata and
drivers/ide are dead for me:
- no way to hot-swap (permanent modules)
- IRQ timeouts on my EPIA-M (never seen with libata)
- now the "end of medium" problems
- code duplication and different device names
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-04-02 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 19:11 IDE CDROM tail read errors Krzysztof Halasa
2006-03-30 8:19 ` Jan Engelhardt
2006-04-02 10:55 ` Krzysztof Halasa
2006-04-02 18:13 ` Jan Engelhardt
2006-03-30 11:18 ` Alan Cox
2006-04-02 10:50 ` Krzysztof Halasa [this message]
2006-04-04 19:09 ` Bill Davidsen
2006-04-12 8:57 ` Alan Cox
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=m3lkuotfnb.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.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