[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PCI and Expansion ROM
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: PCI and Expansion ROM
- From: GERARD_FRASSE-MATHON@HP-France-om3.om.hp.com
- Date: Wed, 21 Aug 96 09:06:00 +0200
- Resent-Date: Wed, 21 Aug 96 09:06:00 +0200
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"m0WwJ1.0.io3.XMh6o"@dart>
- Resent-Sender: pci-sig-request@znyx.com
Item Subject: 3.3V Motherboards
Hello folks,
I've read all your messages on PCI and Expansion ROM issues but I've
personnally one more question about this :
someone says that some BIOS do not check that DeviceId is matching
the one of the device and I do agree that this is a violation of the
spec.
On another hand, if I understand why PCI spec as specified this, a
way to have 'generic' expansion ROM code would be great. For example,
many PCI PC today do not provide ISA expansion ROM sockets, so
applications in ROM such as anti virus codes are not usable...
There's no reason to link such a code to a PCI device but being able
to put this ROM on any PCI card providing a socket would be
appreciable.
Is there any thing doable in the PCI spec for this ? We could
imagine that an expansion ROM header with both DeviceId and VendorId
fields set to 0h or FFFFh could be accepted as a generic code...
Feedbacks appreciated !
Gerard
============================================================================
== Gerard FRASSE-MATHON ==============================
== R&D Network Engineer ========= _/ =========
== Hewlett-Packard - GPCD ======= _/ ======
== 5 Avenue Raymond Chanas, Eybens ===== _/_/_/ _/_/_/ ====
== 38053 Grenoble Cedex 9, FRANCE ===== _/ _/ _/ _/ ====
== Phone: +33 7662 1122 ===== _/ _/ _/_/_/ ====
== Fax : +33 7662 5370 ======= _/ ======
== Email : ========== _/ =========
== Gerard_Frasse-Mathon@hp.com ==============================
============================================================================
[ ü é