On 05/21/2013 06:50 AM, Paolo Bonzini wrote:
>>> -"-chardev ringbuf,id=id[,size=size]\n" +"-chardev
>>> memory,id=id[,size=size]\n"
>
>> This change impacts the command line.
>
> This is just the help text. "qemu-system-x86_64 -chardev
> memory,id=foo" works here on 1.4.1.
Good to know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/05/2013 14:38, Eric Blake ha scritto:
> On 05/21/2013 04:27 AM, Lei Li wrote:
>> Now we have memory char device, but the backend name of it is a
>> little confusion. We actually register it by 'memory', but the
>> description in qemu-option, the
On 05/21/2013 04:27 AM, Lei Li wrote:
> Now we have memory char device, but the backend name of it
> is a little confusion. We actually register it by 'memory', but
> the description in qemu-option, the name of open functions
> and the new api backend called it 'ringbuf'. It should keep
> consisten
On 05/21/2013 06:34 PM, Paolo Bonzini wrote:
Il 21/05/2013 12:27, Lei Li ha scritto:
Now we have memory char device, but the backend name of it
is a little confusion. We actually register it by 'memory', but
the description in qemu-option, the name of open functions
and the new api backend calle
Now we have memory char device, but the backend name of it
is a little confusion. We actually register it by 'memory', but
the description in qemu-option, the name of open functions
and the new api backend called it 'ringbuf'. It should keep
consistent. This patch named it all to 'memory'.
Signed-
