From: Andrew Morton <akpm@linux-foundation.org>
To: Chr <chunkeey@web.de>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, stable@kernel.org,
Justin Forbes <jmforbes@linuxtx.org>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Theodore Ts'o <tytso@mit.edu>,
Randy Dunlap <rdunlap@xenotime.net>,
Dave Jones <davej@redhat.com>,
Chuck Wolber <chuckw@quantumlinux.com>,
Chris Wedgwood <reviews@ml.cw.f00f.org>,
Michael Krufky <mkrufky@linuxtv.org>,
Chuck Ebbert <cebbert@redhat.com>,
Domenico Andreoli <cavokz@gmail.com>,
torvalds@linux-foundation.org, alan@lxorguk.ukuu.org.uk,
linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Gaston@debian64.daheim, Jason D <jason.d.gaston@intel.com>
Subject: Re: [2.6.22.2 review 06/84] Add a PCI ID for santa rosas PATA controller.
Date: Thu, 9 Aug 2007 12:39:48 -0700 [thread overview]
Message-ID: <20070809123948.1d62be70.akpm@linux-foundation.org> (raw)
In-Reply-To: <200708080139.14248.chunkeey@web.de>
On Wed, 8 Aug 2007 01:39:12 +0200
Chr <chunkeey@web.de> wrote:
> On Tuesday, 7. August 2007, Greg KH wrote:
> >
> > From: Christian Lamparter <chunkeey@web.de>
> >
> > This is commit c1e6f28cc5de37dcd113b9668a185c0b9334ba8a which is
> > merged during 23-rc1 window. Considering the popularity of these
> > chips, I think including it in -stable release would be good idea.
> >
> > Signed-off-by: Christian Lamparter <chunkeey@web.de>
> > Signed-off-by: Jeff Garzik <jeff@garzik.org>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> >
>
> I did not receive any complains. I guess it's stable enough for -stable ;-) ...
>
> ---
>
> Not OT:
>
> There is another outstanding issue with ata_piix.c.
> Intel has never officially supported anything faster than PATA 100MB/s.
>
> But, the ata_piix.c driver "define" the ICH5 & ICH7 as UDMA6 (aka 133MB/s) capable.
> [ Well, no one has probably noticed it before, because there is bug in do_pata_set_dmamode...
> Just look at libata_atapiix_enable_real_udma133.patch and you'll see what wrong with it. ]
>
> Here are Intel's datasheets for the affected chipsets:
> ICH5 Datasheet: http://www.intel.com/design/chipsets/datashts/252516.htm
> (See note on page 183: "... the ICH5 supports reads at the maximum rate of 100MB/s.")
>
> ICH7 Datasheet: http://www.intel.com/design/chipsets/datashts/307013.htm
> (See first note on page 190: "... the ICH7 supports reads at the maximum rate of 100MB/s.")
>
> -
>
> They are two different ways to deal with it:
>
> - Either -
>
> 1. replace all ich_pata_133 with ich_pata_100.
> (libata_atapiix_disable_udma6.diff - diff from 2.6.22 )
>
> - Or -
>
> 2. keep all ich_pata_133 and fix the bug in "do_pata_set_dmamode".
> (libata_atapiix_enable_real_udma133.patch - diff from 2.6.22)
> If there are any concerns about the safety of the patch patch:
> http://lkml.org/lkml/2007/7/6/292 (It was already tested by an Intel employee,
> but I guess a bit more user input is necessary here... )
>
> Both ways have their pros and cons. Unfortunately, I don't have the time to follow this
> discussion right now, so here's a:
>
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
> (Just in case, if one of the patches really gets merged!)
>
You kinda hid these patches rather well.
I chose option 1.
next prev parent reply other threads:[~2007-08-09 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070807204034.882009319@mini.kroah.org>
[not found] ` <20070807204157.GA23028@kroah.com>
2007-08-07 20:42 ` [2.6.22.2 review 06/84] Add a PCI ID for santa rosas PATA controller Greg KH
2007-08-07 23:39 ` Chr
2007-08-09 19:39 ` Andrew Morton [this message]
2007-08-07 20:48 ` [2.6.22.2 review 67/84] libata: add FUJITSU MHV2080BH to NCQ blacklist Greg KH
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=20070809123948.1d62be70.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Gaston@debian64.daheim \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cavokz@gmail.com \
--cc=cebbert@redhat.com \
--cc=chuckw@quantumlinux.com \
--cc=chunkeey@web.de \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=jason.d.gaston@intel.com \
--cc=jeff@garzik.org \
--cc=jmforbes@linuxtx.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@linuxtv.org \
--cc=rdunlap@xenotime.net \
--cc=reviews@ml.cw.f00f.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=zwane@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).