From: "rememberme_2000" <rememberme_2000@126.com>
To: linux-omap-open-source@linux.omap.com
Subject: Is there wrong with io.h???
Date: Tue, 19 Sep 2006 17:00:01 +0800 (CST) [thread overview]
Message-ID: <450FB191.000126.10383@bj126app3.126.com> (raw)
hi:
i 'd written a simple program.and found some wrong with io.h.
the following code is:
that:
#include<asm/arch/gpio.h>
main()
{
omap_request_gpio(3);
omap_set_gpio_direction(3,1);
}
compile command :
arm-linux-gcc -I linux-2.6.13.4/include -c main.c
and then i got the following error information:
linux-2.6.13.4/include/asm/arch/io.h:91 error:parse error before "offset"
linux-2.6.13.4/include/asm/arch/io.h:97 error:parse error before "offset"
linux-2.6.13.4/include/asm/arch/io.h:102 error:parse error before "offset".
the toolchains which i used is gcc-3.4.1 for omap 5912,and the kernel is linux-2.6.13.4 for osk.
Is the file wrong? i'm not sure about it!!!!!!!
who has interest in it? i hope to get your help.
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
reply other threads:[~2006-09-19 9:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=450FB191.000126.10383@bj126app3.126.com \
--to=rememberme_2000@126.com \
--cc=linux-omap-open-source@linux.omap.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