Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!doc.ic.ac.uk!pipex!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.bugs Subject: Re: kernel writes to user space Message-ID: <C9ICHs.py@veda.is> Date: 1 Jul 93 22:44:02 GMT References: <20bfrm$le7@pdq.coe.montana.edu> <20qqgu$dj@werple.apana.org.au> <1993Jun30.022629.24466@uvm.edu> <C9GMzD.B6@veda.is> <1993Jul1.190202.17637@uvm.edu> Organization: Veda Systems, Iceland Lines: 33 wollman@UVM.EDU (Garrett Wollman) writes: >In article <C9GMzD.B6@veda.is> adam@veda.is (Adam David) writes: >>i486 is a superset of i386, so it does not make much sense to define i486 >>without also defining i386. Therefore defined(i486) should be enough of a >>test. >No! (At least, not by my interpretation of configuration.) If you >configure a system for >cpu i386 >cpu i486 >...that means it /must/ work on both systems. I agree with this, and it would also be useful. However, I had something else in mind. Consider this: machine i386 #this is for 386bsd, not ARMbsd or bsd68k cpu i486 #additional information, the cpu is a 486 In the Makefile #defines all this does is define 2 symbols. For 386bsd, i386 will always be defined, and if the kernel is configured for >386 cpu then i486 (or whatever) will be defined as well. Machine should define the architecture, and cpu define the actual cpu configuration(s) supported. Maybe it is not implemented in this way, but it makes a whole lot more sense. The respective tokens 'machine' and 'cpu' are only visible to the config program, so if they mean anything special it has to be done there. -- adam@veda.is