From: Jeff Garzik <jeff@garzik.org>
To: Michael Gavlick <mgavl69@juno.com>
Cc: linux-ide@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] ide-iops: fix for drive side 80-wire cable detection failure f or IBM-DJNA-371350 HD
Date: Sun, 27 Sep 2009 20:26:13 -0400 [thread overview]
Message-ID: <4AC002A5.3090705@garzik.org> (raw)
In-Reply-To: <20090927.193419.17010.1@webmail21.vgs.untd.com>
On 09/27/2009 07:34 PM, Michael Gavlick wrote:
> 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 }
Would you create the libata version of this patch, too, please?
We are [very slowly] migrating away from the old-IDE driver.
Jeff
next prev parent reply other threads:[~2009-09-28 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 23:34 [PATCH] ide-iops: fix for drive side 80-wire cable detection failure f or IBM-DJNA-371350 HD Michael Gavlick
2009-09-28 0:26 ` Jeff Garzik [this message]
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=4AC002A5.3090705@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=linux-ide@vger.kernel.org \
--cc=mgavl69@juno.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.