linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: Alex_SYS <schmid-grafenau@t-online.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Videomode 800x480
Date: Tue, 15 Jul 2008 20:29:25 +0200	[thread overview]
Message-ID: <487CEC85.2070801@denx.de> (raw)
In-Reply-To: <18470632.post@talk.nabble.com>

Hello,

Alex_SYS wrote:
> Hello, I have the problem that I need a Framebuffer resolution 800x480!
> Since now I have filled the fb_info, var and fix Structs!
> But there was the problem with the resolution!
> I have found out that the problem is the videomode!
> In modedb there is unfortunately no 800x480 Videomode, and I have tried my
> own 800x480 Struct, but the Kernel does`t want my settings (I tried to
> change an 800x600 to 800x480 only by changing yres to 480).
> Can someone tell me please a working fb_videomode struct for 800x480?

Values for 800x480 fb_videomode depend on the TFT-panel that
you are using. Without the spec of this panel it is hard to guess.
It is also hard to guess the value for .pixclock as we do not know
if internal or external clock is used as the source for display
reference clock. What is the value of GDC DCM0 register (at
offset 0x1fd0000 or 0x1fd0100 from the GDC base)?

Try something like this:
.xres = 800
.yres = 480
.pixclock = 40000
.left_margin = 86
.right_margin = 42
.upper_margin = 33
.lower_margin = 10
.hsync_len = 128
.vsync_len = 2

> The syncs are setted up by U-Boot .

then you probably should retrieve proper values for fb_videomode
from display controller registers set up by U-Boot. If you do not
have the spec for your panel, it is the way to go. Consult the
GDC manual (Display control registers section) and
Documentation/fb/framebuffer.txt in the linux source tree.

Best regards,
Anatolij

  reply	other threads:[~2008-07-15 18:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 17:24 Videomode 800x480 Alex_SYS
2008-07-15 18:29 ` Anatolij Gustschin [this message]
2008-07-16  8:50   ` Alex_SYS
2008-07-17  7:15     ` Alex_SYS
2008-07-17 11:43       ` Anatolij Gustschin
2008-07-17 12:11         ` Alex_SYS
2008-07-17 15:26     ` Detlev Zundel
2008-07-18  8:52       ` Alex_SYS

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=487CEC85.2070801@denx.de \
    --to=agust@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=schmid-grafenau@t-online.de \
    /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).