On 2011-08-29 13:05, Jan Kiszka wrote:
On 2011-08-29 13:00, Avi Kivity wrote:
On 08/29/2011 01:25 PM, Jan Kiszka wrote:
Can't seabios just poke at the hpet itself and see if it exists or not?
Would be hard for the BIOS to guess the locations of the blocks unless we define the addresses used by QEMU as something like base + hpet_no * block_size in all cases.
Currently we have a fixed address. We could do:
if available in fw_cfg: use that (may indicate no hpet) elif fixed address works: use that else no hpet
Currently, we also only have a single HPET block, but that's just because of some QEMU limitations that will vanish sooner or later. Then nothing will prevent multiple "-device hpet,base=XXX".
That said, some HPET probing (without any fw_cfg) may be a short-term workaround to fix Seabios until we defined The solution for communicating HPET block configurations.
Jan