From: Michael Roth <mroth@nessie.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: petkovbb@gmail.com, petkovbb@googlemail.com,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Bug in 2.6.29 ide-cd: Kernel freeze: bisected + unacceptable workaround
Date: Tue, 31 Mar 2009 14:35:39 +0200 [thread overview]
Message-ID: <49D20E1B.7010104@nessie.de> (raw)
In-Reply-To: <20090331122820.167d52e5@the-village.bc.nu>
>> take it ok. Also, if I remember correctly, the original ide-cd behavior
>> was to issue the command and _then_ start DMA so we're back to that. I
>> guess now we should be concerned whether the other ATAPI devices can
>> handle the reverse situation where you first issue a command and _then_
>> start DMA.. Hmm...
>
> Most devices don't care but you do need to follow the exact ATAPI spec.
> If you search way back through the archives you'll find long discussions
> on this during either 2.4 or 2.2 when HP hit problems caused by us
> turning DMA on too early.
AFAIK, the old bevavior was to start DMA _after_ issuing the command _only_
for CD-drives and for the remaining ide devices the other way around,
why not just restore the old behavior and do the DMA after command only
for CD-drives?
next prev parent reply other threads:[~2009-03-31 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 19:25 Bug in 2.6.29 ide-cd: Kernel freeze: bisected + unacceptable workaround Michael Roth
2009-03-29 20:13 ` Borislav Petkov
2009-03-29 21:37 ` Michael Roth
2009-03-30 7:27 ` Borislav Petkov
2009-03-30 11:10 ` Michael Roth
2009-03-30 11:38 ` Michael Roth
2009-03-30 11:50 ` Michael Roth
2009-03-30 20:28 ` Bartlomiej Zolnierkiewicz
2009-03-31 7:45 ` Borislav Petkov
2009-03-31 11:28 ` Alan Cox
2009-03-31 12:35 ` Michael Roth [this message]
2009-03-31 14:06 ` Borislav Petkov
2009-03-31 18:01 ` Bartlomiej Zolnierkiewicz
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=49D20E1B.7010104@nessie.de \
--to=mroth@nessie.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@gmail.com \
--cc=petkovbb@googlemail.com \
/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