From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: albertl@mail.com
Cc: Mikael Pettersson <mikpe@it.uu.se>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
alan@redhat.com, Unicorn Chang <uchang@tw.ibm.com>,
Doug Maxey <dwm@enoyolf.org>
Subject: Re: libata pata_pdc2027x success on sparc64
Date: Thu, 27 Jul 2006 20:35:08 +0400 [thread overview]
Message-ID: <44C8EB3C.4080404@ru.mvista.com> (raw)
In-Reply-To: <44C841B5.40806@tw.ibm.com>
Hello.
Albert Lee wrote:
>>>In contrast, the old IDE pdc202xx_new driver had lots
>>>of problems with CRC errors causing it to disable DMA.
>> Hm, from my experience it usually falls back to UltraDMA/44 and then
>>the thing startrt working...
>>>I wasn't able to manually tune it above udma3 without
>>>getting more errors. This isn't sparc64-specific: I've
>>>had similar negative experience with the old IDE Promise
>>>drivers in a PowerMac.
>> This happens because the "old" driver misses the PLL calibration code.
>> You may want to try these Albert's patches:
>>http://marc.theaimsgroup.com/?t=110992452800002&r=1&w=2
>>http://marc.theaimsgroup.com/?t=110992471500002&r=1&w=2
>>http://marc.theaimsgroup.com/?t=110992490100002&r=1&w=2
>>http://marc.theaimsgroup.com/?t=111019238400003&r=1&w=2
>> It looks like they were never considered for accepting into the kernel
>>while they succesfully solve this issue. Maybe Albert could try pushing
>>them into -mm tree once more?
> The libata version has three improvements compared to the IDE version.
> 1. The PLL calibration patches in the above URLs (for IDE)
> still need more improvement as done in the pdc_read_counter()
> of the libata version.
Indeed. When backporting your patches to 2.6.10, I've added alike
function, so can generate an extra patch against those.
> 2. The Promise 2027x adapters check the "set features - xfer mode"
> and set the timing register automatically. However, the automatically
> set values are not correct under 133MHz. Libata has a hook
> pdc2027x_post_set_mode() to set the values back by software.
You probably forgot -- the last mentioned patch was all about it. :-)
> 3. ATAPI DMA is supported (please see pdc2027x_check_atapi_dma()).
> Maybe we also need to add this to the IDE version.
Wouldn't hurt. :-)
> Currently I have no time to update the IDE pdc202xx_new driver.
I'll probably take this on then, starting with pushing this half-buried
stuff into -mm tree.
> Also as Alan said, we have no maintainer for the IDE layer at this time.
> So, if ok, please try to use the libata-based driver.
WBR, Sergei
next prev parent reply other threads:[~2006-07-27 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 23:58 libata pata_pdc2027x success on sparc64 Mikael Pettersson
2006-07-18 18:07 ` Sergei Shtylyov
2006-07-27 4:31 ` Albert Lee
2006-07-27 16:35 ` Sergei Shtylyov [this message]
2006-08-09 15:59 ` Mikael Pettersson
2006-08-09 16:05 ` Sergei Shtylyov
2006-08-09 16:15 ` Mikael Pettersson
-- strict thread matches above, loose matches on Subject: below --
2006-07-19 0:29 Mikael Pettersson
2006-07-25 16:02 ` 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=44C8EB3C.4080404@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@redhat.com \
--cc=albertl@mail.com \
--cc=dwm@enoyolf.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=uchang@tw.ibm.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;
as well as URLs for NNTP newsgroup(s).