From: Bob <recbo@nishanet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: IRQ disabled (SATA) on NForce2 and my theory
Date: Mon, 15 Dec 2003 22:56:08 -0500 [thread overview]
Message-ID: <3FDE8258.4050801@nishanet.com> (raw)
In-Reply-To: <200312151555.51845.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
>On Monday 15 of December 2003 07:06, Bob wrote:
>
>
>>sii chips have a long history of needing to
>>hdparm off the unmask interrupt feature.
>>
>>I don't know about that chip but for
>>sii680 there is a special option "-p9"
>>for hdparm which is to say pio mode 9
>>is a special instruction in addition to
>>standard hdparm opt "-u0" turning off
>>irq unmask.
>>
>>
>
>There is no such thing as 'special option "-p9"' for sii680.
>
>
Passing PIO mode 9 to sii680 will make it do udma133 with
unmask off, same as "-X70 -u0". What sii did was to make a
bug a feature by embedding their own special pio mode for the
well-known cmdxxx unmask off requirement.
Making A Bug A Feature is begging for "deprecation".
Since -p9 was only documented to set u133 and unmask off,
making a bug a feature, non-bug features are not user-expected
to be set without using other(normal) hdparm options, so
somebody might as well "man hdparm" and bypass the silly
kludge which probably was an internal office joke anyway.
-Bob
>>/sbin/hdparm -d1 -c1 -p9 -X70 -u0 -k0 -i $a
>>
>>
>
>-X70 is only valid if your device is UDMA133.
>
>--bart
>
>
>
next prev parent reply other threads:[~2003-12-16 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 13:14 IRQ disabled (SATA) on NForce2 and my theory Julien Oster
2003-12-15 6:06 ` Bob
2003-12-15 14:55 ` Bartlomiej Zolnierkiewicz
2003-12-16 3:56 ` Bob [this message]
2003-12-16 20:00 ` Bartlomiej Zolnierkiewicz
2003-12-15 1:13 Ross Dickson
2003-12-15 6:22 ` Bob
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=3FDE8258.4050801@nishanet.com \
--to=recbo@nishanet.com \
--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;
as well as URLs for NNTP newsgroup(s).