Re: rombios Info port

> > The rombios Info port at address 0xfff0 causes trouble when using PCI
> > devices because most OSes temporary remap the I/O ports of a PCI device
> > to the maximum address in order to determine the range of the I/O port
> > region of the device. So when the PCI device remaps itself to the
> > requested maximum port (for region size determination by the OS) we run
> > into trouble with that rombios Info port.
> > The file iodev/biosdev.cc states that 0xfff0 is a legacy port... is it
> > still needed?

> The 0xfff0 port was intended to be used with older bioses.
> I think it's no problem to remove it now.

> You may run into the same problem with the 0x8900 
> (shutdown), 0xfedc (debugger toggle) ports.
> Maybe we should relocate these ports lower in the 
> io space.

Definitely. I would suggest to group all the special Bochs ports
together and to provide a PCI device for them. That way a guest OS _can_
remap them if it feels like. VMWare has a PCI vendor ID... it would be
nice if we could get/borrow a device ID from VMware for a virtual Bochs
PCI device to group our guest-to-host stuff in. Anybody feels like
begging VMware for one? They have 2^16 device IDs, I think they can
afford it to give one away for free... :) at the end, Bochs/plex is like
a commercial spot to VMware Inc. (don't shoot me for that last line)


Frank.



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/