From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: The hw does not support source offsets into a YUV linear fb
Date: Tue, 18 Dec 2012 23:26:47 +0000 [thread overview]
Message-ID: <20ab6b$5e7me2@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <453bf0$6unqdb@azsmga001.ch.intel.com>
On Tue, 18 Dec 2012 23:03:02 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, 18 Dec 2012 23:57:05 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Tue, Dec 18, 2012 at 11:51 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > > As we can only pass in the base address of the first plane, we can not
> > > control the offset into the subsampled chroma planes. This means that we
> > > cannot support a source offset into a YUV* linear framebuffer. However,
> > > for tiled framebuffers we can tell the hardware which pixels to read
> > > from. So if we see a source offset into a linear YUV framebuffer, report
> > > the invalid value back to userspace.
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Aren't all the yuv formats we support packet planar? So I think we
> > should be able to support source offsets, as long as x is even ...
> > Probably not worth the bother though.
Ok, double-checked and they are using a packed format, so it should be
possible given the single linear offset and a co-operative userspace to
pass in valid x/y offsets.
I'm no longer trying to use this in the ddx, so you can leave it in
until someone with a little more clue feels like tackling it.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-12-20 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 22:51 [PATCH] drm/i915: The hw does not support source offsets into a YUV linear fb Chris Wilson
2012-12-18 22:57 ` Daniel Vetter
2012-12-18 23:03 ` Chris Wilson
2012-12-18 23:26 ` Chris Wilson [this message]
2012-12-19 11:56 ` Ville Syrjälä
2012-12-19 12:03 ` Chris Wilson
2012-12-19 12:14 ` Ville Syrjälä
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='20ab6b$5e7me2@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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