From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: timofonic timofonic <timofonic@gmail.com>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
wayland-devel@lists.freedesktop.org
Subject: Re: Future desktop on dumb frame buffers?
Date: Mon, 21 Mar 2011 19:56:05 +0000 [thread overview]
Message-ID: <20110321125605.15aa6a04@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTikAeQ=z-M3kW2zPgVRK-bmoiTeA5ktjjTokEybW@mail.gmail.com>
On Mon, 21 Mar 2011 20:50:20 +0100
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Mon, Mar 21, 2011 at 20:25, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > On Mon, 21 Mar 2011 19:19:43 +0000
> > timofonic timofonic <timofonic@gmail.com> wrote:
> >> So if KMS is so cool and provides many advantages over fbdev and
> >> such... Why isn't more widely used intead of still relying on fbdev?
> >> Why still using fbdev emulation (that is partial and somewhat broken,
> >> it seems) instead using KMS directly?
> >
> > Used by what? All three major GPU device classes have KMS support
> > (Intel, ATI, and nVidia). If you want it for a particular device, you
> > can always port it over.
>
> The three major GPU device classes on PC...
Yes, good point. :)
> > As for fbdev emulation, what's still using it? There's nothing
> > stopping projects from converting over; X and Wayland can already
> > handle KMS APIs just fine.
>
> Can Wayland handle fbdev APIs ...
Yes. Fundamentally, the Wayland protocol just assumes a way to share
buffers between processes. For the software raster version of the Qt
port, Kristian created a shmem interface for doing that to allow the
results of CPU rendering to be passed around without copying. On an
embedded device that would be one way to go.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-03-21 19:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 11:20 Future desktop on dumb frame buffers? Geert Uytterhoeven
2011-03-19 15:45 ` Rob Clark
2011-03-21 18:00 ` Jesse Barnes
2011-03-21 19:19 ` timofonic timofonic
[not found] ` <AANLkTimjOs8ZuKRUt1aOizhbRw2-Ni4bTPty-dKpZ-rz-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-21 19:25 ` Jesse Barnes
2011-03-21 19:34 ` Corbin Simpson
2011-03-21 19:59 ` Jesse Barnes
2011-03-21 21:13 ` Ondrej Zary
2011-03-21 21:46 ` Alex Deucher
2011-03-21 19:50 ` Geert Uytterhoeven
2011-03-21 19:56 ` Jesse Barnes [this message]
2011-03-21 20:08 ` Alex Deucher
2011-03-23 14:09 ` Robert Fekete
2011-03-24 11:05 ` Laurent Pinchart
2011-03-21 21:20 ` Alan Cox
[not found] ` <20110321212008.384711f0-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2011-03-21 21:22 ` Jesse Barnes
2011-03-21 21:37 ` Matt Turner
2011-04-04 9:40 ` Alan Cox
2011-03-22 15:26 ` Michal Suchanek
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=20110321125605.15aa6a04@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=timofonic@gmail.com \
--cc=wayland-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).