dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jakob Bornecrantz <jakob@vmware.com>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] vmwgfx: Emulate depth 32 framebuffers
Date: Mon, 24 Oct 2011 18:20:37 -0400	[thread overview]
Message-ID: <20111024222037.GE5527@phenom.dumpdata.com> (raw)
In-Reply-To: <1678380380.230236.1319493683484.JavaMail.root@zimbra-prod-mbox-2.vmware.com>

On Mon, Oct 24, 2011 at 03:01:23PM -0700, Jakob Bornecrantz wrote:
> 
> ----- Original Message -----
> > On Sat, Oct 22, 2011 at 10:29:33AM +0200, Thomas Hellstrom wrote:
> > > From: Jakob Bornecrantz <jakob@vmware.com>
> > > 
> > > Signed-off-by: Jakob Bornecrantz <jakob@vmware.com>
> > > Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
> > > ---
> > >  drivers/gpu/drm/vmwgfx/vmwgfx_kms.c |   10 +++++++++-
> > >  1 files changed, 9 insertions(+), 1 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > > b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > > index 39b99db..00ec619 100644
> > > --- a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > > +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> > > @@ -679,6 +679,7 @@ static int do_dmabuf_define_gmrfb(struct
> > > drm_file *file_priv,
> > >  				  struct vmw_private *dev_priv,
> > >  				  struct vmw_framebuffer *framebuffer)
> > >  {
> > > +	int depth = framebuffer->base.depth;
> > >  	size_t fifo_size;
> > >  	int ret;
> > >  
> > > @@ -687,6 +688,13 @@ static int do_dmabuf_define_gmrfb(struct
> > > drm_file *file_priv,
> > >  		SVGAFifoCmdDefineGMRFB body;
> > >  	} *cmd;
> > >  
> > > +	/* Emulate RGBA support, contrary to svga_reg.h this is not
> > > +	 * supported by hosts. This is only a problem if we are reading
> > 
> > Uh, what if it becomes supported at some point? Should there be some
> > check against the host version?
> > 
> > (Thinking that some user might be running this older driver with a
> > newer host that des support 32 - won't that cause issues?)
> 
> We can add a check then, from the point of view of userspace 32 bit
> framebuffers works fine. The problem is with the readback ioctl where
> the readback pixels alpha will be clobbered. We also don't support
> depths of 30 R10G10B10X2.
> 
> If we add support for depth 32 and/or depth 30 formats we can add
> params to tell userspace about that, right now there isn't really a
> point to them since they will always return not supported and we
> need to do any work around in userspace anyways.

<nods> sounds reasonable.
> 
> Cheers, Jakob.

      reply	other threads:[~2011-10-24 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22  8:29 [PATCH 1/2] vmwgfx: Emulate depth 32 framebuffers Thomas Hellstrom
2011-10-22  8:29 ` [PATCH 2/2] vmwgfx: Don't pass unused arguments to do_dirty functions Thomas Hellstrom
2011-10-24 21:25 ` [PATCH 1/2] vmwgfx: Emulate depth 32 framebuffers Konrad Rzeszutek Wilk
2011-10-24 22:01   ` Jakob Bornecrantz
2011-10-24 22:20     ` Konrad Rzeszutek Wilk [this message]

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=20111024222037.GE5527@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jakob@vmware.com \
    --cc=thellstrom@vmware.com \
    /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