Hi again,

I really only put back in the "madhatter" patch that's been used and
abused by me for so long.  It's attached here:

===================================================================
RCS file: RCS/machdep.c,v
retrieving revision 1.4
diff -c -r1.4 machdep.c
*** machdep.c   1997/09/02 01:50:49     1.4
--- machdep.c   1997/09/02 01:54:49
***************
*** 2145,2150 ****
--- 2145,2153 ----
        case MACH_CLASSQ:
          case MACH_CLASSQ2:
                mac68k_machine.sonic = 1;
+                 /* The next two lines are the infamous "madhatter" patch */
+                 mac68k_vidlog = mac68k_vidphys = 0xf9000000;
+                 mac68k_vidlen = 1 * 1024 * 1024;
        case MACH_CLASSAV:
                VIA2 = 1;
                IOBase = 0x50f00000;



---------------------------------------------------------------------

The difference this seems to make(from putting a couple of debugging
printf's in grf_iv.c) is that "mac68k_vidlog" gets a value other than 
zero.  That means that "grfiv_attach()" also sets a non-zero value for
"fbbase".  This seems to be enough to get X to start working.  

As far as I can tell, the value of "mac68k_vidlog" should be non-zero,
anyway.  The 68030 machines get the value through the "get_mapping()" 
routine, which used to be broken for the 68040 systems.  I was hoping 
it was now fixed, but it looks like it isn't.  Perhaps we should be 
setting "mac68k_vidlog" some other way for the 68040 systems until 
this gets fixed.

Steve Brown,
sbrown@best.com

> On Mon, 1 Sep 1997, Stephen Brown wrote:
> > I've cobbled together a kernel that works in 832x624 at:
> > 
> > 	ftp://ftp9.ba.best.com/pub/sbrown/NetBSD/kernels/madhatter#41.tar.gz
> > 
> > Hopefully the problem with -current can be figured out quickly.  The above
> > kernel is from Saturday's sup(08/30/97).
> Thanks, it works just fine. And it's even synched with my ps! ;)
> My only problem is it doesn't seem as if this kernel has the IPNAT stuff
> built in :(
> Would you mind either putting up a tar of the sources, or posting the
> changes (with instructions on how to apply them ;)?
> Xiamin
>
>