From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jeff@garzik.org, akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_ali: Lots of problems still showing up with small ATAPI DMA
Date: Wed, 28 Nov 2007 20:26:47 +0900 [thread overview]
Message-ID: <474D5077.3090203@gmail.com> (raw)
In-Reply-To: <20071128092518.5f2ca7df@the-village.bc.nu>
Alan Cox wrote:
> On Wed, 28 Nov 2007 10:36:15 +0900
> Tejun Heo <htejun@gmail.com> wrote:
>
>> Alan Cox wrote:
>>> Hopefully there is a better long term solution but for now lets favour
>>> reliability.
>> I'm getting a lot of reports on pata_ali w/ misc ATAPI commands too. Do
>> you know whether it's a controller problem or drive one? All the
>> reports I got are laptops and I can't really ask them to disassemble
>> their laptops. :-)
>
> ALi is one that most definitely appears to be controller related. Thats
> why I sent Jeff a patch to use DMA for 2K+ transfers only. Some ALi also
> required the patch to set the xfer lengths.
>
> Its only some revs/combinations annoyingly - a lot of them (including the
> ones I have direct access too) just work.
Does READ_CD work fine via DMA? 2K+ filtering filters most if not all
misc commands so usually only sector (2K) aligned READ and WRITEs are
done via DMA. Interesting exceptions are READ_CD[_MSF] and
READ/WRITE_BUFFER which usually exceed 2K but aren't aligned to 2K. I
guess it's about time to write a test case program which issues a bunch
of problematic commands and see which works.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-11-28 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 14:37 [PATCH] pata_ali: Lots of problems still showing up with small ATAPI DMA Alan Cox
2007-11-24 0:36 ` Jeff Garzik
2007-11-28 1:36 ` Tejun Heo
2007-11-28 9:25 ` Alan Cox
2007-11-28 11:26 ` Tejun Heo [this message]
2007-11-28 13:05 ` 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=474D5077.3090203@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@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.