From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>,
Tony Lindgren <tony@atomide.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
Richard Woodruff <r-woodruff2@ti.com>
Subject: Re: State of LDP3430 platform
Date: Sat, 12 Feb 2011 16:02:16 +0000 [thread overview]
Message-ID: <20110212160216.GA22694@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101206125526.GC31777@n2100.arm.linux.org.uk>
Another LDP3430 report...
The LDP3430 seems to be getting there, but:
1. LCD screen seems wrong. The X display looks rather large, and
flickery - looks like the LCD timing parameters are wrong. Some
text disappears off the RHS.
fbset reports:
mode "240x320-510"
# D: 48.001 MHz, H: 168.424 kHz, V: 510.375 Hz
geometry 240 320 240 320 16
timings 20833 3 39 2 7 3 1
accel false
rgba 5/11,6/5,5/0,0/0
kernel config:
CONFIG_FB_OMAP=y
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2
with the supplied kernel:
mode "640x480-64"
# D: 21.601 MHz, H: 31.396 kHz, V: 63.813 Hz
geometry 640 480 640 640 16
timings 46295 40 4 8 2 4 2
accel false
rgba 5/11,6/5,5/0,0/0
so the LCD timings in the kernel appear to be wrong for the panel
on the LDP. What is 'CONFIG_FB_OMAP_LCD_VGA'? There's *no* help
for this configuration option so god only knows what it's right
setting should be. Please give it some help text to explain what
it is and what it does.
2. Keyboard - numeric keys produce wrong ascii for their labelled
function. This is from /dev/tty1 with X running:
1 gives nothing 2 gives 4 3 gives 7
4 gives 2 5 gives 5 6 gives 8
7 gives 3 8 gives nothing 9 gives 9
* gives nothing 0 gives E # gives nothing
off-hook (green phone) gives 0
on-hook (red phone) gives <1b><5b><31><39><7e>
Killing X and then running evtest on /dev/input/event1 doesn't
return any events, neither does reading /dev/tty1 for the twl4030
keypad - the numeric keys are completely dead. /proc/interrupts
shows no new interrupt counts when pressing the key for
'twl4030_keypad'. Unbinding/rebinding the twl4030 driver doesn't
sort it out, neither does restarting X.
next prev parent reply other threads:[~2011-02-12 16:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 12:55 State of LDP3430 platform Russell King - ARM Linux
2010-12-06 15:59 ` Tony Lindgren
2010-12-06 17:22 ` Russell King - ARM Linux
2010-12-06 18:02 ` Tony Lindgren
2010-12-06 18:19 ` Tony Lindgren
2010-12-06 18:27 ` Paul Walmsley
2010-12-07 8:37 ` Russell King - ARM Linux
2010-12-08 0:50 ` Paul Walmsley
2010-12-08 3:40 ` Paul Walmsley
2011-01-15 0:03 ` Tony Lindgren
2011-01-15 19:38 ` Paul Walmsley
2011-01-15 23:37 ` Russell King - ARM Linux
2011-01-16 0:04 ` Russell King - ARM Linux
2011-01-16 0:05 ` Woodruff, Richard
2011-01-16 0:30 ` Russell King - ARM Linux
2011-01-16 1:09 ` Paul Walmsley
2011-01-16 4:32 ` Paul Walmsley
2011-01-16 15:08 ` Thomas Weber
2011-01-18 19:36 ` Paul Walmsley
2011-01-18 22:26 ` [PATCH] omap1: Fix sched_clock for the MPU timer (Re: State of LDP3430 platform) Tony Lindgren
2011-01-18 22:35 ` [PATCH] omap1: Fix booting for 15xx and 730 with omap1_defconfig " Tony Lindgren
2011-01-18 23:21 ` Tony Lindgren
2011-01-19 18:43 ` [PATCH] omap1: Fix sched_clock implementation when both MPU timer and 32K timer are used " Tony Lindgren
2011-01-19 18:44 ` [PATCH] omap1: Fix sched_clock for the MPU timer " Tony Lindgren
2011-01-19 13:43 ` State of LDP3430 platform Jarkko Nikula
2011-01-18 1:25 ` Tony Lindgren
2011-01-18 19:24 ` Paul Walmsley
2011-01-15 23:47 ` Woodruff, Richard
2011-01-17 17:34 ` Tony Lindgren
2011-01-17 17:44 ` Woodruff, Richard
2011-02-12 16:02 ` Russell King - ARM Linux [this message]
2011-02-12 16:10 ` Russell King - ARM Linux
2011-02-23 22:50 ` Tony Lindgren
2011-02-23 23:22 ` Woodruff, Richard
2011-02-24 7:08 ` Rajendra Nayak
2011-02-24 13:07 ` Rajendra Nayak
2011-02-24 8:21 ` Janorkar, Mayuresh
2011-02-24 8:47 ` Russell King - ARM Linux
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=20110212160216.GA22694@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=r-woodruff2@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
/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