linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: dri-devel@lists.freedesktop.org
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	wayland-devel@lists.freedesktop.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	timofonic timofonic <timofonic@gmail.com>
Subject: Re: Future desktop on dumb frame buffers?
Date: Mon, 21 Mar 2011 21:13:44 +0000	[thread overview]
Message-ID: <201103212213.51565.linux@rainbow-software.org> (raw)
In-Reply-To: <AANLkTi=kRdC1LoHxqwKxYKZJf99vBEU=OmQoY+zS1dK-@mail.gmail.com>

On Monday 21 March 2011 20:34:38 Corbin Simpson wrote:
> On Mon, Mar 21, 2011 at 12:25 PM, 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.
> >
> > 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.
> >
> >> I know the graphic driver situation is quite bad on Linux, especially
> >> on the embedded world. Fbdev seems is still quite used there by binary
> >> blob drivers.
> >
> > Probably for a couple of reasons:
> >  1) inertia: fbdev has been around a lot longer, and provides most of
> >  what embedded devices need anyway
> >  2) feature set: why bother doing a full KMS driver if you're not
> >  going to use any of the additional features it would provide (output
> >  management, memory management, execution management)
>
> Related: We are still missing basic userspace tools (kmsset, e.g.),
> some kind of direct KMS console (kmscon would work, if it existed),
> and an xf86-video-modesetting which compiles and works (this is
> actually possible now, with some patches that landed in 2.6.38 for
> generic KMS access.)

This looks interesting. If existing *fb drivers could be easily converted to 
KMS (including 2D acceleration) and then used in X with a common driver, it 
would be great. Let's say, convert cyber2000fb driver to KMS and use it in X 
with 2D acceleration.

> This is important to me, as the various old drivers I've been hacking
> on won't be accepted upstream without some sort of userspace which can
> work with them. One of the big goals of KMS was a generic
> userspace-facing API, like FB, but without the suck.


-- 
Ondrej Zary

  parent reply	other threads:[~2011-03-21 21:13 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 [this message]
2011-03-21 21:46             ` Alex Deucher
2011-03-21 19:50         ` Geert Uytterhoeven
2011-03-21 19:56           ` Jesse Barnes
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=201103212213.51565.linux@rainbow-software.org \
    --to=linux@rainbow-software.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).