Philip Armstrong wrote:
On Fri, Oct 28, 2005 at 04:08:07PM +0000, Duncan Webb wrote:
I think you just need to tweak the timings. Some values just don't
seem to work with the g400. I've got a 1024x768 PAL mode around
somewhere which worked for me, but that probably won't help you very
much...
Any help would be appreciated, I've had a bit of a chat with Petr
Vandrovec <vandrove at vc dot cvut dot cz>. Just exactly which bits need
tweaking?
Here's the framebuffer mode which worked for me which I had lying
around:
mode "1024x768-50"
# D: 49.181 MHz, H: 43.600 kHz, V: 50.000 Hz
geometry 1024 768 1024 8176 8
timings 20333 48 8 80 20 48 4
accel true
rgba 8/0,8/0,8/0,0/0
endmode
From what I recall (these days, I just use freevo with dfbmga output
from mplayer), the output was very sensitive to the timings
values. For starters, they had to be a multiple of 4 IIRC, otherwise
things would go haywire in the way you're describing. There were other
bits of weirdness as well :(
I think I got something that worked by using an X mode & tweaking it
with xvidmode until I got something that worked (ie, filled the TV
frame with a solid image) then used an X -> fb mode style converter on
the web somewhere to get the frambuffer version.
The patch from Ville Syrjälä fixing the priority has fixed the problems
with mplayer and dfbmga. Of course this means that using the above mode
on /dev/fb0 to fix the dfbmga output is no longer required. (I think
that is what you have intended)
What I was trying to do here was to see if was possible to configure
/dev/fb1 to send it's output to a second monitor. To see where the
problem was and thanks to Ville he has found the bug in the driver. So I
suppose that I don't need to pursue this problem any more (more than
likely another priority setting in the driver).
Thanks for you help
Duncan
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
