From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc1: IDE: fix potential data corruption with SL82C105 interfaces
Date: Mon, 15 May 2006 20:05:54 +0400 [thread overview]
Message-ID: <4468A6E2.5060305@ru.mvista.com> (raw)
In-Reply-To: <1147706716.26686.64.camel@localhost.localdomain>
Hello.
Alan Cox wrote:
> On Llu, 2006-05-15 at 18:32 +0400, Sergei Shtylyov wrote:
>> Heh, this driver also tries to cache the single PCI register per-channel
>>like hpt366.c... This buglet concerns using fast PIO timings and is probably
>>harmless though but needs to be fixed -- I'll send a patch soon...
>> I wonder what is otherwise wrong with using 2 channels concurrently?
> I've not got any dual channel devices to test, and in fact I couldn't
> find anyone with dual channel stuff at all.
Hm, I thought they're all dual channel, at least from W83C553F docs. We
have this chip on several embedded boards -- I'll try to gain access to one of
them when I get to this driver...
> The caching is one bug, the
> fact the reset hits both channels is the other I know about.
Ah, that register 0x7E reset? Strangely, W83C55[34]F datasheets don't even
mention it. :-/
> Otherwise the libata driver is fairly similar
Found it, looking...
> although the timing is
> pre-computed from the documentation for the DMA modes.
As these chips lack 66 MHz PCI support, this should be quite enough, I
think... :-)
MBR, Sergei
next prev parent reply other threads:[~2006-05-15 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 16:55 2.6.15-rc1: IDE: fix potential data corruption with SL82C105 interfaces Russell King
2005-11-12 18:03 ` Alan Cox
2005-11-12 17:46 ` Russell King
2006-05-15 14:32 ` Sergei Shtylyov
2006-05-15 15:25 ` Alan Cox
2006-05-15 16:05 ` Sergei Shtylyov [this message]
2006-05-15 16:35 ` Alan Cox
2006-05-15 17:10 ` Russell King
2005-11-15 13:27 ` 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=4468A6E2.5060305@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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).