qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ondrej Zajicek <santiago@crfreenet.org>
Cc: Vincent Hanquez <tab@snarc.org>,
	linux-fbdev-devel@lists.sourceforge.net,
	Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Linux-fbdev-devel] [Qemu-devel] Re: [PATCH] Add VirtIO Frame Buffer Support
Date: Tue, 03 Nov 2009 18:05:13 +0200	[thread overview]
Message-ID: <4AF054B9.9060204@redhat.com> (raw)
In-Reply-To: <20091103152911.GA8266@localhost>

On 11/03/2009 05:29 PM, Ondrej Zajicek wrote:
> On Tue, Nov 03, 2009 at 11:38:18AM +0200, Avi Kivity wrote:
>    
>> On 11/03/2009 01:25 PM, Vincent Hanquez wrote:
>>      
>>> not sure if i'm missing the point here, but couldn't it be hypothetically
>>> extended to stuff 3d (or video&   more 2d accel ?) commands too ? I can't
>>> imagine the cirrus or stdvga driver be able to do that ever ;)
>>>
>>>        
>> cirrus has pretty good 2d acceleration.  3D is a mega-project though.
>>      
> Cirrus has no blending/compositing hardware support.
> Paravirtualized graphics can easily support full XRender-style
> 2D acceleration.
>    

What do that entail? 3/4 operand raster ops?

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-11-03 16:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 22:09 [Qemu-devel] [PATCH] Add VirtIO Frame Buffer Support Alexander Graf
     [not found] ` <20091102223249.GC22301@localhost>
     [not found]   ` <D295329B-4DE0-4935-8C6B-D45042E72826@suse.de>
2009-11-02 23:24     ` [Qemu-devel] Re: [Linux-fbdev-devel] " Alexander Graf
2009-11-02 23:57       ` Ondrej Zajicek
2009-11-02 23:59         ` Alexander Graf
2009-11-03  6:21 ` [Qemu-devel] " Avi Kivity
2009-11-03  6:22   ` Alexander Graf
2009-11-03  6:24     ` Avi Kivity
2009-11-03  6:27       ` Alexander Graf
2009-11-03  6:34         ` Avi Kivity
2009-11-03  6:39           ` Alexander Graf
2009-11-03  7:43             ` Avi Kivity
2009-11-03  7:50               ` Alexander Graf
2009-11-03  8:20                 ` Avi Kivity
2009-11-03  8:26                   ` Alexander Graf
2009-11-03  8:53                     ` Avi Kivity
2009-11-03 15:14                       ` Anthony Liguori
2009-11-03 15:57                         ` Avi Kivity
2009-11-03 11:25             ` Vincent Hanquez
2009-11-03  9:38               ` Avi Kivity
2009-11-03 15:29                 ` [Linux-fbdev-devel] " Ondrej Zajicek
2009-11-03 16:05                   ` Avi Kivity [this message]
2009-11-03 16:53                     ` Ondrej Zajicek
2009-11-03 17:33                     ` Paolo Bonzini
2009-11-04 16:09                 ` Vincent Hanquez
2009-11-04 16:35                   ` Anthony Liguori
2009-11-05  9:04                     ` Avi Kivity
2009-11-06  2:39   ` Jamie Lokier
2009-11-06  3:05     ` Anthony Liguori
2009-11-05 11:36 ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AF054B9.9060204@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --cc=santiago@crfreenet.org \
    --cc=tab@snarc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).