From: "Antonino A. Daplas" <adaplas@gmail.com>
To: vasvir@iit.demokritos.gr
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Twister savagefb doesn't sync
Date: Mon, 29 May 2006 08:13:52 +0800 [thread overview]
Message-ID: <447A3CC0.9060403@gmail.com> (raw)
In-Reply-To: <447994A8.30600@iit.demokritos.gr>
Vassilis Virvilis wrote:
> Antonino A. Daplas wrote:
>
>>
>> lspci -v -d 5333:8d04
>>
> OK 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
next prev parent reply other threads:[~2006-05-29 0:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 7:46 Twister savagefb doesn't sync Vassilis Virvilis
2006-05-23 18:51 ` Vassilis Virvilis
2006-05-23 21:43 ` Antonino A. Daplas
2006-05-24 4:04 ` Knut Petersen
2006-05-24 11:38 ` Vassilis Virvilis
2006-05-24 11:31 ` Vassilis Virvilis
2006-05-27 7:47 ` Vassilis Virvilis
2006-05-27 9:26 ` Antonino A. Daplas
2006-05-27 9:29 ` Antonino A. Daplas
2006-05-28 12:16 ` Vassilis Virvilis
2006-05-29 0:13 ` Antonino A. Daplas [this message]
2006-05-29 13:22 ` Vassilis Virvilis
2006-05-29 21:00 ` Antonino A. Daplas
2006-05-31 14:11 ` Vassilis Virvilis
2006-06-05 16:38 ` Vassilis Virvilis
2006-06-06 5:11 ` Alex Deucher
2006-06-06 9:57 ` Vassilis Virvilis
2006-06-06 14:43 ` Alex Deucher
2006-06-11 12:03 ` Twister savagefb doesn't sync (resolved for 640x480@64K) Vassilis Virvilis
2006-06-11 15:03 ` Alex Deucher
2006-06-12 6:12 ` Vassilis Virvilis
2006-06-12 14:37 ` Alex Deucher
2006-06-12 15:50 ` Vassilis Virvilis
2006-06-12 8:33 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=447A3CC0.9060403@gmail.com \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=vasvir@iit.demokritos.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).