From: Dirk Behme <dirk.behme@googlemail.com>
To: "Pharaoh ." <pharaoh137@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Broken uwire usage in lcd_p2.c, was: Unable to compile Linux 2.6.21 from source.mvista.com
Date: Mon, 07 May 2007 16:39:35 +0200 [thread overview]
Message-ID: <463F3A27.3000501@googlemail.com> (raw)
In-Reply-To: <61445c750705070659v1d2fd55akbd8ed2d1108459f9@mail.gmail.com>
Pharaoh . wrote:
> I am latest 2.6.21 source from source.mvista.com. I am trying to compile
> the
> kernel for my omap 850 based board.
>
> I am getting following error:
>
> 1. make ARCH=arm omap_perseus2_730_defconfig => works well
>
> 2. make ARCH=arm
>
> CC drivers/video/omap/lcd_p2.o
> drivers/video/omap/lcd_p2.c:151:39: ../drivers/ssi/omap-uwire.h: No such
> file or directory
> drivers/video/omap/lcd_p2.c: In function `p2_panel_enable':
> drivers/video/omap/lcd_p2.c:185: warning: implicit declaration of function
> `omap_uwire_configure_mode'
> drivers/video/omap/lcd_p2.c:187: warning: implicit declaration of function
> `omap_uwire_data_transfer
>
>
> There is no file like ../drivers/ssi/omap-uwire.h, I have checked. Please
> enlighten.
uwire code moved to drivers/spi. Unfortunately, lcd_p2.c isn't
converted to new uwire code yet, see [1]. Do you like to send a patch
for this? Looks like lcd_h2.c was converted, maybe this can help.
Dirk
[1]
http://linux.omap.com/pipermail/linux-omap-open-source/2007-March/009254.html
prev parent reply other threads:[~2007-05-07 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 13:59 Unable to compile Linux 2.6.21 from source.mvista.com Pharaoh .
2007-05-07 14:39 ` Dirk Behme [this message]
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=463F3A27.3000501@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=pharaoh137@gmail.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