On Wed, 30 May 2012 11:54:11 +0300
Alon Levy wrote:
> On Tue, May 29, 2012 at 01:44:35PM -0300, Luiz Capitulino wrote:
> > On Tue, 29 May 2012 17:51:50 +0300
> > Alon Levy wrote:
> >
> > > On Tue, May 29, 2012 at 10:38:20AM -0300, Luiz Capitulino wrote:
> > > > On Tue, 29 May 2012 09:25:40 +020
On Tue, May 29, 2012 at 01:44:35PM -0300, Luiz Capitulino wrote:
> On Tue, 29 May 2012 17:51:50 +0300
> Alon Levy wrote:
>
> > On Tue, May 29, 2012 at 10:38:20AM -0300, Luiz Capitulino wrote:
> > > On Tue, 29 May 2012 09:25:40 +0200
> > > Gerd Hoffmann wrote:
> > >
> > > > Hi,
> > > >
> > >
On Tue, 29 May 2012 17:51:50 +0300
Alon Levy wrote:
> On Tue, May 29, 2012 at 10:38:20AM -0300, Luiz Capitulino wrote:
> > On Tue, 29 May 2012 09:25:40 +0200
> > Gerd Hoffmann wrote:
> >
> > > Hi,
> > >
> > > >> How would that work? I have QXLInfo that only makes sense when the
> > > >> info
On Tue, May 29, 2012 at 10:38:20AM -0300, Luiz Capitulino wrote:
> On Tue, 29 May 2012 09:25:40 +0200
> Gerd Hoffmann wrote:
>
> > Hi,
> >
> > >> How would that work? I have QXLInfo that only makes sense when the
> > >> information is about a qxl device. Can't have opaque data in a QMP
> > >>
On Tue, 29 May 2012 09:25:40 +0200
Gerd Hoffmann wrote:
> Hi,
>
> >> How would that work? I have QXLInfo that only makes sense when the
> >> information is about a qxl device. Can't have opaque data in a QMP
> >> response, so would this be a "info display qxl" "info display cirrus"
> >> etc. o
On Tue, May 29, 2012 at 09:25:40AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> >> How would that work? I have QXLInfo that only makes sense when the
> >> information is about a qxl device. Can't have opaque data in a QMP
> >> response, so would this be a "info display qxl" "info display cirrus"
> >> e
Hi,
>> How would that work? I have QXLInfo that only makes sense when the
>> information is about a qxl device. Can't have opaque data in a QMP
>> response, so would this be a "info display qxl" "info display cirrus"
>> etc. or "info qxl"?
>
> You could show what's available and/or being used c
On Mon, 28 May 2012 16:36:16 +0300
Alon Levy wrote:
> On Mon, May 28, 2012 at 10:13:28AM -0300, Luiz Capitulino wrote:
> > On Mon, 28 May 2012 12:08:13 +0300
> > Alon Levy wrote:
> >
> > > On Fri, May 25, 2012 at 11:43:11AM -0300, Luiz Capitulino wrote:
> > > > On Thu, 24 May 2012 19:22:52 +030
On Mon, May 28, 2012 at 10:13:28AM -0300, Luiz Capitulino wrote:
> On Mon, 28 May 2012 12:08:13 +0300
> Alon Levy wrote:
>
> > On Fri, May 25, 2012 at 11:43:11AM -0300, Luiz Capitulino wrote:
> > > On Thu, 24 May 2012 19:22:52 +0300
> > > Alon Levy wrote:
> > >
> > > > For all devices print id,
On Mon, 28 May 2012 12:08:13 +0300
Alon Levy wrote:
> On Fri, May 25, 2012 at 11:43:11AM -0300, Luiz Capitulino wrote:
> > On Thu, 24 May 2012 19:22:52 +0300
> > Alon Levy wrote:
> >
> > > For all devices print id, mode and guest_bug status.
> >
> > Is qxl really tied to spice? In the meaning
On Fri, May 25, 2012 at 11:43:11AM -0300, Luiz Capitulino wrote:
> On Thu, 24 May 2012 19:22:52 +0300
> Alon Levy wrote:
>
> > For all devices print id, mode and guest_bug status.
>
> Is qxl really tied to spice? In the meaning that it's impossible to use it
> without spice? Wouldn't it be bette
On Thu, 24 May 2012 19:22:52 +0300
Alon Levy wrote:
> For all devices print id, mode and guest_bug status.
Is qxl really tied to spice? In the meaning that it's impossible to use it
without spice? Wouldn't it be better to have 'info display' instead?
> Known problems: Prints devices from highes
For all devices print id, mode and guest_bug status.
Known problems: Prints devices from highest id to lowest.
Signed-off-by: Alon Levy
---
This one builds. Fixed qapi-schema to say additions are for 1.2
hmp.c| 11 +++
hw/qxl.c | 22 ++
qapi-
13 matches
Mail list logo
