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 (resolved for 640x480@64K)
Date: Sun, 11 Jun 2006 11:03:11 -0400 [thread overview]
Message-ID: <a728f9f90606110803v10ca364xf3e32e4a40f4bbfa@mail.gmail.com> (raw)
In-Reply-To: <448C067B.3040404@iit.demokritos.gr>
On 6/11/06, Vassilis Virvilis <vasvir@iit.demokritos.gr> wrote:
> Hi Alex,
>
> I would like to thank you and Antonino for all the help so far. I have finally
> manage to make my twister to sync with both of my screens (one TFT, one CRT).
>
> I am attaching the patch. The patch itself disables all modes other than
> 640x480@64K-60Hz. Note that the patch is clearly inapropriate but it
> may sparkle some discussion about how this thing works.
>
> One more question:
>
> Alex Deucher 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.
> >>
>
> When you say panel what do you mean?
> a) The rest of the framebuffer and scan logic resided in CRTC?
> b) The screen attached to CRTC?
>
> I believe a) but I would like to know for sure.
I'm not sure I understand your question. The panel connects to the
chip via a built in flat panel interface, however it has to be driven
with timings and a clock just like a CRT. The CRTC can drive either
the FP interface or the DAC or both. Based on you patch it seems you
only need to tweak the clock. Perhaps if we had a few more testers we
could figure out a pattern for common panels and put in some sort of
generic fix.
Alex
>
> Thanks again...
>
> .bill
>
>
>
next prev parent reply other threads:[~2006-06-12 17:39 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
2006-06-11 12:03 ` Twister savagefb doesn't sync (resolved for 640x480@64K) Vassilis Virvilis
2006-06-11 15:03 ` Alex Deucher [this message]
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=a728f9f90606110803v10ca364xf3e32e4a40f4bbfa@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).