From: Krzysztof Halasa <khc@pm.waw.pl>
To: Dave Airlie <airlied@linux.ie>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Jean Delvare <jdelvare@suse.de>, Jeff Mahoney <jeffm@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fb/intelfb: Do not depend on EMBEDDED
Date: Thu, 17 Dec 2009 00:19:49 +0100 [thread overview]
Message-ID: <m3vdg6zeui.fsf@intrepid.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.0912162255501.25055@skynet.skynet.ie> (Dave Airlie's message of "Wed, 16 Dec 2009 22:57:29 +0000 (GMT)")
Dave Airlie <airlied@linux.ie> writes:
> Currently with the command line video=, this isn't optimal but still
> nobody has come up with a way to make fbset useful since it can't deal
> with multiple heads.
Ahh, now I can see it.
> also the old intelfb didn't deal with analog rgb tv at all.
Well... actually, it did: intelfb works very well if a correct mode is
set (a trivial patch adjusting the clock lower limit to 13.5 MHz may be
needed, or one can use the double clock and resolution, or maybe 1:1
pixel aspect ratio etc). It's not about the CH7xxx encoder, the TV is
connected directly to VGA output.
E.g.
# PAL 720x576, 50 Hz, Interlaced (13.5 MHz dotclock)
#
# Horizontal Vertical
# Resolution 720 576
# Scan Frequency 15.625 kHz 50 Hz (I)
# Sync Width 4.296 us 1.280 ms
# Front Porch 1.000 us 0.256 ms
# Back Porch 5.370 us 1.600 ms
# Active Time 53.333 us 36.864 ms
# Blank Time 10.667 us 3.136 ms
# Polarity Negative Negative
#
# H: 720 + 14 + 58 + 72 = 864
# V: 576 + 4 + 20 + 25 = 625
mode "PAL"
# D: 13.5 MHz, H: 15.625 kHz, V: 50 Hz
geometry 720 576 720 576 32
timings 74074 72 14 25 4 58 20
laced true
hsync low
vsync low
endmode
"fbset PAL" is all one needs to use it.
(I know i915 doesn't have interlaced mode support for analog VGA out,
not a problem).
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-12-16 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 21:55 [PATCH] fb/intelfb: Do not depend on EMBEDDED Jesse Barnes
2009-12-13 11:50 ` Jean Delvare
2009-12-13 21:53 ` Dave Airlie
2009-12-16 13:37 ` Jean Delvare
2009-12-16 18:00 ` Jesse Barnes
2009-12-16 22:38 ` Krzysztof Halasa
2009-12-16 22:57 ` Dave Airlie
2009-12-16 23:19 ` Krzysztof Halasa [this message]
2009-12-14 18:36 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2009-12-12 13:19 Jean Delvare
2009-12-12 20:10 ` Dave Airlie
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=m3vdg6zeui.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=airlied@linux.ie \
--cc=jbarnes@virtuousgeek.org \
--cc=jdelvare@suse.de \
--cc=jeffm@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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