[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [5335] Change the way video graphics adapter is selecte
From: |
Blue Swirl |
Subject: |
Re: [Qemu-devel] [5335] Change the way video graphics adapter is selected |
Date: |
Sun, 28 Sep 2008 18:46:20 +0300 |
On 9/28/08, Anthony Liguori <address@hidden> wrote:
> Blue Swirl wrote:
>
> > On 9/28/08, malc <address@hidden> wrote:
> >
> >
> > > Revision: 5335
> > >
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5335
> > > Author: malc
> > > Date: 2008-09-28 00:42:05 +0000 (Sun, 28 Sep 2008)
> > >
> > > Log Message:
> > > -----------
> > > Change the way video graphics adapter is selected
> > >
> > > Instead of having (current)three command line switches -std-vga,
> > > -cirrusvga and -vmwarevga, provide one -vga switch which takes
> > > an argument, so that:
> > > qemu -std-vga becomes qemu -vga std
> > > qemu -cirrusvga becomes qemu -vga cirrus
> > > qemu -vmwarevga becomes qemu -vga vmware
> > >
> > >
> >
> > I'd prefer a more generic syntax, like -drive options:
> > -displayhw model=vga,type=std
> > -displayhw model=vga,type=std
> > -displayhw model=vga,type=std
> > -displayhw model=tcx,type=hardwarecursor
> >
> >
>
> I think this would quickly rat hole since it requires rewriting a huge
> amount of code.
I forgot to change the copied part, I meant to write:
-displayhw model=vga,type=std
-displayhw model=vga,type=cirrrus
-displayhw model=vga,type=vmware
-displayhw model=tcx,type=hardwarecursor
These options should be (for now) mutually exclusive, so you could
select only one. I think the code changes would be limited to vl.c,
with similar parsing to what is done for -drive. The devices would not
be changed at this stage. I can't see how this would become any mess,
what problems you foresee?
> > Then this option would be useful for non-VGA targets. I don't see -vga
> > xxx as an improvement over -xxx-vga.
> >
> >
>
> If the next steps are creating a mechanism to register VGA hw emulation,
> then I think this is a step in the right direction.
>
> I think we have to get to a place where most hardware devices are
> registered within a generic frame work before we start trying to expose that
> to the user.
Maybe. It would be great to get a config file.