Re: Panic at boot on 4/330 with cgfour and cgsix

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

(sorry for late response)

tokenalt@ wrote:

> > [had a chance to look at this again]
> >
> > > > Sounds like it's easiest to just use (-0x00100000).
> > >
> > > Yes that is what I think now as well. I checked cvs history and the
> > > sun3 cgfour driver has been using a negative offset since 1998 and has
> > > worked for many people including me. So if it's good enough for sun3 I
> > > don't see why it can't be good enough for sparc.
> >
> > Agreed.  Let's just use:
> >
> > #define PFOUR_COLOR_OFF_CMAP    0x00100000

PFOUR_COLOR_OFF_CMAP is also used in cgeight.c so maybe
we should also consider how cgeightmmap() should handle it..

> Also in the bwtwo driver I found it used a for loop to limit memset()
> to 4 bytes at a time to prevent write errors, copying that fixed my
> panic on memset(). However it still hangs at wsdisplay_cnattach(). I
> don't know if it's not being set up properly or if it's fighting the
> bwtwo driver over who gets to be console. Attaching a work in progress
> patch. It doesn't handle the overlay and enable planes yet. In the
> sun3 driver it handles them separately instead of lumping them all
> together like the sparc driver does. Not sure which is better.

I've purchased Sun 4/100 board with FPU so I'll try it with
my 4/110 chassis and spare CG4 P4 board (hopefully in this April).

---
Izumi Tsutsui