From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: "Jung-Ik (John) Lee" <jilee@google.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libata:ide: Fix udma timings of pdc202xx_old controllers
Date: Fri, 18 Sep 2009 15:52:50 +0400 [thread overview]
Message-ID: <4AB37492.90407@ru.mvista.com> (raw)
In-Reply-To: <8b5805ff0909171654i515c832bm570db9bd5936b11a@mail.gmail.com>
Hello.
Jung-Ik (John) Lee wrote:
>>>From: John(Jung-Ik) Lee <jilee@google.com>
>>>Fix udma timings of pdc202xx_old controllers.
>>>MB=1, MC=1 (0x20, 0x01) for all UDMA modes of pdc2026{57}.
The patch should be broken in two as it's for 2 different subsystems.
>>On what documentation is this based ?
> I have two documents, 20265, and 20267, and both need to set to the
> same single value for all UDMA modes.
> Doc 1:
> PDC20265 Bus Mastering Ultra DMA PCI –ATA/ATAPI Controller
> Specification Rev 2.0
> #7.17.2, Ultra DMA Data Transfer Speed list
> For all Ultra DMA mode, MB, MC = 01h, 01h
> Doc 2:
> PDC20267 Bus Mastering Ultra DMA PCI –ATA/ATAPI Controller
> Specification Rev 2.0
> #7.17.2, Ultra DMA Data Transfer Speed list
> For all Ultra DMA mode, MB, MC = 01h, 01h
> Are there other pdc202xx old controllers that are different?
There are PDC20262 and PDC20246. We should ask Bart -- he probably has
the documatation for them...
> -John
>>Alan
WBR, Sergei
next prev parent reply other threads:[~2009-09-18 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 23:02 [PATCH] libata:ide: Fix udma timings of pdc202xx_old controllers Jung-Ik (John) Lee
2009-09-17 23:23 ` Alan Cox
2009-09-17 23:54 ` Jung-Ik (John) Lee
2009-09-18 11:52 ` Sergei Shtylyov [this message]
2009-09-20 19:48 ` 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=4AB37492.90407@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jilee@google.com \
--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;
as well as URLs for NNTP newsgroup(s).