From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: DRM_UDL and GPU under Xserver
Date: Thu, 5 Apr 2018 07:16:37 +0000 [thread overview]
Message-ID: <1522912595.4577.5.camel@synopsys.com> (raw)
In-Reply-To: <CAKMK7uG1_B-r+XxVzMusMOBd=udhp8EdL59f375AG5+MO02O4g@mail.gmail.com>
Hi Daniel,
On Thu, 2018-04-05@08:18 +0200, Daniel Vetter wrote:
> On Wed, Apr 4, 2018 at 10:06 PM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> > Hello,
> >
> > We're trying to use DisplayLink USB2-to-HDMI adapter to render GPU-accelerated graphics.
> > Hardware setup is as simple as a devboard + DisplayLink adapter.
> > Devboards we use for this experiment are:
> > * Wandboard Quad (based on IMX6 SoC with Vivante GPU) or
> > * HSDK (based on Synopsys ARC HS38 SoC with Vivante GPU as well)
> >
> > I'm sure any other board with DRM supported GPU will work, those we just used
> > as the very recent Linux kernels could be easily run on them both.
> >
> > Basically the problem is UDL needs to be explicitly notified about new data
> > to be rendered on the screen compared to typical bit-streamers that infinitely
> > scan a dedicated buffer in memory.
> >
> > In case of UDL there're just 2 ways for this notification:
> > 1) DRM_IOCTL_MODE_PAGE_FLIP that calls drm_crtc_funcs->page_flip()
> > 2) DRM_IOCTL_MODE_DIRTYFB that calls drm_framebuffer_funcs->dirty()
> >
> > But neither of IOCTLs happen when we run Xserver with xf86-video-armada driver
> > (see https://urldefense.proofpoint.com/v2/url?u=http-3A__git.arm.linux.org.uk_cgit_xf86-2Dvideo-2Darmada.git_log_-3Fh-3Dunstable-2Ddevel&d=DwIBaQ&
> > c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=oEAlP64L9vkuUs_k3kGwwwlN1WJbDMJbCo0uDhwKwwk&s=3ZHj-
> > 6JXZBLSTWg_4KMnL0VNi7z8c0RxHzj2U5ywVIw&e=).
> >
> > Is it something missing in Xserver or in UDL driver?
>
> Use the -modesetting driverr for UDL, that one works correctly.
If you're talking about "modesetting" driver of Xserver [1] then indeed
picture is displayed on the screen. But there I guess won't be any 3D acceleration.
At least that's what was suggested to me earlier here [2] by Lucas:
---------------------------->8---------------------------
For 3D acceleration to work under X you need the etnaviv specific DDX
driver, which can be found here:
http://git.arm.linux.org.uk/cgit/xf86-video-armada.git/log/?h=unstable-devel
---------------------------->8---------------------------
[1] https://cgit.freedesktop.org/xorg/xserver/tree/hw/xfree86/drivers/modesetting
[2] http://lists.infradead.org/pipermail/linux-snps-arc/2017-November/003031.html
-Alexey
next prev parent reply other threads:[~2018-04-05 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 20:06 DRM_UDL and GPU under Xserver Alexey Brodkin
2018-04-05 6:18 ` Daniel Vetter
2018-04-05 7:16 ` Alexey Brodkin [this message]
2018-04-05 9:32 ` Daniel Vetter
2018-04-05 10:10 ` Jose Abreu
2018-04-05 10:29 ` Lucas Stach
2018-04-05 10:59 ` Daniel Vetter
2018-04-05 11:10 ` Alexey Brodkin
2018-04-05 13:44 ` Daniel Vetter
2018-04-05 18:39 ` Alexey Brodkin
2018-04-09 8:31 ` Daniel Vetter
2018-04-09 8:55 ` Alexey Brodkin
2018-04-09 9:17 ` Daniel Vetter
2018-04-09 9:45 ` Alexey Brodkin
2018-04-13 15:52 ` Daniel Vetter
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=1522912595.4577.5.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@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