mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Athol Mullen <athol_SPIT_SPAM@idl.net.au>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: (was Re: [RFC] IDE 80-core cable detect - chipset-specific code to over-ride eighty_ninty_three())
Date: Wed, 18 Feb 2004 18:26:38 +1100	[thread overview]
Message-ID: <200402181826.38042.athol_SPIT_SPAM@idl.net.au> (raw)
In-Reply-To: <1ovjW-1Ol-7@gated-at.bofh.it>

Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:

> Athol, does this patch solves your problem?

> [PATCH] add 80-wires cable detection quirk for QUANTUM FIREBALLlct20 30

My apologies for the delay.  Paid work gets in the way sometimes...

I haven't had a chance to test the patch yet, but have confirmed that it is 
definately a drive-related problem.  I put it on my ICH4 as slave to another 
drive that passes the validation bit, then put the Quantum back on the ICH5 
and put the other drive in as slave.  The other drive always passes the 
validation bit and the Quantum always fails.

Another suggestion would be to make a kernel parameter such as ide0=ivb or 
hda=ivb to force ignoring the validation bit...  That way, we don't need a 
list of drive models hardcoded into the kernel.

I'll test the patch ASAP.

-- 
Athol
<http://cust.idl.com.au/athol>
Linux Registered User # 254000
I'm a Libran Engineer. I don't argue, I discuss.



       reply	other threads:[~2004-02-18  7:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ovjW-1Ol-7@gated-at.bofh.it>
2004-02-18  7:26 ` Athol Mullen [this message]
2004-02-12 20:06 Bartlomiej Zolnierkiewicz
2004-02-12 20:41 ` Miquel van Smoorenburg
2004-02-13 17:33   ` Bartlomiej Zolnierkiewicz
2004-02-13  8:37 ` Willy Tarreau
2004-02-13 17:23   ` Bartlomiej Zolnierkiewicz
2004-02-13 17:44     ` Erik Mouw
2004-02-13 18:30       ` 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=200402181826.38042.athol_SPIT_SPAM@idl.net.au \
    --to=athol_spit_spam@idl.net.au \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®