🚀 go-pugleaf

In article <1990Aug28.012633.28332@odin.corp.sgi.com>,
jsw@xhead.esd.sgi.com (Jeff Weinstein) writes:
|> In article <Fj2wsrx1@cs.psu.edu>, ehrlich@cs.psu.edu (Dan &) writes:
|> > In article <1990Aug26.231909.6505@athena.mit.edu>
|> dyer@arktouros.mit.edu (Steve Dyer) writes:
|> ...
|> 	I believe that the current AOS kernel only enables this fake
|> 	buffer if certain options are enabled in your config file.
|> 	One option was X10, and another was specifically for xtrek, but
|> 	obtusely named, so at to not upset management, etc.  Perhaps
|> 	Bill Webb would like to comment?  The code is in machdep.c, and
|> 	is surrounded by #if defined(X10) ||
defined(XsomethingIDontRemember).
|> 		--Jeff


Aha, another gross hack come back to haunt me too!

Ok, here are the relevent lines from /sys/ca/machdep.c:

/*
 * Support for AED simulated bitmap hack
 * we include this support if AED is configured and
 * either X10 support is specified or XWM is specified
 * (the latter is only for a single program that uses
 * the bitmap as shared memory and should eventually
 * disappear).
 */
#include "xtenemul.h"
#include "aed.h"
#if (NAED > 0 && NXTENEMUL > 0) || defined(XWM)
#include "../machinecons/apaaed.h"
#endif (NAED > 0 && NXTENEMUL > 0) || defined(XWM)

If it is obvious from the above the kernel option is "XWM". In case
you are wondering XTENEMUL is used instead of X10 because config 
didn't like numbers in option names.

PS: for those wondering how to configure a BSD 4.3 kernel for the
IBM 6152 so that it can run xtrek - XWM is it!

----------------------------------------------------------------
The above views are my own, not necessarily those of my employer.
Bill Webb (IBM AWD Palo Alto), (415) 855-4457.
UUCP: ...!uunet!ibmsupt!webb