[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a9b3996-38fb-e4f1-1e25-436f0f09f510@osg.samsung.com>
Date: Wed, 19 Oct 2016 16:56:08 -0600
From: Shuah Khan <shuahkh@....samsung.com>
To: Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>,
Inki Dae <inki.dae@...sung.com>, jy0922.shim@...sung.com,
sw0312.kim@...sung.com, kyungmin.park@...sung.com,
airlied@...ux.ie, kgene@...nel.org,
Krzysztof Kozlowski <krzk@...nel.org>
Cc: dri-devel@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
Shuah Khan <shuahkh@....samsung.com>
Subject: Re: exynos-drm: display manager fails to start without IOMMU problem
On 10/19/2016 10:23 AM, Tobias Jakobi wrote:
> Hello Shuah,
>
> just a short note that more misleading comments about default allocation
> flags can be found in libdrm.
>
> https://cgit.freedesktop.org/mesa/drm/tree/exynos/exynos_drm.c
>
> See e.g. the comment for exynos_bo_create().
>
> In my opinion, the whole approach to _set_ a bit to get non-contigious
> memory is messed up. It would make more sense to me to set a bit to
> request an additional property (here "being contiguous") of the memory.
>
> Anyway, clearing up this situation is highly appreciated!
>
> More comments below.
>
> With best wishes,
> Tobias
>
Hi Tobias,
Thanks for the note. Yes the comments are confusing. It seems like
some old assumptions are persisting. I will fix these as well.
-- Shuah
Powered by blists - more mailing lists