From owner-freebsd-sparc64@FreeBSD.ORG  Tue Dec  9 15:45:54 2003
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 758)
	id B4A0E16A4CF; Tue,  9 Dec 2003 15:45:54 -0800 (PST)
Date: Tue, 9 Dec 2003 15:45:54 -0800
From: Kris Kennaway <kris@FreeBSD.org>
To: Wilko Bulte <wkb@freebie.xs4all.nl>
Message-ID: <20031209234554.GC15583@hub.freebsd.org>
References: <20031203230916.GA70189@xor.obsecurity.org>
	<20031204142855.GB79411@xor.obsecurity.org>
	<20031204105430.D78277@carver.gumbysoft.com>
	<20031209135843.GA83083@sorted.org> <20031209190255.GB10414@hub.freebsd.org>
	<20031209234408.GA46900@freebie.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031209234408.GA46900@freebie.xs4all.nl>
User-Agent: Mutt/1.4.1i
cc: Kris Kennaway <kris@FreeBSD.ORG>
cc: sparc64@FreeBSD.ORG
Subject: Re: syscons by default?
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2003 23:45:54 -0000

On Wed, Dec 10, 2003 at 12:44:08AM +0100, Wilko Bulte wrote:
> On Tue, Dec 09, 2003 at 11:02:55AM -0800, Kris Kennaway wrote:
> > 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 XFree86
> > > > can nab it later.  I see that the creator code handles the case where its
> > > > 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. 
> > > 
> > > Is it not possible to write shim driver that falls back onto the OBP 
> > > 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.
> 
> Should I interpret that as "the Creator3D does not have the problem" ?

Creator3D is the supported graphics card.  If you have one, you can run syscons and XFree86.

Kris