[Qemu-devel] 'blank' address space for unknown arm peripherals?

[Marty Plummer]

Greetings.

Its my understanding that for creating machine definitions for qemu one
uses what amount to 'drivers' or 'hardware simulations'. I was wondering
if there was what amounted to a blank or raw memory area one could use
as a placeholder for a peripheral which is currently undocumented and
lacking source code for the linux kernel drivers the vendor ships.

My aim is to simulate as much of the hardware as I've managed to
positively identify (mostly primecell stuff) and use the
blank/placeholder address space to observe the interactions between the
blob drivers with the known address space within a simulated environment
to hopefully deduce the hardware registers for the peripherals (mostly
a/v & h264/jpeg stuff).

Any tips and tricks you could provide I would be greatly appreciative.

Marty.