From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9f3897940609141547n40b159cbkf2aa6ec888d837e4@mail.gmail.com> Date: Fri, 15 Sep 2006 00:47:57 +0200 From: "=?UTF-8?Q?Pawe=C5=82_Lasek?=" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: [9fans] alpha port? In-Reply-To: <8a95754de042540e0d779608dd0f89e1@plan9.bell-labs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <509071940609140403j42c89fbbiad7ff653f5982d7c@mail.gmail.com> <8a95754de042540e0d779608dd0f89e1@plan9.bell-labs.com> Topicbox-Message-UUID: b3ec42de-ead1-11e9-9d60-3106f5b1d025 On 9/14/06, geoff@plan9.bell-labs.com wrote: > As /sys/doc/port.ms says, > --- > The compiler assumes that the target CPU supports the optional byte and > word memory operations (the ``BWX'' extension). > If you have an old system, you can generate code without using the extension > by passing the loader the > .CW -x > option. > --- > > That may not be enough though; dhog thought that some of the > device drivers might depend upon byte or word accesses. > Plus you'd need to check all the assembly language code for > BWX operations. I recall that there was some kind of EV56 emulator for EV45, which added BWX and some other operations to running cpu (like FPU emulator). The problem is that it might be hidden behind some proprietary license. If all goes wrong I'll just need to grep them all... > And of course details of I/O and memory management vary across > Alpha models. Isn't that the reason PAL exists? ;-) Well, I'll look into netbsd/alpha code for AS255 and check relevant parts. IIRC many things were accomplished in netbsd by using OSF PALcode. But first I'll need to get a place to put my normal computer to do any work, so don't expect anything fast :-) -- Paul Lasek