All of lore.kernel.org
 help / color / mirror / Atom feed
From: "stanley.miao" <stanley.miao@windriver.com>
To: Sam Duan <sam_duan@ovt.com.cn>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] OMAP: Add OMAP_LDP platform support.
Date: Thu, 04 Dec 2008 19:28:12 +0800	[thread overview]
Message-ID: <1228390092.7392.53.camel@localhost> (raw)
In-Reply-To: <001b01c955f4$e4f08940$aed19bc0$@com.cn>

The first patch(PATCHv2 1/3) in this thread have fixed this problem. It
has not been pushed in. 

Stanley.

On Thu, 2008-12-04 at 17:44 +0800, Sam Duan wrote:
> Hi Stanley,
> 
> I git clone the
> tree(http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.gi
> t)
> and configured the kernel with omap_ldp_defconfig but met some compile
> errors.
> It seems like the line "gpio_direction_input(eth_gpio) " was not patched in.
> It's "omap_set_gpio_direction(eth_gpio, 1)" at Line343 in
> arch/arm/mach-omap2/board-ldp.c which caused an error "implicit
> declaration";
> I replaced omap_set_gpio_direction(eth_gpio, 1) with
> gpio_direction_input(eth_gpio) but the same error appeared with
> drivers/video/omap/lcd_ldp.c for "omap_set_gpio_direction" and
> "omap_set_gpio_dataout".
>  
> Did I miss some other patches? Are there any patchs can make the kernel
> compiled with omap_ldp_defconfig?
> Thanks
> Sam
> 

  reply	other threads:[~2008-12-04 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04  9:44 [PATCH 1/2] OMAP: Add OMAP_LDP platform support Sam Duan
2008-12-04 11:28 ` stanley.miao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-26 23:12 [PATCHv2 0/3] OMAP_LDP support in linux-git tree Tony Lindgren
2008-11-27 15:34 ` [PATCH 1/2] OMAP: Add OMAP_LDP platform support Stanley.Miao

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=1228390092.7392.53.camel@localhost \
    --to=stanley.miao@windriver.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sam_duan@ovt.com.cn \
    /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.