From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michel =?ISO-8859-1?Q?D=E4nzer?= Subject: Re: [Linux-fbdev-devel] fbdv/fbcon pending problems Date: Thu, 26 Feb 2004 16:26:57 +0100 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <1077809216.2681.107.camel@thor.asgaard.local> References: <20040224214106.GA17390@guug.org> <20040225031553.GC17390@guug.org> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20040225031553.GC17390@guug.org> List-Id: Cc: James Simmons , Geert Uytterhoeven , Benjamin Herrenschmidt , Linux Fbdev development list , Linux Kernel list On Wed, 2004-02-25 at 04:15, Otto Solares wrote:=20 >=20 > 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 th= e 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... --=20 Earthling Michel D=C3=A4nzer | Debian (powerpc), X and DRI dev= eloper Libre software enthusiast | http://svcs.affero.net/rm.php?r=3Ddaen= zer