linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven@powerlinux.fr>
To: Denis Oliver Kropp <dok@directfb.org>
Cc: directfb-users@directfb.org, "Brian G. Rhodes" <bgr@acdstar.com>,
	linux-fbdev-devel@lists.sourceforge.net,
	directfb-dev@directfb.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [directfb-dev] [directfb-users] DirectFB without FBDev
Date: Sat, 31 May 2008 08:45:01 +0200	[thread overview]
Message-ID: <20080531064501.GA7526@powerlinux.fr> (raw)
In-Reply-To: <4840F060.7090500@directfb.org>

On Sat, May 31, 2008 at 08:29:52AM +0200, Denis Oliver Kropp wrote:
> Sven Luther wrote:
> >Yes, but given that the kernel already has 2 "graphical" subsystems, fbdev
> >an drm, the reticence of Linus to merge in the fbdev back then, and the
> >failure of the ggi/kgi project, i wonder if it makes sense to try to add
> >yet another system.
> 
> I wouldn't try to add another system either, but write small, specialized 
> and
> optimized kernel modules suited best for the way the hardware works to take 
> as
> most advantage as possible. The example shows that 600 lines of hardware 
> plus
> 200 lines of Linux code suffice in the SH7722 case.

The risk is ending with a bunch of different such kernel modules without
any unified kernel-userland interface, and it will end up in a mess,
just like the different powerpc embedded board support ended up with a
huge in-kernel mess which is beign fixed right now.

> >In my opinion, what would make sense would be to disucss with the fbdev
> >and drm/xorg folk, as well as the vendors out there, to obtain a single
> >unified "graphical" driver, on which fbdev and xorg/drm functionality
> >can be built, and which allows us to take advantage of the various
> >functionality of the graphic chips, and which is designed, not only for
> >high end desktop/workstation graphic cards, but also for embedded
> >chipsets.
> 
> A single unified solution would be nice, but it's always a trade off. For

Why should there be a tradeoff ? The kernel space part should expose the
functionality of the hardware, and there is not thousand of ways to do
this, and the needs of all the userland users of this are pretty much
the same, or at least similar.

> embedded chipsets there's a unified solution in user space as well as for
> desktops, while the former can be used for desktops with limitations and
> the latter can be used for embedded with overhead.
> 
User space is easy, its the kernel space which is the problem.

Friendly,

Sven Luther

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-05-31  6:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 14:59 DirectFB without FBDev Denis Oliver Kropp
2008-05-28 17:04 ` Geert Uytterhoeven
2008-05-28 17:20   ` Denis Oliver Kropp
     [not found]     ` <483D9453.1080700-iGvX3keArt1g9hUCZPvPmw@public.gmane.org>
2008-05-28 17:53       ` [Linux-fbdev-devel] " Brian G. Rhodes
2008-05-28 18:07         ` [directfb-users] " Denis Oliver Kropp
2008-05-28 18:24           ` Alex Deucher
     [not found]             ` <a728f9f90805281124y53df86e7n7ae1918ac97907fc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-28 18:57               ` [Linux-fbdev-devel] " Denis Oliver Kropp
2008-05-28 19:33                 ` [directfb-users] " Alex Deucher
2008-05-28 18:55           ` Brian G. Rhodes
     [not found]             ` <483DAAB7.6080208-3mWahjwryh5BDgjK7y7TUQ@public.gmane.org>
2008-05-28 19:11               ` [Linux-fbdev-devel] " Denis Oliver Kropp
2008-05-28 19:38                 ` [directfb-users] " Brian G. Rhodes
     [not found]           ` <483D9F4E.4000707-iGvX3keArt1g9hUCZPvPmw@public.gmane.org>
2008-05-29 16:54             ` [directfb-dev] [Linux-fbdev-devel] " Sven Luther
2008-05-31  6:08               ` [directfb-dev] [directfb-users] " Denis Oliver Kropp
2008-05-31  6:21                 ` Sven Luther
2008-05-31  6:29                   ` Denis Oliver Kropp
2008-05-31  6:45                     ` Sven Luther [this message]
     [not found]                       ` <20080531064501.GA7526-XkLrfMvk983aVgXGlvhGPA@public.gmane.org>
2008-05-31 20:32                         ` George Tsalikis
2008-06-01  7:10                           ` [directfb-dev] " Denis Oliver Kropp
     [not found]                             ` <48424B49.8080202-iGvX3keArt1g9hUCZPvPmw@public.gmane.org>
2008-06-01  9:20                               ` [directfb-dev] " George Tsalikis
2008-06-01  9:38                                 ` Denis Oliver Kropp
2008-05-28 17:55     ` Geert Uytterhoeven
2008-05-28 18:33       ` Denis Oliver Kropp
     [not found] ` <483D7344.6030503-iGvX3keArt1g9hUCZPvPmw@public.gmane.org>
2008-06-01  9:31   ` [directfb-dev] " Denis Oliver Kropp
     [not found]     ` <48426C76.5080606-iGvX3keArt1g9hUCZPvPmw@public.gmane.org>
2008-06-01 11:57       ` Denis Oliver Kropp

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=20080531064501.GA7526@powerlinux.fr \
    --to=sven@powerlinux.fr \
    --cc=bgr@acdstar.com \
    --cc=directfb-dev@directfb.org \
    --cc=directfb-users@directfb.org \
    --cc=dok@directfb.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).