From: "stanley.miao" <stanley.miao@windriver.com>
To: felipe.balbi@nokia.com
Cc: linux-omap@vger.kernel.org
Subject: Re: omapfb problem on 3430sdp
Date: Wed, 27 Aug 2008 21:03:47 +0800 [thread overview]
Message-ID: <1219842228.15818.97.camel@localhost> (raw)
In-Reply-To: <20080827094318.GB9340@gandalf.research.nokia.com>
I updated the kernel again. Now the kernel from omapzoom.org is OK, but
the kernel from "source.mvista.com/git/linux-omap-2.6.git" still can't
work.
The LCD drivers in omapzoom.org and in linux-omap-2.6 use different
files. the LCD driver in omapzoom.org is omap_disp_out.c and omap_fb.c
while the driver in linux-omap-2.6 is lcd_2430sdp.c and omapfb_main.c.
The following MACRO are defined differently. Can anyone tell me why ?
In the file omap_disp_out.c in omapzoom.org :
113 #define LCD_PANEL_ENABLE_GPIO 5
114 #define LCD_PANEL_BACKLIGHT_GPIO 8
In the file lcd_2430sdp.c in linux-omap-2.6:
35 #define SDP3430_LCD_PANEL_BACKLIGHT_GPIO 24
36 #define SDP3430_LCD_PANEL_ENABLE_GPIO 28
Why are they defined differently?
Thanks
Stanley.
On Wed, 2008-08-27 at 12:43 +0300, Felipe Balbi wrote:
> On Wed, Aug 27, 2008 at 05:28:36PM +0800, ext stanley.miao wrote:
> > Hardware:
> > Mainboard: 750-2094-001(C)
> > Display board: 750-2081-101(B)
> >
> > Software:
> > the lastest kernel from linux-omap-2.6 and from omapzoom.org.
> >
> > The linux bootup logo is green, and LCD is dark. It looks like backlight
> > disabled.
> >
> > I commented the following two sentences in lcd_2430.c, there is still
> > the same thing. It seems these two sentences doesn't work.
> >
> > 96 omap_set_gpio_dataout(enable_gpio, 1);
> > 97 omap_set_gpio_dataout(backlight_gpio, 1);
> >
> > Both the the latest kernels from omapzoom.org and linux-omap-2.6 have
> > this problem. However, the old version in linux-omap-2.6, 2.6.21,
> > doesn't have this problem.
>
> Cool could you bisect and try to find the commit that broke it ?
>
> $ git bisect start
> $ git bisect good v2.6.21-omap1
> $ git bisect bad
>
> Should help you. Read git help bisect for more information. When you
> find the exact commit that broke lcd_2430.c, report here with the commit
> id.
>
> Just a note, if you can't build the bisect point, reset to some points
> before and try again until you find a commit that builds, do not mark
> them as bad.
>
next prev parent reply other threads:[~2008-08-27 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 9:28 omapfb problem on 3430sdp stanley.miao
2008-08-27 9:43 ` Felipe Balbi
2008-08-27 13:03 ` stanley.miao [this message]
2008-08-27 13:32 ` Felipe Balbi
2008-08-27 14:09 ` iqbal
2008-08-27 14:27 ` iqbal
2008-08-29 12:28 ` stanley.miao
[not found] ` <c656a4d20808290848q3c676ddbn19df1d5fff43e5ad@mail.gmail.com>
[not found] ` <1220232703.14924.68.camel@localhost>
2008-09-01 6:38 ` arun c
-- strict thread matches above, loose matches on Subject: below --
2008-07-30 6:35 OMAPFB problem on 3430SDP Tomi Valkeinen
2008-07-30 6:51 ` iqbal
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=1219842228.15818.97.camel@localhost \
--to=stanley.miao@windriver.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.