In "Re: cgfour0 giving a BIG display with Xsun", "Gordon W. Ross"
<gwr@mc.com> wrote: 
> > From: Scott Ellis <sellis@rohan.sdsu.edu>
> > Date: Mon, 29 Apr 1996 11:18:02 (-0800)
> 
> > I tried using -dev, but it didn't change anything.  On bootup I get:
> > 
> > obmem0 at mainbus0
> > bwtwo0 at obmem0 addr 0xff000000 (1152x900)
> > cgfour0 at obmem0 addr 0xff200000 (1152x900)
> > 
> > So yes, it does configure just fine (or so it seems).  I'm building a
> > -current kernel right now, so if it doesn't work, I'll try hard-coding
> > the address in, and see what I can make happen.
> 
> I doubt that will help.  It sounds to me like Xsun is using /dev/btwo0
> (or /dev/fb perhaps?) so maybe you could temporarily remove all the FB
> device nodes (bw* cg*) except /dev/cgfour0 and see what happens...

Removing fb and bwtwo0 didn't make any difference.  It looks like Xsun
is using cgfour0 fine, it's just that cgfour0 is mmap'ed wrong somehow.

    Scott

-- 
   //////////////////////////////////////////////////////////////////////
  //  Scott Ellis   //   sellis@gi.com   //   sellis@rohan.sdsu.edu   //
 //////////////////////////////////////////////////////////////////////
// WARNING: This signature warps  time and space in its vicinity    //