From owner-freebsd-alpha Sat Dec 4 23: 9: 8 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from Twig.Rodents.Montreal.QC.CA (Twig.Rodents.Montreal.QC.CA [132.206.78.3]) by hub.freebsd.org (Postfix) with ESMTP id 7644915177 for ; Sat, 4 Dec 1999 23:09:03 -0800 (PST) (envelope-from mouse@Twig.Rodents.Montreal.QC.CA) Received: (from mouse@localhost) by Twig.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id CAA18406; Sun, 5 Dec 1999 02:08:43 -0500 (EST) Date: Sun, 5 Dec 1999 02:08:43 -0500 (EST) From: der Mouse Message-Id: <199912050708.CAA18406@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit To: port-alpha@netbsd.org, alpha@FreeBSD.ORG Subject: Re: Q: Compaq, *BSD and 'Linux-only' AlphaBIOS (fwd) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> [...my misunderstanding of what PALcode is...] > [...thorpej explaining...] > To be honest, PALcode is one of my favorite features of the Alpha > architecture. [...] Plus, the PALcode is written by the processor > designers. Those people know how the hardware works, and all of its > quirks and gotchas (or, at least, they'd better :-) ... I trust their > TLB reloading code more than I would mine, I think :-) Yeah, I can see that. And the more I learn about it, the more I like it - as a feature of the architecture. The problem is with the implementation: when you can't *get* "their TLB reloading code", you don't have enough info to write your own. :-( Growl. der Mouse mouse@rodents.montreal.qc.ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message