From owner-freebsd-ppc@FreeBSD.ORG Tue Jun 27 21:17:39 2006 Return-Path: X-Original-To: freebsd-ppc@freebsd.org Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EDE416A4C8 for ; Tue, 27 Jun 2006 21:17:39 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 269844520A for ; Tue, 27 Jun 2006 19:51:03 +0000 (GMT) (envelope-from grehan@freebsd.org) Received: from [10.33.24.110] (nat-198-95-226-228.netapp.com [198.95.226.228]) by dommail.onthenet.com.au (MOS 3.5.7-GR) with ESMTP id BXR16182 (AUTH peterg@ptree32.com.au); Wed, 28 Jun 2006 05:50:57 +1000 (EST) Message-ID: <44A18C3E.6090507@freebsd.org> Date: Tue, 27 Jun 2006 12:51:26 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8b) Gecko/20051014 MIME-Version: 1.0 To: matt@genesi-usa.com References: <025101c69a0a$32fc16d0$99dfdfdf@bakuhatsu.net> In-Reply-To: <025101c69a0a$32fc16d0$99dfdfdf@bakuhatsu.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: FreeBSD 6.0 on Pegasos/ODW X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2006 21:17:39 -0000 >> Is there a serial port on the Pegasos ? > > Yep. Standard PC serial UART, at the standard PC IO addresses. It should be possible to get the uart(4) driver to use this but it will take some work. > Going to do a boot -v now. > > Nope, no difference. kernel loaded at 0x13078 or so, then ddb > messages, then Cpppppppppppppppp. No other messages. > > As for the open firmware console, not sure if it works or not. We are > using a beta firmware for testing which has framebuffer support and > it would definitely be nice to support that, but if not just plain > text to a plain text console is okay (writing to the openfirmware > stdout equivalent) The framebuffer console makes some assumptions: - the framebuffer is linear - it is set up by the firmware with a 1:1 virt-phys mapping so it can be BAT-mapped later - the depth must be 8 or 32 (16 not supported) - it can be located in the openfirmware tree with: chosen = OF_finddevice("/chosen"); OF_getprop(chosen, "stdout", &stdout, sizeof(stdout)); node = OF_instance_to_package(stdout); OF_getprop(node, "device_type", type, sizeof(type)); if (strcmp(type, "display") != 0) return (0); ... and the node must have height, width, linebytes and address properties. later, Peter.