From owner-freebsd-hackers Mon Jun 1 00:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16238 for freebsd-hackers-outgoing; Mon, 1 Jun 1998 00:24:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ascetic.portal.ca (ascetic.portal.ca [206.87.139.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16233 for ; Mon, 1 Jun 1998 00:24:33 -0700 (PDT) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by ascetic.portal.ca (8.8.8/8.8.5) with SMTP id AAA06375; Mon, 1 Jun 1998 00:24:23 -0700 (PDT) X-Authentication-Warning: ascetic.portal.ca: cjs owned process doing -bs Date: Mon, 1 Jun 1998 00:24:23 -0700 (PDT) From: Curt Sampson To: Doug Rabson cc: Mike Smith , 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 Mon, 1 Jun 1998, Doug Rabson wrote: > Don't worry, I am fully aware of the PALcode problem. I think it will be > a far easier problem to deal with the bootstrap installing PALcode than > for it to have a complete set of device drivers. There is plenty of > PALcode source in milo. There's plenty of device driver source code in Linux and NetBSD, too. :-) My point is, every time a new type of Alpha comes along, you have to write new PALcode and compile it in to the boot loader. This is not really all that different than having to write and compile in a new device driver every time a new device comes along. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite mist, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message