From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: 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: Sat, 12 Nov 2005 18:03:34 +0000 [thread overview]
Message-ID: <1131818615.18258.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20051112165548.GB28987@flint.arm.linux.org.uk>
On Sad, 2005-11-12 at 16:55 +0000, Russell King wrote:
> We must _never_ _ever_ on pain of death enable IDE DMA on SL82C105
> chipsets where the southbridge revision is <= 5, otherwise data
> corruption will occur.
If you are fixing this driver also set ->serialize = 1; before someone
with dual channel device gets burned.
next prev parent reply other threads:[~2005-11-12 17:32 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 [this message]
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
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=1131818615.18258.6.camel@localhost.localdomain \
--to=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