From: "Michel Dänzer" <michel@daenzer.net>
To: Otto Solares <solca@guug.org>
Cc: James Simmons <jsimmons@infradead.org>,
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: [Linux-fbdev-devel] fbdv/fbcon pending problems
Date: Thu, 26 Feb 2004 16:26:57 +0100 [thread overview]
Message-ID: <1077809216.2681.107.camel@thor.asgaard.local> (raw)
In-Reply-To: <20040225031553.GC17390@guug.org>
On Wed, 2004-02-25 at 04:15, Otto Solares wrote:
>
> 4. Memory mappings.
> We can currently map the vmem and io regions in userspace. It
> current exists problems with highmem but in short it simply works
> for dumb chips or programable chips so specialized libs (like
> mesa-solo) can do a decent job.
I hope Mesa-solo doesn't bang the chip directly, does it? That would
mean root only.
And while we're brainstorming... :)
I'm not sure being able to map the whole video RAM is a good idea in the
long run either; at some point we probably need a centralized memory
manager, and I think ideally it should map the allocated regions
separately (which could allow for moving them between video RAM, GART
and system RAM transparently, e.g.) and only allow to use them for
acceleration by opaque handles (via the DRM or whatever). This would be
quite a lot of stuff in the kernel, but I'm not sure it can be done
safely in user space...
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
next prev parent reply other threads:[~2004-02-26 15:26 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
2004-02-25 21:42 ` James Simmons
2004-02-26 15:26 ` Michel Dänzer [this message]
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=1077809216.2681.107.camel@thor.asgaard.local \
--to=michel@daenzer.net \
--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 \
--cc=solca@guug.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).