[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166704843772.1532410.11915201216204142960.b4-ty@sntech.de>
Date: Sat, 29 Oct 2022 15:00:46 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: John Keeping <john@...anate.com>, dri-devel@...ts.freedesktop.org
Cc: Heiko Stuebner <heiko@...ech.de>,
linux-arm-kernel@...ts.infradead.org,
Daniel Vetter <daniel@...ll.ch>,
Johan Jonker <jbx6244@...il.com>,
linux-rockchip@...ts.infradead.org,
Thomas Zimmermann <tzimmermann@...e.de>,
Sandy Huang <hjc@...k-chips.com>, linux-kernel@...r.kernel.org,
David Airlie <airlied@...il.com>
Subject: Re: [PATCH] drm/rockchip: fix fbdev on non-IOMMU devices
On Thu, 20 Oct 2022 19:12:47 +0100, John Keeping wrote:
> When switching to the generic fbdev infrastructure, it was missed that
> framebuffers were created with the alloc_kmap parameter to
> rockchip_gem_create_object() set to true. The generic infrastructure
> calls this via the .dumb_create() driver operation and thus creates a
> buffer without an associated kmap.
>
> alloc_kmap only makes a difference on devices without an IOMMU, but when
> it is missing rockchip_gem_prime_vmap() fails and the framebuffer cannot
> be used.
>
> [...]
Applied, thanks!
[1/1] drm/rockchip: fix fbdev on non-IOMMU devices
commit: ab78c74cfc5a3caa2bbb7627cb8f3bca40bb5fb0
Best regards,
--
Heiko Stuebner <heiko@...ech.de>
Powered by blists - more mailing lists