Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Michael Gavlick" <mgavl69@juno.com>
To: linux-ide@vger.kernel.org
Cc: davem@davemloft.net
Subject: [PATCH] ide-iops: fix for drive side 80-wire cable detection failure f or IBM-DJNA-371350 HD
Date: Sun, 27 Sep 2009 23:34:19 GMT	[thread overview]
Message-ID: <20090927.193419.17010.1@webmail21.vgs.untd.com> (raw)

  The IDE driver complains about an 80-wire cable detection failure and falls back to UDMA/33 for the old IBM-DJNA-371350 Rev. J7NOA30K HD even though it is an UDMA/66 HD.

Kernel Message:
"hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdb: drive side 80-wire cable detection failed, limiting max speed to UDMA33
hdb: UDMA/33 mode selected"

  This patch disables the word 93 validity check in /drivers/ide/ide-iops.c for this particular hardware by adding it to the buggy firmware ivb_list. 

diff --git a/drivers/ide/ide-iops.c b/drivers/ide/ide-iops.c
index 6cc6c83..6d6f78f 100644
--- a/drivers/ide/ide-iops.c
+++ b/drivers/ide/ide-iops.c
@@ -218,6 +218,7 @@ static const struct drive_list_entry ivb_list[] = {
 	{ "TSSTcorp CDDVDW SH-S202H"	, "SB00"	},
 	{ "TSSTcorp CDDVDW SH-S202H"	, "SB01"	},
 	{ "SAMSUNG SP0822N"		, "WA100-10"	},
+        { "IBM-DJNA-371350"             , "J7NOA30K"    },
 	{ NULL				, NULL		}
 };




____________________________________________________________
Best Weight Loss Program - Click Here!
http://thirdpartyoffers.juno.com/TGL2131/fc/BLSrjnsEGrFwnIvIOVxbEtcxl1mbToJZIUdYtrSAhgUZhuqeEORJOOJ5xRW/

             reply	other threads:[~2009-09-27 23:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 23:34 Michael Gavlick [this message]
2009-09-28  0:26 ` [PATCH] ide-iops: fix for drive side 80-wire cable detection failure f or IBM-DJNA-371350 HD Jeff Garzik
2009-09-28 10:23 ` Mikael Pettersson
2009-09-28 13:29 ` 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=20090927.193419.17010.1@webmail21.vgs.untd.com \
    --to=mgavl69@juno.com \
    --cc=davem@davemloft.net \
    --cc=linux-ide@vger.kernel.org \
    /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