From owner-freebsd-hackers Wed Jun 3 12:37:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13105 for freebsd-hackers-outgoing; Wed, 3 Jun 1998 12:37:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12854 for ; Wed, 3 Jun 1998 12:37:01 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id UAA01016; Wed, 3 Jun 1998 20:35:55 +0100 (BST) Date: Wed, 3 Jun 1998 20:35:55 +0100 (BST) From: Doug Rabson To: Curt Sampson cc: Terry Lambert , mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: AlphaBIOS documentation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jun 1998, Curt Sampson wrote: > On Tue, 2 Jun 1998, Doug Rabson wrote: > > > Which parts of the PALcode in the Linux source are incompatible? > > I don't know the exact details, but I have been assured by someone > who should know that DU never ran on the development kit PALcode, > and one of our developers has tested NetBSD on the DK PALcode and > confirmed that it does not work. > > > I don't think I will have any real problem using this code for FreeBSD. > > Well, good luck! I'll be interested to what you need to do, if > anything, to clean it up. Well at least one problem I noticed during a code review of the eb164 palcode in milo is that the interrupt support is pretty thin. It always supplies a vector number of 800 to the OS, whatever the real interrupt source and it doesn't support the undocumented cserve functions 0x34 and 0x35 which NetBSD and DU use to enable and disable interrupts. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message