On Wed, May 16, 2012 at 05:50:31PM +0200, Paolo Bonzini wrote: > Il 16/05/2012 15:46, Gleb Natapov ha scritto: > > I saw that, but I don't get why doing it this way instead of defining > > the object in AML and patching it? I can define Name(S4VL, 0x2) and path > > 0x2 to whatever QEMU wants me to use, or I can patch Package directly > > like I did. > > > > Can we build an SSDT that includes the contents of fw_cfg (e.g. > FW_CFG_SIGNATURE at offset 0, FW_CFG_UUID at offset 4, FW_CFG_NOGRAPHIC > at offset 16... the entry <-> offset mapping and the defaults would be > part of SeaBIOS), and then read that data from normal DSDT methods? > > That would be similar to Gerd's patch, but without letting the OSPM use > the real fw_cfg device.
I'm not sure I understand your proposal. Are you suggesting reading every fw_cfg "port" into memory and then passing that memory into an SSDT? If so, that wouldn't be easy (we don't necessarily know the size of each "port") and could potentially waste a lot of memory (think a vmlinuz stored in fw_cfg). -Kevin
