[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Galileo GT 64011 + PC BIOS Extension
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: Galileo GT 64011 + PC BIOS Extension
- From: "John R Pierce" <pierce@hogranch.com>
- Date: Mon, 28 Sep 1998 21:49:16 -0700
- Delivered-To: pcisig@teleport.com
- Resent-Date: Tue, 29 Sep 1998 16:25:58 -0700
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"p8kid2.0.TS2.gQ64s"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
Finichiu György <finisch@freemail.c3.hu> writes ...
>We should write a PC BIOS extension code, which
>reorganizes the PCI mapping so our mapped CS2
>is under 1MB. But We can not decide which is the
>empty place, and we can not use the mapped mem
>at BIOS POST time, because we see only the shadow
>RAM there.
you can't move resources in BIOS extension code. Its simply not feasible, as
you say, there's no way of determining where to move it.
Your device should have an alternate method of access, such as using IO ports,
if it requires realmode ROM code... Quite frankly, unless your device is a
legacy boot device (i.e. a disk controller or a VGA) it should not HAVE a bios
rom. The operating system device driver should manage accesses to PCI device
space.
-jrp
(device-driver developer on hiatus)