Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!mcsun!sun4nl!utrcu1!klamer From: klamer@mi.el.utwente.nl (Klamer Schutte) Subject: Re: 680x0 version of 386BSD?? [Was: Re: Mac version of 386BSD??] Message-ID: <klamer.714298926@mi.el.utwente.nl> Sender: news@utwente.nl (USENET News System) Organization: University of Twente, BSC-El References: <1992Aug18.105723.13123@olymp.informatik.uni-bonn.de> <1992Aug18.174205.23671@news.iastate.edu> <1992Aug19.093937.14857@olymp.informatik.uni-bonn.de> <1992Aug19.155359.629@athena.mit.edu> Date: Thu, 20 Aug 1992 08:22:06 GMT Lines: 24 In <1992Aug19.155359.629@athena.mit.edu> bri@pegasus.mit.edu (Brian D. Carlstrom) writes: >In article <1992Aug19.093937.14857@olymp.informatik.uni-bonn.de> volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt ) writes: >>In article <1992Aug18.174205.23671@news.iastate.edu> niko@iastate.edu (Nikolaus E Schuessler) writes: >>>Since most of the source is written in C, I believe that most of the time >>>is going to be spent writing drivers for disks, displays, etc... >i just had an interesting thought. wouldn't ib be a bit easier to port >to the 68k apollos, since they use an ISA bus, which is supported by >386bsd? i realize that the video cards they use are not standard, but >you could at least get it up and going by using a pc card and monitor. One word of caution: beware of the byte order in words! On a 80x86 (PC style) it is little endian, and on a 68K it is big endian. Which means it is just the other way around... And which means that the same code accessing word-size registers on I/O cards almost certainly fails, if it is not aware of this problem. (and not efficient if it does...) Klamer -- Klamer Schutte Tel: +31-53-892778 Fax: +31-53-340045 Faculty of electrical engineering -- University of Twente, The Netherlands preferred: klamer@mi.el.utwente.nl SMTP: klamer@utelmi01.el.utwente.nl