Date: Tue, 9 Dec 2003 11:02:55 -0800 From: Kris Kennaway <kris@FreeBSD.org> To: Pete Bentley <pete@sorted.org> Cc: sparc64@freebsd.org Subject: Re: syscons by default? Message-ID: <20031209190255.GB10414@hub.freebsd.org> In-Reply-To: <20031209135843.GA83083@sorted.org> References: <20031203230916.GA70189@xor.obsecurity.org> <20031204142855.GB79411@xor.obsecurity.org> <20031204105430.D78277@carver.gumbysoft.com> <20031209135843.GA83083@sorted.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 09, 2003 at 01:58:43PM +0000, Pete Bentley wrote: > On Thu, Dec 04, 2003 at 11:03:52AM -0800, Doug White wrote: > > Which is really pesky since XFree86 will work on the ATI fine, we just > > need a way of having syscons attach the display but not use it so XFree= 86 > > can nab it later. I see that the creator code handles the case where i= ts > > not the chosen console; I wonder if some shim driver that goes through = the > > motions but doesn't implement any of the fb functions might work.=20 >=20 > Is it not possible to write shim driver that falls back onto the OBP=20 > functions for text mode output? Sure they're slow, but at least > you could potentially get text working under syscons, then XFree86 > can grab the device later and do its thing. I'm sure it's possible - if you could investigate this it would be greatly appreciated by the rest of the users without Creator3D hardware. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031209190255.GB10414>