public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.nl>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Willy Tarreau <willy@w.ods.org>, 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: Fri, 13 Feb 2004 18:44:18 +0100	[thread overview]
Message-ID: <20040213174418.GA31694@bitwizard.nl> (raw)
In-Reply-To: <200402131823.53939.bzolnier@elka.pw.edu.pl>

On Fri, Feb 13, 2004 at 06:23:53PM +0100, Bartlomiej Zolnierkiewicz wrote:
> Great, but I wonder why cable bits are set incorrectly.
> Probably it's a BIOS bug, maybe BIOS update will help?

I think there is something wrong in the cable detection code. I've
tried chasing the bug a couple of weeks ago, but got distracted by
other work. On an AMD-768 based motherboard disks run in UDMA5 without
problem using linux-2.4.20, but on 2.4.24 (or anything with the new IDE
code), I can't get any further than UDMA2. At first glance it looks
like the 80-pin bits in the chipset registers aren't set. When I
manually force them, the driver has no problem running the disks in
UDMA5.

So far I've seen this behaviour with the following chipset:

  Bus  0, device   7, function  1:
    IDE interface: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE (rev 4).
      Master Capable.  Latency=32.  
      I/O at 0xd800 [0xd80f].

But rumours are that even on Intel ICH2 it goes wrong (haven't
confirmed this myself).

FWIW, I'm using modular IDE, I still have to test it with IDE built
into the kernel.


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.nl -- 0800 220 20 20 --
| Eigen lab: Delftechpark 26, 2628 XH, Delft, Nederland
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!

  reply	other threads:[~2004-02-13 17:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 20:06 (was Re: [RFC] IDE 80-core cable detect - chipset-specific code to over-ride eighty_ninty_three()) 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 [this message]
2004-02-13 18:30       ` Bartlomiej Zolnierkiewicz
     [not found] <1ovjW-1Ol-7@gated-at.bofh.it>
2004-02-18  7:26 ` Athol Mullen

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=20040213174418.GA31694@bitwizard.nl \
    --to=erik@harddisk-recovery.nl \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.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