[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: BIOS and Clocks
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: RE: BIOS and Clocks
- From: Cédric Caron <Cedric.Caron@merging.com>
- Date: Fri, 29 May 1998 16:26:44 +0200
- Resent-Date: Sat, 30 May 1998 02:37:33 -0700
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"l6E4o1.0.U-4.d9iRr"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
You probably have the PnP OS option in your bios set to YES
If you set this option to NO your card will be correctly configured.
To solve this problem you can change the value in the Command register
in the config space of your card when you starts your driver.
Cédric.
-----Original Message-----
From: Terje Melsom, VMETRO [mailto:terje@vmetro.no]
Sent: Friday, May 29, 1998 10:48 AM
To: Mailing List Recipients
Subject: BIOS and Clocks
Hi,
I have two questions related observation we have made
when debugging a
driver problem on a dual Pentium-II motherboard.
1) When the PC boots, the clock signals to un-populated
PCI slots are
disabled after a few seconds. Does anyone know how this
is done? It does
not seem to be controlled using the PRSNT pins, but
rather by which
boards respond in config space. Is this a feature of the
motherboard
that can be turned of for the purpose of debugging? How
common is this?
2) We have a board with a Windows-NT driver that does
not work on this
specific motherboard. What we see is that the BIOS
assigns base
addresses in both memory and I/O space to the PCI
interface, but leaves
it in a state with memory and I/O space disabled. In
most other systems
we have observed that the BIOS enables memory and I/O
space. Are there
rules or a recommendations on how the BIOS should behave
in this matter
?
Thanks for your help
--
Terje Melsom