Re: Twister savagefb doesn't sync
From: "Antonino A. Daplas" <adaplas@gmail.com>
Date: 2006-05-29 00:14:08
Vassilis Virvilis wrote:
Antonino A. Daplas wrote:quoted
lspci -v -d 5333:8d04OK I have done a lot of tests. First my device is 5333:8d01 and the non-prefetchable memory is at ec000000 so we have #define PCI_ID 0x8d01 /* put the PCI id of the device here */ #define PCI_PBASE 0xec000000 /* put the start address of the PCI resource here */ Ok. I tried both X (with use bios), and SDL testsprite in 640x480, 800x600, 1024x768 at 8, 16, 24 bpp. testsprite is a SDL demo that accepts the following options (-width, -height, -bpp). I made both sets of tests in a medion TFT 18 screen and in an EIZO F520 CRT. All X modes are working. SDL works for 1024x768 bpp=* in CRT and TFT SDL work in 800x600 bpp={16, 24} (not 8bpp) only in TFT and __not in CRT__ I am attaching the output of savagedump for all modes, for both monitors (#36), just for future reference. I will try to understand the differences but the registers are too many and without documentation it is a bit hopeless I am afraid. Or is there
Too many differences since the timings for the 2 modes are also different. If you can match the timings, as shown by fbset and xvidtune, this should minimize the variation.
documentation somewhere publicly available?
There are no docs.
Is there any way to replay the working set of registers to get the correct mode settings?
savagefb does save the initial registers and reuses part of them when setting the mode, so if you can boot with vga= parameter that matches the initial mode of savagefb, it might help. Try this: video=savagefb:1024x768-16@60 vga=0x317 Tony ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642