[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: A BAR of 0 = disabled
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: RE: A BAR of 0 = disabled
- From: Daniele Beccari <daniele@petrus.grenoble.hp.com>
- Date: Fri, 06 Sep 1996 18:53:12 +0200
- Organization: Hewlett-Packard Company
- Resent-Date: Fri, 06 Sep 1996 18:53:12 +0200
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"2ZZoQ2.0.l9.zS5Co"@dart>
- Resent-Sender: pci-sig-request@znyx.com
- Sender: daniele@petrus.grenoble.hp.com
PCI people,
I don't understand what the problem is with this discussion.
The note about a BAR not valid if 0, means to me:
"If a BAR is 0 it means it is NOT implemented and THEREFORE
it will not receive any memory allocation"
Or if you like: "A BAR reading 0 is invalid THEREFORE it is
not implemented and THEREFORE it will not receive any memory
allocation".
As far as I understand, there is no way that a BAR can BE SET
to 0. It just CONTAINS 0 because it was burnt like that.
Unless, obviously, I am missing something and THEREFORE I
should read the spec one more time ... ;-)
Cheers,
Daniele
--
__________________________________________________________
Daniele Beccari Daniele_Beccari@grenoble.hp.com
Hewlett-Packard, Enterprise Networking & Security Division
Î ö