From: "H. Peter Anvin" <hpa@zytor.com>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: tenth post about PCI code, need help
Date: Wed, 08 Jan 2003 11:48:29 -0800 [thread overview]
Message-ID: <3E1C808D.8080406@zytor.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1030108143728.31888A-100000@chaos.analogic.com>
Richard B. Johnson wrote:
> On 8 Jan 2003, H. Peter Anvin wrote:
>
>
>>Followup to: <Pine.LNX.3.95.1030108132812.28791A-100000@chaos.analogic.com>
>>By author: "Richard B. Johnson" <root@chaos.analogic.com>
>>In newsgroup: linux.dev.kernel
>>
>>>The problem is that he's discovered something that's not supposed
>>>to be in the code. Only 32-bit accesses are supposed to be made to
>>>the PCI controller ports. He has discovered that somebody has made
>>>some 8-bit accesses that will not become configuration 'transactions'
>>>because they are not 32 bits.
>>>
>>
>>Right. That's what the code is checking for.
>>
>> -hpa
>
> Somebody is very lucky the designer of the bus interface state-machine
> let him get away with it. This is a borderline "insane instruction" that
> could, on some (future?) machine, require a power-off to recover. This is
> NotGood(tm). It's like testing a fuse by shorting out a circuit. If it
> works, the circuit no longer works. If I doesn't, the circuit no longer
> works. Some things should not be tested.
>
If so, we will get an bug report rather than mysterious strange
behaviour. This is a good thing. (Amusingly enough, exactly this code
in the Linux kernel actually found a bug in one of the very early
versions of the Transmeta northbridge. It was fixed in firmware.)
-hpa
next prev parent reply other threads:[~2003-01-08 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 18:09 tenth post about PCI code, need help Ray Lee
2003-01-08 18:49 ` Richard B. Johnson
2003-01-08 19:13 ` Ray Lee
2003-01-08 19:20 ` H. Peter Anvin
2003-01-08 19:44 ` Richard B. Johnson
2003-01-08 19:48 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 16:13 fretre lewis
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=3E1C808D.8080406@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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.