From owner-freebsd-sparc64@FreeBSD.ORG Sat May 14 13:54:29 2005 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAB1616A4CE for ; Sat, 14 May 2005 13:54:29 +0000 (GMT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17B3143D5E for ; Sat, 14 May 2005 13:54:29 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) j4EDsR4w087605 for ; Sat, 14 May 2005 15:54:27 +0200 (CEST) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.11/8.12.10/Submit) id j4EDsMmF087604 for freebsd-sparc64@freebsd.org; Sat, 14 May 2005 15:54:22 +0200 (CEST) (envelope-from marius) Date: Sat, 14 May 2005 15:54:22 +0200 From: Marius Strobl To: freebsd-sparc64@freebsd.org Message-ID: <20050514155422.A33783@newtrinity.zeist.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-4; AVE: 6.30.0.12; VDF: 6.30.0.177; host: newtrinity.zeist.de) Subject: Blade 100 tester wanted X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 May 2005 13:54:29 -0000 I'm looking for someone to give native support for ATI Mach64 graphics chips (onboard in U5/U10 and Blade 100, Sun PGX cards, etc.) a try on a Blade 100. The patch is at: http://alchemy.franken.de/~marius/kreator_machfb.diff and requires 6.0-current. For testing in addition to applying the patch and compiling a kernel with machfb(4), syscons(4), ukbd(4) and usb(4) enabled (have a look at how the patch changes the sparc64 GENERIC config file or just use that one) ttyX have to be enabled in /etc/ttys. To actually simplify testing I built custom install images which are at: http://people.freebsd.org/~marius//6.0-20050513-SNAP-sparc64-bootonly.iso.bz2 and http://people.freebsd.org/~marius//6.0-20050513-SNAP-sparc64-disc1.iso.bz2 The checksums of these images when decompressed are: MD5 (6.0-20050513-SNAP-sparc64-bootonly.iso) = 7694411beea290553f49520a5f174195 MD5 (6.0-20050513-SNAP-sparc64-disc1.iso) = a1a08b4b9d44a636d0d60fb17263934a I'm interested in: - Whether the graphical console works when 'input-device' is set to 'keyboard' and 'output-device' to screen and an USB keyboard is actually plugged in. - Whether the monitor also comes up with the VTY when both 'input-device' and 'output-device' are set to 'ttya' (i.e. using a serial console as the primary console). When booting the above install images the monitor should just show an all white screen with a black cursor in the top left corner in this configuration. - The machfb(4) bits of the dmesg. It would be great if someone could give this a try in the next couple of days as the plan actually is to enable creator(4), machfb(4) and syscons(4) in the sparc64 GENERIC kernel for FreeBSD 6.0 and the code and feature freeze for 6.0 starts really soon now. In case the graphical console works X should also work. For Blade 100 with USB keyboards Xorg 6.8.2 actually should work out of the box. When using machfb(4) on e.g. a U5/U10 with a RS232 keyboard the keyboard probably won't work properly under Xorg 6.8.2; it however should work when using the old 'keyboard' driver instead of the new 'kbd' one (search the freebsd-sparc64 archives for how to compile the xorg-server 6.8.2 port with the 'keyboard' driver instead). Marius