All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Inki Dae <inki.dae@samsung.com>,
	Joonyoung Shim <jy0922.shim@samsung.com>
Cc: dri-devel@lists.freedesktop.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/exynos: remove DRM_EXYNOS_GEM_MAP_OFFSET ioctl
Date: Thu, 02 Oct 2014 12:28:25 +0200	[thread overview]
Message-ID: <542D28C9.30809@gmail.com> (raw)
In-Reply-To: <542D2824.9020208@samsung.com>

On 02.10.2014 12:25, Inki Dae wrote:
> On 2014년 10월 02일 08:47, Joonyoung Shim wrote:
>> Hi Tomasz,
>>
>> On 10/02/2014 12:13 AM, Tomasz Figa wrote:
>>> Hi Inki,
>>>
>>> On 17.09.2014 15:48, Inki Dae wrote:
>>>> This interface and relevant codes aren't used anymore.
>>>>
>>>
>>> Hmm, I might be missing something, but after removing this IOCTL, how do
>>> we obtain an offset to pass to mmap()?
>>
>> There is DRM_IOCTL_MODE_MAP_DUMB, it can get mmap offset before mmap and
>> the offset is passed via mmap.
> 
> Exactly. That will lead us to more generic world.

OK. Thanks Joonyoung, Inki, for quick response. I was confused by name
of this IOCTL. I'll modify my code to use it.

Best regards,
Tomasz

  reply	other threads:[~2014-10-02 10:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 13:48 [PATCH 0/2] drm/exynos: use drm generic mmap interface Inki Dae
2014-09-17 13:48 ` [PATCH 1/2] drm/exynos: remove DRM_EXYNOS_GEM_MAP_OFFSET ioctl Inki Dae
2014-10-01 15:13   ` Tomasz Figa
2014-10-01 23:47     ` Joonyoung Shim
2014-10-02 10:25       ` Inki Dae
2014-10-02 10:28         ` Tomasz Figa [this message]
2014-09-17 13:48 ` [PATCH 2/2] drm/exynos: use drm generic mmap interface Inki Dae
2014-09-18  4:56   ` Joonyoung Shim
2014-09-18  5:15     ` Inki Dae
2014-09-18  5:19   ` [PATCH v2] " Inki Dae
2014-10-01 13:17   ` [PATCH 2/2] " Tomasz Figa
2014-10-02 10:22     ` Inki Dae
2014-11-18 22:09       ` Tobias Jakobi
2014-11-19  2:04         ` Inki Dae
2014-11-19  2:32           ` Tobias Jakobi
2014-09-17 15:18 ` [PATCH 0/2] " 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=542D28C9.30809@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=jy0922.shim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.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 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.