From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Romanick Subject: Re: RE: [Dri-devel] Memory management of AGP and VRAM Date: Fri, 07 May 2004 14:23:39 -0700 Sender: mesa3d-dev-admin@lists.sourceforge.net Message-ID: <409BFE5B.5020308@us.ibm.com> References: <16539.63659.810291.931565@xf11.fra.suse.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <16539.63659.810291.931565@xf11.fra.suse.de> Errors-To: mesa3d-dev-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Egbert Eich Cc: dri-devel , mesa3d-dev , fb-devel Egbert Eich wrote: > However chipset probing/display device probing and mode setting isn't > required to live in kernel space. Portability and system stability > arguments speak against it. In fact only Apple MAC users seem to > advocate this idea to be able to an initial video mode on their > systems. Allow me to speak up for users of IBM pSeries hardware or Sun SPARC hardware. Users of those systems face exactly the same issues as Mac users. I imagine most embedded systems will be in the same boat. Being forced to use a serial console for early boot messages is so 1980's. ;) The kernel doesn't need to have support for everything, but I think it's important to have at least minimal support. ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3