On 08/31/2013 04:36 PM, Cole Robinson wrote:
> Unlike other list types, enum wasn't adding any padding, which caused
> a mismatch between the generated struct size and GenericList struct
> size. More details in a678e26cbe89f7a27cbce794c2c2784571ee9d21
>
> This crashed qemu if calling qmp query-tpm
Dear Zaborowski:
Firstly,I'm writing to express my thanks to you for the source
code of Max7310 which have helped me so much.
But I'm still confused about the method of reading output port register.
code:
case 0x01: /* Output port */
return s->level & ~s->direction;
break;
Unlike other list types, enum wasn't adding any padding, which caused
a mismatch between the generated struct size and GenericList struct
size. More details in a678e26cbe89f7a27cbce794c2c2784571ee9d21
This crashed qemu if calling qmp query-tpm-types for example, which
upsets libvirt capabilities p
Am 31.08.2013 19:22, schrieb Antony Pavlov:
> Use of SysBusDevice::init is deprecated.
> Use Device::realize instead of SysBusDevice::init.
> Check dma/pl330.c for an example of the pattern.
>
> Also introduce TypeInfo::instance_init milkymist_uart_init()
> as char/pl011.c does.
>
> Reported-by:
Use of SysBusDevice::init is deprecated.
Use Device::realize instead of SysBusDevice::init.
Check dma/pl330.c for an example of the pattern.
Also introduce TypeInfo::instance_init milkymist_uart_init()
as char/pl011.c does.
Reported-by: Peter Crosthwaite
Signed-off-by: Antony Pavlov
CC: Peter C
qemu_chr_fe_write() is capable of returning 0
to indicate EAGAIN (and friends) and we don't
handle this.
Just change it to qemu_chr_fe_write_all() to fix.
Reported-by: Peter Crosthwaite
Signed-off-by: Antony Pavlov
CC: Peter Crosthwaite
CC: Michael Walle
CC: Andreas Färber
---
hw/char/milky
This patch series based on DIGIC support adding comments:
http://lists.nongnu.org/archive/html/qemu-devel/2013-08/msg04748.html
[PATCH v2 1/2] milkymist-uart: use qemu_chr_fe_write_all() instead of
qemu_chr_fe_write()
[PATCH v2 2/2] milkymist-uart: use Device::realize instead of SysBusDevice::i
Public bug reported:
Originally filed here:
https://bugzilla.redhat.com/show_bug.cgi?id=1000118
./x86_64-softmmu/qemu-system-x86_64 -device ahci -drive
id=aa,file=/tmp/foo,if=none -drive id=bb,file=/tmp/foo,if=none -device
ide-hd,drive=aa -device ide-hd,drive=bb
qemu-system-x86_64: -device ide-
Hi there,
Our team want to emulate a multi-touchscreen device controller/device based
on x86 arch, and encounter some problems.
We have created a virtual multi-touchscreen controller demo, and registered
it on i2c bus, but it doesn't seem to work.
We register the controller on i2c bus, cause:
Am 31.08.2013 07:33, schrieb Antony Pavlov:
> url="http://lists.nongnu.org/archive/html/qemu-devel/2013-08/msg04748.html";>
> Use of SysBusDevice::init is deprecated. Please use
> Device::realize instead of SysBusDevice::init.
> Check dma/pl330.c for an example of the pattern.
>
>
> Signe
Public bug reported:
NB: This bug ONLY happens on i686. When qemu is compiled for x86-64,
the bug does NOT happen.
$ ./configure --enable-tpm
$ make
$ (sleep 5; printf
'{"execute":"qmp_capabilities"}\n{"execute":"query-tpm-types"}\n') |
./i386-softmmu/qemu-system-i386 -S -nodefaults -nographic
I tested below combos of qemu and kernel,
++-+-+
|kernel | QEMU | migration |
++-+-+
| SLES11SP2+kvm-kmod-3.6 | qemu-1.6.0|GOOD |
+
On Thu, Aug 29, 2013 at 8:28 PM, Gary Ching-Pang Lin wrote:
> On Fri, Aug 30, 2013 at 02:04:40AM +1000, Bruce Rogers wrote:
>> I tried this out, and I get the black screen as well when ept=n, but it boots
>> successfully to the efi shell when ept=y.
>>
>> Gary, what does 'cat /sys/module/kvm_intel
Il 30/08/2013 21:05, Jordan Justen ha scritto:
> I meant your proposed update to VTF0 is not quite what is needed
> within EDK II. The current ROM based tables need to stay because that
> is what real firmware would need to use to enable a 64-bit PEI.
Ok, understood.
> OVMF will just have to do s
14 matches
Mail list logo
