dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
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:18:31 -0800	[thread overview]
Message-ID: <20110106161831.03c10d69@jbarnes-desktop> (raw)
In-Reply-To: <1294355811-3225-1-git-send-email-airlied@gmail.com>

On Fri,  7 Jan 2011 09:16:51 +1000
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.

Would extracting libwfb from the server and providing it as a standalone
fb access API from the server also fill these needs? It would be a
bigger API, but presumably would allow us to share fbs between early
boot and subsequent, accelerated usage. We'd still need to settle on
the basic allocation API, but we seem to manage that on the server
side...

-- 
Jesse Barnes, Intel Open Source Technology Center

      parent reply	other threads:[~2011-01-07  0:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 23:16 [PATCH] drm: dumb scanout create/mmap for intel/radeon (v3) Dave Airlie
2011-01-07  0:12 ` Chris Wilson
2011-01-07  0:12 ` Corbin Simpson
2011-01-07  0:18 ` Jesse Barnes [this message]

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=20110106161831.03c10d69@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).