Quoting Carlos Ojea Castro:
> Hello!
> 
> > > I boot with fb in 640x480. Later with 'fbset' I change to another
> > > resolution (720x576), but, if I run my user program now, screen
> > > resolution changes automatically back to 640x480.
> >
> > DirectFB uses the first valid mode found in /etc/fb.modes or the current
> > one if no other is found. You can use the "mode = <width>x<height>" option
> > to choose another default resolution.
> 
> I discovered this behaviour when I start directFB
> (I boot in 640x480 and then change with fbset to 720x576, the actual
> resolution):
> 1.- A call to DirectFBCreate (&dfb) makes screen resolution switch
> back to 640x480
> 2.- A call to CreateSurface (primary one) makes screen resolution
> switch to actual resolution (720x576).
> 
> These things happen if I don't use panning. If I do, the call to
> CreateSurface don't switch to the actual resolution (720x576), maybe
> becouse I did the panning function in my geode nsc driver by myself...

The switch should anyways, unless there's insufficient memory for double 
buffering.

> So, the function in the geode nsc fb driver that changes resolution is
> gx1_geode_set_par(). I made a ioctl to use a flag to block that
> resolution change when I don't want to.

Check if the driver blocks virtual resolutions.

Or try "fbset -vyres 1152" after switching to 720x576 and check the output
of fbset afterwards to see if the change wasn't discarded.

-- 
Best regards,
  Denis Oliver Kropp
 
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/                 |
"------------------------------------------"

_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to