linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Deucher" <alexdeucher@gmail.com>
To: vasvir@iit.demokritos.gr
Cc: linux-fbdev-devel@lists.sourceforge.net,
	"Antonino A. Daplas" <adaplas@gmail.com>
Subject: Re: Twister savagefb doesn't sync
Date: Tue, 6 Jun 2006 10:43:53 -0400	[thread overview]
Message-ID: <a728f9f90606060743t7fd6dfdfia3e2a050ff954e06@mail.gmail.com> (raw)
In-Reply-To: <44855197.7040801@iit.demokritos.gr>

On 6/6/06, Vassilis Virvilis <vasvir@iit.demokritos.gr> wrote:
> Alex Deucher wrote:
> > On 6/5/06, Vassilis Virvilis <vasvir@iit.demokritos.gr> wrote:
> >
> > The reason the savage xorg drver uses the bios is because almost every
> > panel they connect to the chip seems to require fairly custom timings.
> > the twisters and prosavages are even worse than the discrete chips.
> > Also, only the bios seems to know the magic incantation necessary for
> > dualhead.  I tried for a while to add non-bios mode setting to crtc2
> > without much luck.
>
> I don't care for dualhead right now. I can imagine it is 4 times weirder
> than my current setup. What is crtc*?

twisters/prosavages can't do dualhead anyway. crtc stands for crt
controller.  it's just another name for a display controller (ie,
thing that scans out the image).

>
> >
> > For a short term fix, just program the registers with the new values
> > from the bios.  You may be able to just get away with adjusting the
> > crtc1 dclk (SR12, SR13, SR29).
>
> I will try that. Thanks for the suggestion.
>
> A real fix may require special
> > calculations or tables for different chip/panel combos.
> >
>
> I will try for both of my monitors and I will report here any
> success or failure unless of course I am told that this info is
> not desirable.

Sounds good.

>
> Do you know if changing the number of colors 256/64K/16M requires
> clock adjustments (SR12, SR13, SR29)?

It shouldn't.

>
> Thanks for answering.

No problem.

Alex

>
>       .bill
>

  reply	other threads:[~2006-06-08  1:45 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
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 [this message]
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=a728f9f90606060743t7fd6dfdfia3e2a050ff954e06@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=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).