> > > The first problem was that cgsix doesn't support changing resolution;
> > > it produced an error, because every ggi-demo seemed to set some
> > > resolution. The cgsix is set to 1152x900x8.
> > That's a problem. So do not run demos ;-) If your display supports
> > only limited functionality, you'll get only limited functionality
> > from libraries.
>
> Yes, but maybe the library shouldn't exit completely. The cgsix driver
> gives error no matter what resolution you try to set with the ioctl,
> so even if you set 1152x900x8, it will fail.
I'll hack sbusfb so that it returns 0 for display change if it matches the
probed resolution. But anyway, IMHO libraries should not fail in such case.
>
> > > priv->fb_ptr = mmap(NULL, priv->mmap_size, PROT_READ | priv->PROT_WRITE,
> > > MAP_SHARED, LIBGGI_FD(vis), 0);
> > > This will not work on the cgsix, because it needs an offset of
> > > 0x70016000 when mmapping the display. Similar, but other values on
> > > other cards. I think cgthree needs offset 0x04000000, although I
> > You are not serious, are you? mmapping on /dev/fb is DEFINED that at
> > offset zero there is framebuffer with length found in fix.smem_len.
> > Immediately after that there is mmio region with length fix.mmio.len.
> > (maybe you should add PAGE_ALIGN() around fix.*_len values; but driver
> > should report PAGE_ALIGNed values to userspace).
> > I see no notice about smem_start, about 0x70016000 and so on in that
> > sentece... You should fix cgsix, I think (are other tools (fbtv) able
> > to find your videomemory?).
No, it does not work that way on any SBUS/UPA /dev/fb nor on SPARC mach64
/dev/fb. The reason is binary compatibility. We had /dev/fb devices far
before fbcon went into the standard kernel, and the mappings are defined
to match SunOS/Solaris mappings.
In fact, on most adapters the smem_start/smem_len/mmio_len is clearly
unsufficient, most of the cards export several different framebuffer views
with different semantics and several different IO regions as well.
And you really want to map more different fb views, because e.g. on Creator
you have different view for different depths and some are dumb (in the sense
they do not depend on IO register setting) while some are smart (so that you
can e.g. set rop in IO and then paint GXcopy into the smart view and the
card does things for you).
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | [EMAIL PROTECTED] | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.26 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
