From owner-freebsd-alpha Sat Mar 18 13:57:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id AD97437B536; Sat, 18 Mar 2000 13:57:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA23476; Sat, 18 Mar 2000 13:57:19 -0800 Date: Sat, 18 Mar 2000 13:57:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: Initial Alpha 8200 support is integrated- Alpha Hardware.txt update? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The initial pass at the Alpha 8200 (aka TurboLaser) has been checked in. I've run this on machines up to 2GB in size (some with 2 processors, but we're not using those yet). There's still a lot to do, and the following should be noted: 1. Console For serial console usage (pretty much mostly what the 8200 has, although I hear that newer versions *do* support some kind of frame buffer), either change /etc/ttys to have: console "/usr/libexec/getty std.9600" unknown on secure as the console entry, or add zs0 "/usr/libexec/getty std.9600" unknown on secure and make the zs node: mknod /dev/zs0 c 135 0 [ I would like, in fact, to see console *always* be enabled - that way the real console device will always have a getty, but that's a separate issue ] 2. PCI cards I've tried a variety of cards, but I haven't sat down and checked out type 1 cycles, so I suspect that any card with a bridge will just not work right now. I also, haha, tried the FDDI driver and that's not working, but that's more due to it likely not working on alpha period. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message