public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <menon.nishanth@gmail.com>
To: Hunyue Yau <hyau@mvista.com>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap-open-source@linux.omap.com
Subject: Re: 2430 FB driver issues
Date: Wed, 18 Jul 2007 21:21:49 -0500	[thread overview]
Message-ID: <469ECABD.4020106@gmail.com> (raw)
In-Reply-To: <200707091204.21320.hyau@mvista.com>

All,
Apologies on a late response..
Hunyue Yau stated on 7/9/2007 2:04 PM:
> Paul,
>
> It should have been working when it went it. The commit entry 
> adding it should be:
>
> commit 4ed427693dd7e0d4fd00a493988cefaa17accebc
> Author: Hunyue Yau <hyau@mvista.com>
>
>   
to keep things simple, here is the set of facts that i gathered:
a) With Hunyue patch(4ed427693dd7e0d4fd00a493988cefaa17accebc),
Framebuffer is enabled, BUT LCD backlight does not come on, nor does
anything come to the display. Intrestingly, as Hunyue mentioned, NO errors.
b) Patch from Paul (5c6cd5d71bdb1a8536238c7812f1dbd6a68bc542), enables
LCD on 2430SDP with LCD backlight and all.. This is the first patch that
makes 2430SDP LCD work and the error that i started this chain with exists!
c) all intermediate patches between (a) and (b) including the following:
Richard W (bbe8d2b1654809c39be2e9ecc91dd5632006a2cb)
Tony (517928578afaea422975fd8216242fdd067b56a2)
Tony(dd1d9a62f7cd60b544013eb429d6a3137617f0b2)
all retain the same state as I mentioned in (a).

Not much useful information except that my guess is FB LCD is broken on
2430SDP as of date and it is possibly broken from the time it is
enabled.. Since i do see Tony punching in a bunch every weekend, did
Hunyue test with the git latest once Tony finished pushing all patches?
- esp since May 25th is the time when the major clock/prcm  framework
patches from Paul W went into git.
> On Sunday 08 July 2007 16:01, Paul Walmsley wrote:
>   
>> You mentioned earlier that this code formerly worked for you before the 
>> PRCM changes.  Do you have a commit ID or revision from a working version? 
>> if so then perhaps Nishanth or someone else with a 2430 SDP might be able 
>> to git-bisect to find which commit broke it.
>>
>>     
Hmm... I did try this, and i failed badly.. this is a topic of a
seperate mail..

Regards,
Nishanth Menon

  reply	other threads:[~2007-07-19  2:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  0:06 2430 FB driver issues nishanth menon
2007-07-06 19:21 ` Kevin Hilman
2007-07-06 22:22   ` Syed Mohammed, Khasim
2007-07-06 22:40     ` Syed Mohammed, Khasim
2007-07-08 23:01   ` Paul Walmsley
2007-07-09 19:04     ` Hunyue Yau
2007-07-19  2:21       ` Nishanth Menon [this message]
2007-07-19 16:32         ` Woodruff, Richard
2007-07-19 16:54           ` Syed Mohammed, Khasim
2007-07-19 18:37             ` Woodruff, Richard
  -- strict thread matches above, loose matches on Subject: below --
2007-07-26 17:05 Timothy Tang

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=469ECABD.4020106@gmail.com \
    --to=menon.nishanth@gmail.com \
    --cc=hyau@mvista.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=paul@pwsan.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