From: Athol Mullen <athol_SPIT_SPAM@idl.net.au>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] IDE 80-core cable detect - chipset-specific code to over-ride eighty_ninty_three()
Date: Sun, 8 Feb 2004 11:45:18 +1100 [thread overview]
Message-ID: <200402081145.19027.athol_SPIT_SPAM@idl.net.au> (raw)
In-Reply-To: <1mwNn-1xb-27@gated-at.bofh.it>
Willy Tarreau <willy@w.ods.org> wrote:
> On Sat, Feb 07, 2004 at 05:00:18PM +1100, Athol Mullen wrote:
(Don't CC. I read lkml via linux.kernel newsgroup.)
>> After looking through the Intel specs for the ICH5, I discovered that they
>> specify that the BIOS is supposed to initialise bit flags for the presence
>> of 80-core ribbon for each drive.
> that could explain why I recently discovered that a 2.4.25-rc1 on a
> supermicro MB with ICH5 was limiting hda and hdb to 30 MB/s at UDMA33 while
> an old 2.4.20 + many patches including IDE gave me about 64 MB/s at UDMA100.
Before I modified eighty_ninty_three(), it returning 0 caused the _indicated_
mode to drop to UDMA33. Check in /proc/ide/piix to see what mode the driver
tells you. IIRC (could be wrong), dmesg and hdparm both believe it to be in
UDMA33 while the init code and /proc/ide/piix both showed it as UDMA5.
I'm starting to wonder if my ICH5 _is_ actually running UDMA5... It's doing
21MB/s, which I've been blaming on the old 30G Quantum, whereas the ICH4 with
a 120G drive is doing 56MB/s... I think I checked the bit flags in
/proc/ide/ide0/config and it showed up as UDMA5.
>> I'm not certain exactly how this would be implemented, but I'd like to see
>> eighty_ninty_three() check for chipset-specific detection code, and use the
>> existing word93 validation otherwise.
>> I have written and tested code for the intel ICH chipsets, but can't post a
>> patch until I know where to stick it. :-)
> well, why not in piix:piix_ratemask() around line 315 ?
I could put it there, but I was actually intending to use it to also return a
value properly for eighty_ninty_three(), and figured that it would need to be
a separate routine - I expect that the module structure needs to change, and
that's where I'm not sure - it could affect _all_ ide drivers. There might
be others that have their own specific detection code, and what I'm looking
to do is establish the framework for that.
Yes, there was a fairly stupid stuff-up on my part in my previous message - my
business .sig wasn't supposed to get tacked on after my usenet .sig... It
_was_ a spam-free email address. :-(
--
Athol
<http://cust.idl.com.au/athol>
Linux Registered User # 254000
I'm a Libran Engineer. I don't argue, I discuss.
next parent reply other threads:[~2004-02-08 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1mtPj-7oQ-3@gated-at.bofh.it>
[not found] ` <1mwNn-1xb-27@gated-at.bofh.it>
2004-02-08 0:45 ` Athol Mullen [this message]
2004-02-08 7:31 ` Willy Tarreau
2004-02-10 0:10 ` Bartlomiej Zolnierkiewicz
2004-02-10 0:37 ` Bartlomiej Zolnierkiewicz
[not found] <1n9OA-6lu-17@gated-at.bofh.it>
[not found] ` <1n9OA-6lu-23@gated-at.bofh.it>
[not found] ` <1n9OA-6lu-15@gated-at.bofh.it>
[not found] ` <1nu6y-XO-3@gated-at.bofh.it>
2004-02-10 7:16 ` Athol Mullen
2004-02-10 14:41 ` Bartlomiej Zolnierkiewicz
[not found] <1mLsS-6Oq-7@gated-at.bofh.it>
[not found] ` <1mLsS-6Oq-9@gated-at.bofh.it>
[not found] ` <1mLsS-6Oq-5@gated-at.bofh.it>
[not found] ` <1mRHV-4Xn-7@gated-at.bofh.it>
2004-02-09 2:50 ` Athol Mullen
2004-02-09 20:04 ` Willy Tarreau
2004-02-10 0:24 ` Bartlomiej Zolnierkiewicz
2004-02-07 6:00 Athol Mullen
2004-02-07 9:15 ` Willy Tarreau
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=200402081145.19027.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®