From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
Hugh Dickins <hugh@veritas.com>, Jeff Garzik <jgarzik@redhat.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.29-rc libata sff 32bit PIO regression
Date: Thu, 22 Jan 2009 03:20:13 +0300 [thread overview]
Message-ID: <4977BBBD.90704@ru.mvista.com> (raw)
In-Reply-To: <4977B1D1.2010305@ru.mvista.com>
Hello, I wrote:
>>>>>> > I've a Dell Precision 670 here (four-year-old EM64T Xeon with
>>>>>> ata_piix)
>>>>>> > which doesn't like your commit
>>>>>> 871af1210f13966ab911ed2166e4ab2ce775b99d
>>>>>> > libata: Add 32bit PIO support. Full dmesg (and .config)
>>>>>> attached, but
>>>>>> > here's an extract showing the start of the error messages on
>>>>>> ata2:
>>>>>>
>>>>> Cool - so we need two different 32bit PIO methods - at least
>>>>> according to
>>>>> the docs for the AMD we should use entirely 32bit I/O there. Fun fun
>>>>>
>>>> Could you refer me to the exact AMD doc that requires that?
>>>>
>>>
>>> AMD762 page 82, under DevB:1x40 bit 14 and bit 12
>>>
>>
>> What exactly AMD-762 document has this? I'm not seeing it in either
>> stasheet ot software/BIOS design guide. Besides, AMD-762 is a north
>> bridge and doesn't include IDE.
>
> Finally found it in the AMD-768 datasheet.
>
>>> "Note: only 32-bit writes to the data port are allowed when this bit is
>>> set."
>>>
>>
>> Now tell me who forces you to set that bit (I assume it's the write
>> buffer enable) for the ATAPI devices?
>
> Yes, it's the write buffer enable (about which I have written already).
IMHO, this is the same situation as with the prefetch -- you want to
avoid additional data read (write in this case) cycles to with an ATAPI
device, so you have to turn it off.
MBR, Sergei
next prev parent reply other threads:[~2009-01-22 0:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 13:34 2.6.29-rc libata sff 32bit PIO regression Hugh Dickins
2009-01-21 20:11 ` Mikael Pettersson
2009-01-21 21:47 ` Alan Cox
2009-01-21 22:51 ` Sergei Shtylyov
2009-01-21 22:58 ` Alan Cox
2009-01-21 23:34 ` Sergei Shtylyov
2009-01-21 23:37 ` Sergei Shtylyov
2009-01-22 0:20 ` Sergei Shtylyov [this message]
2009-01-25 15:22 ` Alan Cox
2009-01-26 19:11 ` Alan Cox
2009-01-31 15:11 ` Sergei Shtylyov
2009-01-31 16:06 ` Alan Cox
2009-01-31 16:57 ` Sergei Shtylyov
2009-02-01 21:13 ` Hugh Dickins
2009-02-02 11:48 ` Sergei Shtylyov
2009-02-02 12:12 ` Hugh Dickins
2009-02-02 14:17 ` Sergei Shtylyov
2009-02-03 3:59 ` Jeff Garzik
2009-02-04 11:10 ` Sergei Shtylyov
2009-01-26 19:12 ` Alan Cox
2009-02-03 4:00 ` Jeff Garzik
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=4977BBBD.90704@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=rjw@sisk.pl \
/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).