From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: I.MX6 HDMI support in v4.2
Date: Tue, 15 Sep 2015 15:01:34 -0400 [thread overview]
Message-ID: <1442343694.2637.38.camel@pengutronix.de> (raw)
In-Reply-To: <20150915170444.GX21084@n2100.arm.linux.org.uk>
Am Dienstag, den 15.09.2015, 18:04 +0100 schrieb Russell King - ARM
Linux:
> On Tue, Sep 15, 2015 at 12:53:54PM -0400, Lucas Stach wrote:
> > Hi Russell,
> >
> > Am Dienstag, den 15.09.2015, 17:36 +0100 schrieb Russell King - ARM
> > Linux:
> > > On Tue, Sep 15, 2015 at 05:53:45PM +0200, Lucas Stach wrote:
> > > > It includes a new kernel<->userspace interface, so needs a
> > > > modified
> > > > xf86-video-armada to go with it. You can pick that up here:
> > > > git://git.pengutronix.de/git/lst/xf86-video-armada.git for-rmk
> > > >
> > > > Caution: the armada code is WIP and needs further cleanups. It
> > > > should
> > > > work though.
> > >
> > > And it needs updating to the latest version - you seem to be
> > > missing
> > > a whole load of changes, including the changes which update the
> > > kernel API.
> > >
> > > So... you seem to be talking about the kernel API having changed
> > > from
> > > the version which you picked up years ago, rather than the
> > > current
> > > version. It's really unclear what you're talking about.
> > >
> > What do you mean with missing a lot of stuff? The "for-rmk" branch
> > in
> > that repo is your upstream "unstable-devel" branch minus the few
> > XvBO
> > commits with my changes on top.
>
> Ah, probably because I haven't pushed the stuff out :)
>
> Anyway, I've taken two of your patches, reworking the second
> slightly:
>
> 1fec728 etnaviv: fix compilation without DRI2 support
> 1663382 make sure that system strndup doesn't collide with X.Org
> server version
>
> which are _both_ fixes, and would have been nice for them to have
> been
> sent in a timely manner.
>
Sorry about that. I'll try to single out the fixes more quickly going
forward.
> Looking at "etnaviv: fix XV resize for UYVY source format", this is
> wrong
> to the documentation for the GC320. Documentation which was around
> for
> the GC320 indicates that the _only_ YUV format it supports as a
> target
> is YUY2 with the vertical filter blit. It's very specifically worded
> to
> indicate that this is the only YUV target format which is supported.
> What testing have you done to prove uyvy support, and on which GPUs?
>
I've tested this on i.MX6Q hardware with some GStreamer pipelines using
the videotestsrc. Without this commit the GPU will write out only zerosin the first step, so the video image will show up as fully green after CSC.
I don't think I have that documentation you are talking about. Is this
doc under NDA?
Chapter "31.4.1.6 Filter BLT" of the i.MX6 RM seems to agree with you,
so this commit depends on unspecified behavior. But it fixes a real bug
where the GPU writes out only zeros to the intermediate buffer if the
source is UYVY, so videos show up as fully green after CSC. So this
needs more investigation.
> "etnaviv: align vximage buffer size to pagesize" I have issues with
> as
> well - mapping more memory than was passed to the X server is really
> not
> permissible. If we need the image size to be larger, we need to
> report
> a larger buffer size - and in fact, that's already done.
> QueryImageAttributes indicates that the image size is to be rounded
> up to a page size. The X server will reject smaller buffers at
> higher
> levels. So, this patch isn't required.
>
This does not seem to be be working. I've certainly seen GStreamer
pushing non-aligned buffers which cause the GEM import to fail.
Ignoring the real size may well be a GStreamer bug (I'll look into that
code), but the server doesn't seem to reject that.
> The last patch is your final one, I'll look at that at some point,
> but for now I'm pushing out the tree as it now stands.
>
If you're not going to look at this too soonish I can rebase that on
top of what you just pushed out and mybe clean it up some more. But
certainly not this week, as I'm physically away from any test hardware.
Regards,
Lucas
next prev parent reply other threads:[~2015-09-15 19:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 10:55 I.MX6 HDMI support in v4.2 Krzysztof Hałasa
2015-09-07 11:25 ` Russell King - ARM Linux
2015-09-07 14:04 ` Krzysztof Hałasa
2015-09-08 9:16 ` Russell King - ARM Linux
2015-09-08 11:01 ` Krzysztof Hałasa
2015-09-08 12:57 ` Russell King - ARM Linux
2015-09-08 14:59 ` Krzysztof Hałasa
2015-09-10 10:25 ` Krzysztof Hałasa
2015-09-10 10:49 ` Russell King - ARM Linux
2015-09-10 11:29 ` Krzysztof Hałasa
2015-09-17 7:21 ` Philipp Zabel
2015-09-17 8:38 ` Krzysztof Hałasa
2015-09-17 9:23 ` Russell King - ARM Linux
2015-09-08 10:45 ` Krzysztof Hałasa
2015-09-08 10:56 ` Lucas Stach
2015-09-08 11:01 ` Russell King - ARM Linux
2015-09-08 11:07 ` Lucas Stach
2015-09-08 11:29 ` Russell King - ARM Linux
2015-09-08 12:43 ` Lucas Stach
2015-09-08 13:40 ` Russell King - ARM Linux
2015-09-08 14:17 ` Robert Nelson
2015-09-08 14:45 ` Krzysztof Hałasa
2015-09-08 14:48 ` Lucas Stach
2015-09-08 15:55 ` Russell King - ARM Linux
2015-09-08 17:07 ` Jon Nettleton
2015-09-08 11:06 ` Krzysztof Hałasa
2015-09-14 8:39 ` Krzysztof Hałasa
2015-09-15 8:24 ` Krzysztof Hałasa
2015-09-15 10:12 ` Russell King - ARM Linux
2015-09-15 11:01 ` Krzysztof Hałasa
2015-09-15 14:29 ` Russell King - ARM Linux
2015-09-15 16:53 ` Krzysztof Hałasa
2015-09-15 15:53 ` Lucas Stach
2015-09-15 16:36 ` Russell King - ARM Linux
2015-09-15 16:53 ` Lucas Stach
2015-09-15 17:04 ` Russell King - ARM Linux
2015-09-15 19:01 ` Lucas Stach [this message]
2015-09-28 14:48 ` xf86-video-armada + etnaviv (Was: Re: I.MX6 HDMI support in v4.2) Lucas Stach
2015-09-28 15:24 ` Russell King - ARM Linux
2015-09-28 15:40 ` Lucas Stach
2015-09-28 16:50 ` Russell King - ARM Linux
2015-09-29 8:28 ` Lucas Stach
2015-09-29 8:41 ` Russell King - ARM Linux
2015-09-29 9:01 ` Lucas Stach
2015-09-15 16:57 ` I.MX6 HDMI support in v4.2 Krzysztof Hałasa
2015-09-16 7:57 ` Krzysztof Hałasa
2015-09-16 15:52 ` Lucas Stach
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=1442343694.2637.38.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).