From owner-freebsd-alpha Fri Oct 9 16:26:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18241 for freebsd-alpha-outgoing; Fri, 9 Oct 1998 16:26:04 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from gateway.sequent.com (gateway.sequent.com [138.95.18.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18196 for ; Fri, 9 Oct 1998 16:25:56 -0700 (PDT) (envelope-from seifert@sequent.com) Received: from eng4.sequent.com (eng4.sequent.com [138.95.7.64]) by gateway.sequent.com (8.8.5/8.8.5) with ESMTP id QAA25661 for ; Fri, 9 Oct 1998 16:25:46 -0700 (PDT) Received: from localhost (seifert@localhost) by eng4.sequent.com (8.8.5/8.8.5) with SMTP id QAA07824 for ; Fri, 9 Oct 1998 16:25:45 -0700 (PDT) Message-Id: <199810092325.QAA07824@eng4.sequent.com> X-Authentication-Warning: eng4.sequent.com: seifert@localhost didn't use HELO protocol To: alpha@FreeBSD.ORG Subject: PALcode Date: Fri, 09 Oct 98 16:25:44 PDT From: David Seifert Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> The fact that the ARC or AlphaBIos console doesn't include PALcode that's >> UNIX-friendly is the issue. The SRM console image includes VMS and OSF/1 >> PALcode; NetBSd uses the OSF/1 PALcode. The ARC console includes Windows NT >> PALcode; Linux hacks around this by including its own PALcode in MILO. > > Isn't this more of a case of us running a UNIX that isn't ARC PALcode > friendly? No. The PALcode customises the machine for a particular OS. That is the whole point of the PALcode. There is PALcode for Unix, PALcode for VMS, and PALcode for NT. Similar deal with the console software. SRM for VMS and Unix, ARC or AlphaBIOS for NT. ARC cannot read a BSD disklabel. -Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message