From: Otto Solares <solca@guug.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] neofb patches
Date: Thu, 29 Apr 2004 19:18:16 -0600 [thread overview]
Message-ID: <20040430011816.GC26704@guug.org> (raw)
In-Reply-To: <1083280337.8281.181.camel@thor.asgaard.local>
On Fri, Apr 30, 2004 at 01:12:17AM +0200, Michel Dänzer wrote:
> On Thu, 2004-04-29 at 19:52, Otto Solares wrote:
> > On Thu, Apr 29, 2004 at 03:01:13PM +0200, Michel Dänzer wrote:
> > > On Thu, 2004-04-29 at 03:07, Otto Solares wrote:
> > > > On Thu, Apr 29, 2004 at 12:26:41AM +0200, Michel Dänzer wrote:
> > > >
> > > > > A small low-level driver could handle this, which both the framebuffer
> > > > > device and the DRM use. Linus has proposed this approach, and I must say
> > > > > I like it.
> > > >
> > > > That should be fbdev without fbcon.
> > >
> > > I'm not sure that works: keep in mind that the DRM works on other OSs
> > > than Linux, and even on Linux some people may want to use the DRM
> > > without a framebuffer device. Neither should be a problem with a minimal
> > > base driver which does nothing more than hardware resource management
> > > and arbitration.
> >
> > Differents OSs have differents sources for DRM kernel side so
> > that's not a problem nor will affect others OSs than linux.
>
> Nope. Most of the code in the DRI CVS drm module is shared between OSs.
> Most of the shared code is hardware specific though, so if you change
> the interface to the hardware, either all the OSs will have to provide
> the new interface, or the code can no longer be shared, which would get
> us back to the code duplication horrors. I'd very much like to avoid
> that.
I don't see your point, nothing prevents using the shared code,
the idea is not to change the interface, just to have a single
graphics layer that handle that same interface. I know it could be
a pain to duplicate the fbdev into the cvs drm module, but with
proper file separations there could live the fbdev's drm code.
> > Yes, a minimal driver would do the work _NOW_.
>
> Why wouldn't it in the future?
Because we need a single and unified graphics layer for linux
in the very same way like the sound and input layers exists now.
A proper graphics layer based on fbdev_sysfs + libraries like the
ones Ben or Jon are working on + dri + hotplug + hal + udev + dbus
+ a good graphics servers (based on the unified layer) + toolkits
= a chance for linux to compete in the future with longhorn and
OSX. The graphics layer I am describing here is low-level and
must contain the basics needed for a graphics server. I am
working on one but i'm sure it would be useful to any Xserver
like the xserver from fd.o.
-otto
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next prev parent reply other threads:[~2004-04-30 1:17 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 1:14 [PATCH] neofb patches Alex Stewart
2004-04-21 17:47 ` James Simmons
2004-04-21 19:10 ` Antonino A. Daplas
2004-04-22 8:09 ` Geert Uytterhoeven
2004-04-23 23:27 ` James Simmons
2004-04-23 16:53 ` Alex Stewart
2004-04-23 20:03 ` James Simmons
2004-04-23 18:35 ` James Simmons
2004-04-23 19:54 ` James Simmons
2004-04-22 3:18 ` Alex Stewart
2004-04-22 20:57 ` James Simmons
2004-04-23 4:03 ` Alex Stewart
2004-04-23 6:43 ` Alex Stewart
2004-04-23 23:00 ` James Simmons
2004-04-23 23:00 ` [Linux-fbdev-devel] " James Simmons
2004-04-24 3:15 ` Randy.Dunlap
2004-04-24 7:08 ` Alex Stewart
2004-04-24 7:08 ` [Linux-fbdev-devel] " Alex Stewart
2004-04-25 3:10 ` James Simmons
2004-04-25 3:10 ` James Simmons
2004-04-25 3:09 ` James Simmons
2004-04-25 3:09 ` James Simmons
2004-04-24 17:29 ` Alex Stewart
2004-04-24 17:29 ` [Linux-fbdev-devel] " Alex Stewart
2004-04-25 0:55 ` James Simmons
2004-04-25 0:55 ` [Linux-fbdev-devel] " James Simmons
2004-04-26 18:12 ` Alex Stewart
2004-04-27 0:11 ` James Simmons
2004-04-27 1:15 ` Alex Stewart
2004-04-27 8:49 ` Geert Uytterhoeven
2004-04-27 10:12 ` Benjamin Herrenschmidt
2004-04-27 20:25 ` James Simmons
2004-04-27 22:48 ` John Zielinski
2004-04-27 23:10 ` Benjamin Herrenschmidt
2004-04-27 23:21 ` James Simmons
2004-04-27 23:25 ` Benjamin Herrenschmidt
2004-04-27 23:46 ` John Zielinski
2004-04-27 23:50 ` Benjamin Herrenschmidt
2004-04-28 0:38 ` John Zielinski
2004-04-28 0:41 ` Benjamin Herrenschmidt
2004-04-28 1:39 ` John Zielinski
2004-04-28 3:17 ` Alex Stewart
2004-04-28 3:18 ` Benjamin Herrenschmidt
2004-04-28 17:02 ` James Simmons
2004-04-28 4:36 ` John Zielinski
2004-04-28 4:56 ` Alex Stewart
2004-04-28 6:59 ` John Zielinski
2004-04-28 8:26 ` Geert Uytterhoeven
2004-04-28 22:00 ` John Zielinski
2004-04-28 0:29 ` Otto Solares
2004-04-28 0:54 ` Antonino A. Daplas
2004-04-28 1:15 ` Otto Solares
2004-04-28 1:21 ` John Zielinski
2004-04-28 16:53 ` James Simmons
2004-04-28 0:23 ` Otto Solares
2004-04-28 0:20 ` Otto Solares
2004-04-28 0:36 ` Benjamin Herrenschmidt
2004-04-28 7:08 ` Otto Solares
2004-04-28 8:27 ` Geert Uytterhoeven
2004-04-28 10:16 ` Michel Dänzer
2004-04-28 16:37 ` Otto Solares
2004-04-28 16:50 ` James Simmons
2004-04-28 22:26 ` Michel Dänzer
2004-04-28 23:42 ` Benjamin Herrenschmidt
2004-04-28 23:59 ` James Simmons
2004-04-29 1:06 ` Otto Solares
2004-04-29 1:20 ` Benjamin Herrenschmidt
2004-04-29 16:56 ` James Simmons
2004-04-29 21:57 ` Benjamin Herrenschmidt
2004-04-30 15:06 ` Ville Syrjälä
2004-04-30 16:50 ` James Simmons
2004-05-01 0:40 ` Otto Solares
2004-05-06 19:28 ` Mobility M1 refresh code problem 2.4.26? Richard Smith
2004-05-06 19:57 ` Mikael Eriksson
2004-05-06 20:35 ` Richard Smith
2004-05-06 20:42 ` Geert Uytterhoeven
2004-05-06 21:12 ` Richard Smith
2004-05-07 7:57 ` Mikael Eriksson
2004-05-07 14:11 ` Richard Smith
2004-05-07 15:34 ` Mikael Eriksson
2004-05-07 19:42 ` Richard Smith
2004-05-07 23:11 ` Mikael Eriksson
2004-04-29 8:32 ` [PATCH] neofb patches Geert Uytterhoeven
2004-04-29 1:07 ` Otto Solares
2004-04-29 1:23 ` Benjamin Herrenschmidt
2004-04-29 13:01 ` Michel Dänzer
2004-04-29 17:52 ` Otto Solares
2004-04-29 23:12 ` Michel Dänzer
2004-04-30 1:18 ` Otto Solares [this message]
2004-04-30 1:28 ` Michel Dänzer
2004-04-30 21:26 ` Otto Solares
2004-04-28 23:30 ` Benjamin Herrenschmidt
2004-04-28 17:39 ` James Simmons
2004-04-28 18:03 ` Geert Uytterhoeven
2004-04-28 22:46 ` John Zielinski
2004-04-27 8:56 ` Geert Uytterhoeven
2004-04-23 16:07 ` James Simmons
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=20040430011816.GC26704@guug.org \
--to=solca@guug.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michel@daenzer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.