On Wed, 10 Nov 2010 14:33:47 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > On Wed, 10 Nov 2010 13:56:39 +0100
> > Markus Armbruster wrote:
> >
> >> Luiz Capitulino writes:
> >>
> >> > On Wed, 10 Nov 2010 10:26:15 +0100
> >> > Markus Armbruster wrote:
> [...]
> >> >> Unlike
Luiz Capitulino writes:
> On Wed, 10 Nov 2010 13:56:39 +0100
> Markus Armbruster wrote:
>
>> Luiz Capitulino writes:
>>
>> > On Wed, 10 Nov 2010 10:26:15 +0100
>> > Markus Armbruster wrote:
[...]
>> >> Unlike normal character drivers, this one can't be closed with
>> >> qemu_chr_close(), can
On Wed, 10 Nov 2010 13:56:39 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > On Wed, 10 Nov 2010 10:26:15 +0100
> > Markus Armbruster wrote:
> >
> >> Luiz Capitulino writes:
> >>
> >> > This driver handles in-memory qemu-char driver operations, that's,
> >> > all writes to thi
Luiz Capitulino writes:
> On Wed, 10 Nov 2010 10:26:15 +0100
> Markus Armbruster wrote:
>
>> Luiz Capitulino writes:
>>
>> > This driver handles in-memory qemu-char driver operations, that's,
>> > all writes to this driver are stored in an internal buffer. The
>> > driver doesn't talk to the e
Luiz Capitulino writes:
> This driver handles in-memory qemu-char driver operations, that's,
> all writes to this driver are stored in an internal buffer. The
> driver doesn't talk to the external world in any way.
I'm not so happy with the name "buffered driver". "Bufferedness" isn't
what this
On Wed, 10 Nov 2010 10:26:15 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > This driver handles in-memory qemu-char driver operations, that's,
> > all writes to this driver are stored in an internal buffer. The
> > driver doesn't talk to the external world in any way.
>
> I'm n
