linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: Thorsten Leemhuis <thl@ct.heise.de>
Cc: Thorsten Leemhuis <fedora@leemhuis.info>,
	Chuck Ebbert <cebbert@redhat.com>, Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Jason Gaston <jason.d.gaston@intel.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, chunkeey@web.de
Subject: Re: [patch 2.6.22-rc6] ATA: add a PCI ID for Intel Santa Rosa PATA controller
Date: Thu, 5 Jul 2007 22:30:24 +0200	[thread overview]
Message-ID: <200707052230.25310.chunkeey@web.de> (raw)
In-Reply-To: <468BA8B0.8030606@ct.heise.de>

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

On Wednesday, 4. July 2007, Thorsten Leemhuis wrote:
>
> Maybe Alan or someone from Intel can answer that and thus tell us how to
> move forward; it would be really nice to get the patch that started this
> thread (it got posted by Chuck again today) could go into 2.6.22, but I
> assume the time runs away...
>
Jeff is on holiday and Intel doesn't respond at all... 

So, if someone has a ICH5 or ICH7/7-R with a ATA133 captable HDD... could
you please try the following patch? (Of course, I don't know if it works,...
It may cause data loss, serve corruption, or damage your controller/hdd/pc,
so make backups and keep a first-aid kit handy!) 
  
> > On the other hand, we can leave it, because of a "off-by-one error" in ata_piix.c, 
> > do_pata_set_dmamode, line ~770:
> > [...]
> 

Thanks,
	Chr.


[-- Attachment #2: don_t_try_this_if_you_don_t_know_what_it_does.patch --]
[-- Type: text/x-diff, Size: 401 bytes --]

--- a/drivers/ata/ata_piix.c	2007-06-19 12:19:39.000000000 +0200
+++ b/drivers/ata/ata_piix.c	2007-07-05 22:11:52.000000000 +0200
@@ -767,8 +767,8 @@
 		 *	       except UDMA0 which is 00
 		 */
 		u_speed = min(2 - (udma & 1), udma);
-		if (udma == 5)
-			u_clock = 0x1000;	/* 100Mhz */
+		if (udma >= 5)
+			u_clock = 0x1000;	/* 133Mhz */
 		else if (udma > 2)
 			u_clock = 1;		/* 66Mhz */
 		else

  reply	other threads:[~2007-07-05 20:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 19:16 ATA: add a PCI ID for Intel Santa Rosa PATA controller Chuck Ebbert
2007-06-28 19:47 ` [patch 2.6.22-rc6] " Chuck Ebbert
2007-06-29 14:31   ` Jeff Garzik
2007-07-02  5:02   ` Thorsten Leemhuis
2007-07-02  9:07     ` Thorsten Leemhuis
2007-07-02 11:24       ` Chr
2007-07-02 11:44         ` Thorsten Leemhuis
2007-07-02 14:36           ` Chr
2007-07-04 14:03             ` Thorsten Leemhuis
2007-07-05 20:30               ` Chr [this message]
2007-07-06 19:06                 ` Gaston, Jason D
2007-07-06 19:45                   ` Chr
2007-07-06 20:01                     ` Thorsten Leemhuis
2007-07-06 20:43                       ` Jeff Garzik
2007-07-05 21:17               ` 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=200707052230.25310.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cebbert@redhat.com \
    --cc=fedora@leemhuis.info \
    --cc=jason.d.gaston@intel.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thl@ct.heise.de \
    /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).