Re: [PATCH] drm: dumb scanout create/mmap for intel/radeon (v3)

From: Corbin Simpson <mostawesomedude@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: dumb scanout create/mmap for intel/radeon (v3)
Date: Thu, 6 Jan 2011 16:12:17 -0800	[thread overview]
Message-ID: <AANLkTi=k585dk-029UMfKEJzs8hucEPYrxwV+qbow9Wq@mail.gmail.com> (raw)
In-Reply-To: <1294355811-3225-1-git-send-email-airlied@gmail.com>

On Thu, Jan 6, 2011 at 3:16 PM, Dave Airlie <airlied@gmail.com> wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> This is just an idea that might or might not be a good idea,
> it basically adds two ioctls to create a dumb and map a dumb buffer
> suitable for scanout. The handle can be passed to the KMS ioctls to create
> a framebuffer.
>
> It looks to me like it would be useful in the following cases:
> a) in development drivers - we can always provide a shadowfb fallback.
> b) libkms users - we can clean up libkms a lot and avoid linking
> to libdrm_*.
> c) plymouth via libkms is a lot easier.
>
> Userspace bits would be just calls + mmaps. We could probably
> mark these handles somehow as not being suitable for acceleartion
> so as top stop people who are dumber than dumb.
>
> Signed-off-by: Dave Airlie <airlied@redhat.com>

Looks pretty reasonable. One thing from the IRC conversation on v2 was
about cursors -- were they going to be handled through this patch?

~ C.

-- 
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
<MostAwesomeDude@gmail.com>