Re: PCI code: why need outb (0x01, 0xCFB); ?

From: H. Peter Anvin (hpa@zytor.com)
Date: Wed Jan 08 2003 - 13:52:30 EST

Next message: H. Peter Anvin: "Re: Patch(2.5.54): devfs shrink - integration candidate"
Previous message: Bill Davidsen: "Re: observations on 2.5 config screens"
Next in thread: Petr Vandrovec: "Re: PCI code: why need outb (0x01, 0xCFB); ?"
Maybe reply: Petr Vandrovec: "Re: PCI code: why need outb (0x01, 0xCFB); ?"
Maybe reply: Petr Vandrovec: "Re: PCI code: why need outb (0x01, 0xCFB); ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Followup to: <F87sTOHYNhMwqvbLaKL0001615a@hotmail.com>
By author: "fretre lewis" <fretre3618@hotmail.com>
In newsgroup: linux.dev.kernel

> 1. which device is at port address 0xCFB?

Hopefully none.

> 2. what is meaning of the writing operation "outb (0x01, 0xCFB);" for THIS
> device?, it'seem that PCI spec v2.0 not say anything about it?

It's trying to verify that the PCI northbridge does *NOT* respond to
this (byte-wide) reference.

-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: H. Peter Anvin: "Re: Patch(2.5.54): devfs shrink - integration candidate"
Previous message: Bill Davidsen: "Re: observations on 2.5 config screens"
Next in thread: Petr Vandrovec: "Re: PCI code: why need outb (0x01, 0xCFB); ?"
Maybe reply: Petr Vandrovec: "Re: PCI code: why need outb (0x01, 0xCFB); ?"
Maybe reply: Petr Vandrovec: "Re: PCI code: why need outb (0x01, 0xCFB); ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:24 EST