From: tomi.valkeinen@ti•com (Tomi Valkeinen)
To: linux-arm-kernel@lists•infradead.org
Subject: OMAP2430 SDP boot broken after Linus' rmk merge
Date: Thu, 25 Jul 2013 09:50:13 +0300 [thread overview]
Message-ID: <51F0CAA5.8010108@ti.com> (raw)
In-Reply-To: <51F0C841.8000900@ti.com>
On 25/07/13 09:40, Tomi Valkeinen wrote:
> On 24/07/13 17:52, Russell King - ARM Linux wrote:
>
>> I also continue to be disappointed by the lack of things working on the
>> 4430 - it's been a number of years now and _still_ the on-board LCDs do
>> not work. People have tried to blame that on hardware faults and the
>> like, but they're just being idiotic when they say stuff like that. It
>> can't be hardware faults when the kernel supplied with the board is able
>> to make them work to the extent that userspace can play back video on all
>> three output devices simultaneously, without hiccup or any imperfection.
>> I don't know whether it's just that the backlight support isn't working
>> or what - because any information on the 4430 seems to be a tightly
>> controlled secret that only a few select people are permitted to know
>> about. As far as I'm concerned, much of the hardware is a black box to
>> me.
>
> The 4430SDP's backlight hasn't been working in the mainline due to
> missing support from the TWL driver. But we finally did get that in for
> 3.10 (or maybe 3.9), and booting 3.10 non-DT kernel brings up the
> backlights. However, the BL doesn't work yet with DT boot, so again with
> 3.11, with no board files, the BL is out... Sigh.
Ah, sorry, I take that back. Backlight seems to be working fine with 3.11.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130725/de5e0ef5/attachment.sig>
next prev parent reply other threads:[~2013-07-25 6:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 18:07 OMAP2430 SDP boot broken after Linus' rmk merge Paul Walmsley
2013-07-22 18:43 ` Russell King - ARM Linux
2013-07-22 20:07 ` Paul Walmsley
2013-07-23 7:03 ` Rajendra Nayak
2013-07-23 7:07 ` Paul Walmsley
2013-07-23 9:05 ` Rajendra Nayak
2013-07-24 13:56 ` Will Deacon
2013-07-24 14:17 ` Santosh Shilimkar
2013-07-24 14:20 ` Will Deacon
2013-07-24 14:45 ` Santosh Shilimkar
2013-07-27 4:10 ` Paul Walmsley
2013-07-27 12:22 ` Will Deacon
2013-07-28 5:38 ` Paul Walmsley
2013-07-28 5:46 ` [PATCH] ARM: v6: avoid remaining accesses to missing CP15 registers on ARM1136 r0 Paul Walmsley
2013-07-28 5:58 ` Paul Walmsley
2013-07-28 6:00 ` [PATCH v2] " Paul Walmsley
2013-07-28 19:58 ` Paul Walmsley
2013-07-28 5:43 ` [PATCH] ARM: v6: avoid read_cpuid_ext() on ARM1136r0 in cache_ops_need_broadcast() Paul Walmsley
2013-07-28 11:10 ` Will Deacon
2013-07-28 11:52 ` Russell King - ARM Linux
2013-07-28 19:56 ` Paul Walmsley
2013-07-28 19:47 ` Paul Walmsley
2013-07-28 20:16 ` [PATCH] ARM: v6: prevent gcc from reordering extended CP15 reads above is_smp() test Paul Walmsley
2013-07-29 7:30 ` Tony Lindgren
2013-07-29 10:02 ` Will Deacon
2013-07-30 10:58 ` Paul Walmsley
2013-07-30 11:32 ` [PATCH v2] ARM: v6: prevent gcc 4.5 " Paul Walmsley
2013-07-30 15:04 ` Will Deacon
2013-07-24 14:52 ` OMAP2430 SDP boot broken after Linus' rmk merge Russell King - ARM Linux
2013-07-24 15:40 ` OMAP4430 SDP boot issues.. (Was Re: OMAP2430 SDP boot broken after Linus' rmk merge) Santosh Shilimkar
2013-07-24 17:23 ` Russell King - ARM Linux
2013-07-24 18:17 ` Santosh Shilimkar
2013-07-25 6:40 ` OMAP2430 SDP boot broken after Linus' rmk merge Tomi Valkeinen
2013-07-25 6:50 ` Tomi Valkeinen [this message]
2013-07-26 22:59 ` Russell King - ARM Linux
2013-08-07 18:09 ` Paul Walmsley
2013-08-08 5:37 ` Rajendra Nayak
2013-08-08 10:20 ` Rajendra Nayak
2013-07-23 10:33 ` Jonathan Austin
2013-07-31 0:57 ` Paul Walmsley
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=51F0CAA5.8010108@ti.com \
--to=tomi.valkeinen@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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