From: Marcus Sundberg <mackan@stacken.kth.se>
  To  : ggi-develop@eskimo.com
  Date: Sat, 03 Jul 1999 16:02:21 +0000

Re: tile target?

Ketil Froyn wrote:
> 
> On Sat, 3 Jul 1999, Marcus Sundberg wrote:
> 
> > ggix :0 -modes "[GT_16BIT]" -targets
> > "tile:0,0,1152,864,(fbdev):1152,0,800,600,(glide)"
> > will do what you want.
> 
> This gave me:
> LibGGI: Checking GGI_INPUT_TILE_3 : (nil)
> LibGGI: Checking GGI_INPUT_TILE : (nil)
> LibGGI: Checking GGI_INPUT : (nil)
> LibGGI: ggiParseMode(0xbffff3fc, 0x81c6364) called
> LibGGI: ggiCheckMode(0x81c8708, 0x81c6364) called
> LibGGI: display-fbdev: checkmode 1152x864#0x0F1[0x2001010]
> LibGGI: display-fbdev: result 0 1152x864#1152x864F1[0x2001010]
> LibGGI: res2glideres: breaking on highfreq

The last line means you have told the glide target that your
monitor can not cope with the frequency required for this mode.

> display-tile: ggiCheckMode() on visual #1 error -- please explicitly
> specify cor
> rect mode instead.
> 
> Fatal server error:
> XGGI doesn't support 0 bpp screens.
> 
> > No emulated target will ever support DirectBuffer and acceleration
> > at the same time, simply because it is not possible do do this.
> 
> Damn :) Can you make XGGI work without DirectBuffering, then? :)

In theory - sure, but even though I'd like that I won't have the time
to do it in the forseeable future.

> > > Also, there's still the problem of dragging a window from one screen to
> > > the other. When I try, the window pops up on the other side of the
> > > original screen instead of on the other screen. Is this only possible with
> > > the tile-target also?
> > The tile target is only one screen so you can drag windows wherever
> > you like on that.
> 
> But without tile the windows have to stay on one screen?

Currently yes. XFree86 4.0 may provide better backend code which
removes this and other limits from XGGI.

> > > Lastly, I was wondering if I can set interlaced modes on the Voodoo2.
> > No. Why would you want to do that?
> 
> Cos I have a lousy screen.

Well that's a reason ofcourse. ;)
But the Glide API doesn't know about interlace. How about using a
lower resolution?

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan/
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: mackan@stacken.kth.se