> Can anyone tell me if the Xsun24 binary shipped with NetBSD (1.4M)
> actually works?  It just SIGSEGVs on me:

>    196 Xsun24   "/dev/bwtwo1"                      Err#2 ENOENT
>    196 Xsun24   "/dev/bwtwo2"                      Err#2 ENOENT
>    196 Xsun24   "/dev/cgeight0"                    Err#2 ENOENT
>    196 Xsun24   "/dev/fb"                          = 0
>    196 Xsun24   open("/dev/fb", 0x2, 0)            = 6
> ,_IOW('F',0x6,0x58)   196 Xsun24   ioctl(0x6, 0x250100)               =
> 0
>    196 Xsun24   __sysctl(0xeffff688, 0x2, 0x102ea500, 0xeffff684, 0, 0)
> = 0
>    196 Xsun24   mmap(0, 0, 0x3, 0x1, 0x6, 0, 0, 0) = 270401536
> SIGSEGV SIG_DFL
>    196 Xsun24   

I don't know *what* happened to that trace; it looks very weirdly
mangled.  But it's mostly clear enough how it should go back together.

> I'm attempting to use it to drive my Parallax 24-bit dumb framebuffer
> through the 'pllx' driver I've written (see a previous message), but
> note that the SIGSEGV event is not associated with my driver code, as
> far as I can tell.  Debug printf's show my driver's open, ioctl
> (FBIOGATTR), and close routines being called, then the seg fault
> occurs.

Um, then something is wrong with either your debugging printfs or the
way you've hooked into the VM machinery; note that the mmap() call is
done on fd 6, the fd returned for /dev/fb - check into how your driver
handles mmap.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B