PCI BAR and Expansion ROM

[<w_wong@emulex.com>]

Hello, everyone,

First of all, thank you very much for the enthusiastic inputs from
everybody especially David O'Shea from Corollary.
it's really helpful. I have some more questions, though.

ASSUMPTION:
(1) Architecture: Intel PC and PCI boot device.
(2) O.S:  Window NT, Window95 or SCO and others.
(3) BAR:  The memory map address only; NO ALTERNATIVE
I/O ACCESS TO THE BAR.

PCI BAR QUESTION:
Can I force the TYPE bits of the BAR to be under 1M and
implement INT13 in real mode to access the BAR? Any
unforseen problems with above assumptions?

PCI EXPANSION ROM QUESTIONS:
Since Gilbert Yeung from Lanworks Technologies Inc brought up
some interesting issues about PCI Expansion ROM, I have
some questions also.

(1) During INIT before the O.S is booted, can the Intialization routine
switch to Protected mode to access Expansion Rom Register
instead of calling INT15 function 87?

(2) If there is an address in the Expansion ROM Base Register after
the O.S. is booted, is it safe for the Device Driver to claim it (in
Protected Mode) by setting bit 0 of the ROM BAR? This is under the
assumption that BAR and Expansion ROM DO NOT share the same
address decoder for the Boot Device.

(3) According to the book " PCI Hardware and Software Architecture
& Design", author by Edward Solari & George Willse, PCI System
BIOS will zero out the ROM Register after it copied the ROM image to
RAM area (c8000h to e0000h).  However, it did not happened to one
of my PC system.  Is it up to the individual System BIOS vendor to
zero out after the ROM image was copied to the RAM area? In
other words, some will do and some will not do?

Thank you very much.

Windson Wong
(714) 513-8119
Emulex Corp Network Systems.
3535 Harbor Bl.,
Costa Mesa, Ca92626
!
ÔÃ