From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"airlied@redhat.com" <airlied@redhat.com>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>
Subject: Re: xf86-video-armada via UDL [was: Re: UDL's fbdev doesn't work for user-space apps]
Date: Tue, 5 Dec 2017 12:26:11 +0000 [thread overview]
Message-ID: <335eaaa2-b209-fb60-392f-93036050b406@synopsys.com> (raw)
In-Reply-To: <1512474815.4977.90.camel@synopsys.com>
On 05-12-2017 11:53, Alexey Brodkin wrote:
>
> From my note above about udl_drm_gem_mmap() being only used in case of Xserver
> I barely may conclude anything. Given my lack of knowledge of DRM guts
> especially
> when it comes to complicated cases with DMA buffer exports/imports I cannot say
> immediately if that's just improper implementation of
> udl_drm_gem_mmap() or not.
> Even though I do see some differences between implementation of file_operations->mmap()
> callback in UDL and
> say exynos_drm_gem_mmap() or qxl_mmap() it's not clear
> why this and that implementation was done.
Oh, I've seen this before. This is the same thing that arcpgu
used to do in the mmap callback! Please comment out the call to
update_vm_cache_attr() in the mmap callback and check if it works.
next prev parent reply other threads:[~2017-12-05 12:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 11:32 UDL's fbdev doesn't work for user-space apps Alexey Brodkin
2017-12-04 11:50 ` Jose Abreu
2017-12-04 13:16 ` xf86-video-armada via UDL [was: Re: UDL's fbdev doesn't work for user-space apps] Alexey Brodkin
2017-12-04 14:02 ` Jose Abreu
2017-12-04 14:53 ` Alexey Brodkin
2017-12-04 15:55 ` Jose Abreu
2017-12-04 16:00 ` Alexey Brodkin
2017-12-04 17:24 ` Jose Abreu
2017-12-04 17:29 ` Alexey Brodkin
2017-12-05 10:39 ` Jose Abreu
2017-12-05 11:53 ` Alexey Brodkin
2017-12-05 12:26 ` Jose Abreu [this message]
2017-12-05 14:47 ` Alexey Brodkin
2017-12-04 17:52 ` Emil Velikov
2017-12-09 17:20 ` UDL's fbdev doesn't work for user-space apps Pavel Machek
2017-12-12 19:48 ` Alexey Brodkin
2017-12-12 21:12 ` Pavel Machek
2017-12-12 21:58 ` Noralf Trønnes
2017-12-13 21:53 ` Alexey Brodkin
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=335eaaa2-b209-fb60-392f-93036050b406@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®