From: Alan Cox <alan@redhat.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mikael Pettersson <mikpe@it.uu.se>,
Jeff Norden <jeff@math.tntech.edu>,
alan@redhat.com, linux-kernel@vger.kernel.org,
Albert CC Lee <albertcc@tw.ibm.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 1/1] pata_it821x: fix lost interrupt with atapi devices
Date: Tue, 18 Sep 2007 05:14:00 -0400 [thread overview]
Message-ID: <20070918091400.GC13425@devserv.devel.redhat.com> (raw)
In-Reply-To: <46EE68F9.9050707@gmail.com>
On Mon, Sep 17, 2007 at 01:46:01PM +0200, Tejun Heo wrote:
> failures and would really like to know what's broken. The reason can be
> one of the following two.
>
> 1. libata itself isn't doing anything wrong but using SCSI for mid and
> high level drivers are causing problems as more types of commands are used.
>
> 2. Mode programming for MWDMA is broken. This doesn't seem too likely
> as we're seeing MWDMA failures across different low level drivers but is
> still a possibility.
3 and 4
3. Libata is wrong (it is in places)
4. Old IDE uses DMA much less for ATAPI especially
next prev parent reply other threads:[~2007-09-18 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200709041607.l84G7KsT032647@norden.math.tntech.edu>
[not found] ` <18141.42848.537873.349518@alkaid.it.uu.se>
[not found] ` <20070906013929.1621849d@the-village.bc.nu>
2007-09-17 5:00 ` [PATCH 1/1] pata_it821x: fix lost interrupt with atapi devices Tejun Heo
2007-09-17 10:00 ` Jeff Garzik
2007-09-17 11:46 ` Tejun Heo
2007-09-18 9:14 ` Alan Cox [this message]
2007-09-18 9:07 ` 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=20070918091400.GC13425@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jeff@math.tntech.edu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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;
as well as URLs for NNTP newsgroup(s).