From: "Morris, Richard" <Richard.Morris@lifetech.com>
To: EnneGi <enricogiordano1992@gmail.com>
Cc: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: How to create a GPIO driver
Date: Wed, 13 Mar 2013 15:36:00 -0000 [thread overview]
Message-ID: <BD27DAD5-48AA-4751-B191-EDD2E005D88A@lifetech.com> (raw)
In-Reply-To: <1363126636423-225218.post@n7.nabble.com>
The pin arguments for the hal_LPC17xx_gpio_xxx() functions you describe are likely provided by a macro, of which I don't know the name. It may be in the var_io.h file for your eCos distribution.
Once you know the value of the PIN argument, you can call the hal_LPC17XX_gpio_xxx() functions of your distribution.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-03-13 15:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 18:19 [ECOS] " EnneGi
2013-03-10 18:59 ` Andrew Lunn
2013-03-10 19:23 ` Ilija Kocho
2013-03-10 22:57 ` [ECOS] " EnneGi
2013-03-11 14:24 ` Morris, Richard
2013-03-11 16:52 ` EnneGi
2013-03-12 14:49 ` [ECOS] " Morris, Richard
2013-03-12 22:17 ` [ECOS] " EnneGi
2013-03-13 15:36 ` Morris, Richard [this message]
2013-03-14 14:41 ` EnneGi
2013-03-14 15:05 ` Michael Jones
2013-03-14 15:24 ` EnneGi
2013-03-14 15:26 ` EnneGi
2013-03-14 15:32 ` Michael Jones
2013-03-14 15:35 ` EnneGi
2013-03-14 15:43 ` [ECOS] " Michael Jones
2013-03-14 15:53 ` [ECOS] " EnneGi
2013-03-14 15:58 ` Michael Jones
2013-03-14 16:09 ` [ECOS] " Morris, Richard
2013-03-14 17:08 ` [ECOS] " EnneGi
2013-03-14 18:17 ` [ECOS] " Morris, Richard
2013-03-14 18:27 ` [ECOS] " EnneGi
2013-03-14 19:59 ` EnneGi
2013-03-14 21:10 ` Morris, Richard
2013-03-15 19:09 ` EnneGi
2013-03-15 22:14 ` EnneGi
2013-03-14 15:06 ` EnneGi
2013-03-14 15:21 ` Michael Jones
2013-03-12 22:36 ` EnneGi
2013-03-11 14:11 ` [ECOS] " Morris, Richard
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=BD27DAD5-48AA-4751-B191-EDD2E005D88A@lifetech.com \
--to=richard.morris@lifetech.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=enricogiordano1992@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).