From: Mark yao <mark.yao@rock-chips.com>
To: David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
Russell King <linux@arm.linux.org.uk>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] drm/rockchip: import dma_buf to gem
Date: Tue, 17 Nov 2015 16:01:21 +0800 [thread overview]
Message-ID: <564ADED1.7090208@rock-chips.com> (raw)
In-Reply-To: <20151116162547.GE16848@phenom.ffwll.local>
On 2015年11月17日 00:25, Daniel Vetter wrote:
> On Tue, Nov 10, 2015 at 05:11:57PM +0800, Mark Yao wrote:
>> >We want to display a buffer allocated by other driver, need import
>> >the buffer to gem.
> Does this work with some open-source driver/userspace or is this for the
> proprietary stack only? A bit a grey area I guess, but if it's only for
> the proprietary stack I think it shouldn't land in upstream - making sure
> it works with open-source (e.g. Xorg prime) first would be good.
> -Daniel
>
Hi Daniel
It works on open-source with following stack:
ion -> dma_fd -> prime fd to handle -> drm -> vop
ion is the android ION memory allocator, its driver at
upstream-kernel/drivers/staging/android/ion.
We have some application use ion on android, and want to port to
Xorg side.
Thanks
--
Mark Yao
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: mark.yao@rock-chips.com (Mark yao)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] drm/rockchip: import dma_buf to gem
Date: Tue, 17 Nov 2015 16:01:21 +0800 [thread overview]
Message-ID: <564ADED1.7090208@rock-chips.com> (raw)
In-Reply-To: <20151116162547.GE16848@phenom.ffwll.local>
On 2015?11?17? 00:25, Daniel Vetter wrote:
> On Tue, Nov 10, 2015 at 05:11:57PM +0800, Mark Yao wrote:
>> >We want to display a buffer allocated by other driver, need import
>> >the buffer to gem.
> Does this work with some open-source driver/userspace or is this for the
> proprietary stack only? A bit a grey area I guess, but if it's only for
> the proprietary stack I think it shouldn't land in upstream - making sure
> it works with open-source (e.g. Xorg prime) first would be good.
> -Daniel
>
Hi Daniel
It works on open-source with following stack:
ion -> dma_fd -> prime fd to handle -> drm -> vop
ion is the android ION memory allocator, its driver at
upstream-kernel/drivers/staging/android/ion.
We have some application use ion on android, and want to port to
Xorg side.
Thanks
--
?ark Yao
WARNING: multiple messages have this Message-ID (diff)
From: Mark yao <mark.yao@rock-chips.com>
To: David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
Russell King <linux@arm.linux.org.uk>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] drm/rockchip: import dma_buf to gem
Date: Tue, 17 Nov 2015 16:01:21 +0800 [thread overview]
Message-ID: <564ADED1.7090208@rock-chips.com> (raw)
In-Reply-To: <20151116162547.GE16848@phenom.ffwll.local>
On 2015年11月17日 00:25, Daniel Vetter wrote:
> On Tue, Nov 10, 2015 at 05:11:57PM +0800, Mark Yao wrote:
>> >We want to display a buffer allocated by other driver, need import
>> >the buffer to gem.
> Does this work with some open-source driver/userspace or is this for the
> proprietary stack only? A bit a grey area I guess, but if it's only for
> the proprietary stack I think it shouldn't land in upstream - making sure
> it works with open-source (e.g. Xorg prime) first would be good.
> -Daniel
>
Hi Daniel
It works on open-source with following stack:
ion -> dma_fd -> prime fd to handle -> drm -> vop
ion is the android ION memory allocator, its driver at
upstream-kernel/drivers/staging/android/ion.
We have some application use ion on android, and want to port to
Xorg side.
Thanks
--
Mark Yao
next prev parent reply other threads:[~2015-11-17 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 9:11 [RESEND PATCH] drm/rockchip: import dma_buf to gem Mark Yao
2015-11-10 9:11 ` Mark Yao
2015-11-10 9:11 ` Mark Yao
2015-11-16 16:25 ` Daniel Vetter
2015-11-16 16:25 ` Daniel Vetter
2015-11-16 16:25 ` Daniel Vetter
2015-11-17 8:01 ` Mark yao [this message]
2015-11-17 8:01 ` Mark yao
2015-11-17 8:01 ` Mark yao
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=564ADED1.7090208@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.