From: Otto Solares <solca@guug.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: fbdv/fbcon pending problems
Date: Thu, 26 Feb 2004 14:12:16 -0600 [thread overview]
Message-ID: <20040226201216.GH17390@guug.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0402261941520.20525-100000@phoenix.infradead.org>
On Thu, Feb 26, 2004 at 07:45:47PM +0000, James Simmons wrote:
>
> > Exactly, that's the whole point, if you want userland accel you must disable
> > kernel land accel. That's was my question against acceleration work inside
> > the kernel. Nobody use it in userland and is the stability devil in fbdev.
> > If you want acceleration in userland there is mesa-solo or directfb or console-sdl.
> >
> > In short acceleration belongs to specialized libs not the kernel.
> >
> > Why accel it is needed for font drawing?, i am pretty sure my 8bit video old
> > sparc doesn't have any accel and is pretty capable for drawing fonts.
>
> Because we are going to run into graphics hardware that don't have
> framebuffers. The solution is the one we are approaching now. That fbcon
> be a client like userland apps to the accel engine. You will see it will
> all work out :-)
Oh, that fact changes everything :)
-otto
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-26 20:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 0:53 fbdv/fbcon pending problems Benjamin Herrenschmidt
2004-02-23 15:52 ` Johannes Stezenbach
2004-02-23 18:59 ` James Simmons
2004-02-23 22:50 ` Benjamin Herrenschmidt
2004-02-24 1:19 ` James Simmons
2004-02-24 8:37 ` Geert Uytterhoeven
2004-02-24 8:33 ` Benjamin Herrenschmidt
2004-02-23 20:35 ` Thorsten Kranzkowski
2004-02-23 22:18 ` James Simmons
2004-02-24 2:37 ` Otto Solares
2004-02-24 8:35 ` Geert Uytterhoeven
2004-02-24 17:21 ` [Linux-fbdev-devel] " James Simmons
2004-02-24 21:41 ` Otto Solares
2004-02-25 1:21 ` James Simmons
2004-02-25 1:26 ` Benjamin Herrenschmidt
2004-02-25 21:24 ` James Simmons
2004-02-25 23:46 ` Benjamin Herrenschmidt
2004-02-26 0:20 ` James Simmons
2004-02-26 0:33 ` Benjamin Herrenschmidt
2004-02-26 1:11 ` [Linux-fbdev-devel] " James Simmons
2004-02-25 1:29 ` Benjamin Herrenschmidt
2004-02-25 2:18 ` Otto Solares
2004-02-25 2:33 ` Benjamin Herrenschmidt
2004-02-25 3:15 ` Otto Solares
2004-02-25 11:41 ` Geert Uytterhoeven
2004-02-25 14:01 ` Sven Luther
2004-02-25 14:08 ` Geert Uytterhoeven
2004-02-25 21:43 ` James Simmons
2004-02-26 19:40 ` Otto Solares
2004-02-26 19:45 ` James Simmons
2004-02-26 20:12 ` Otto Solares [this message]
2004-02-25 21:42 ` James Simmons
2004-02-26 15:26 ` [Linux-fbdev-devel] " Michel Dänzer
2004-02-24 5:57 ` Stuart Young
2004-02-24 8:36 ` Geert Uytterhoeven
2004-02-25 7:14 ` Stuart Young
2004-02-26 15:11 ` [Linux-fbdev-devel] " Michel Dänzer
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=20040226201216.GH17390@guug.org \
--to=solca@guug.org \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).