From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: <linuxppc-dev@ozlabs.org>
Subject: Using GPIO
Date: Thu, 15 May 2008 18:35:25 +0200 [thread overview]
Message-ID: <02f401c8b6a9$b1e062e0$ad289e86@LPSC0173W> (raw)
Hello all,
I'm trying to use the Xilinx GPIO from a user program.
Since I haven't managed to compile their example (simon.c is given without a
makefile), I wanted to try using /dev/gpio...
So I added
/dev/gpio0 c 666 0 0 10 185 - - -
to device_table.txt when I generated my root filesystem with buildroot, but
apparently this leads nowhere as it's not visible in /proc/devices.
Is there some example or tutorial on how to use CONFIG_XILINX_GPIO ? Either
as a device or as API calls...
--
Guillaume Dargaud
http://www.gdargaud.net/
next reply other threads:[~2008-05-15 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 16:35 Guillaume Dargaud [this message]
2008-05-15 18:39 ` Using GPIO John Bonesio
2008-05-15 18:56 ` Stephen Neuendorffer
2008-05-16 8:15 ` Guillaume Dargaud
2008-05-16 16:17 ` John Linn
2008-05-19 11:56 ` Guillaume Dargaud
2008-05-19 13:42 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2008-05-19 15:23 Guillaume Dargaud
2008-06-06 7:51 Ludovic Desroches
2008-06-06 16:09 ` Guillaume Dargaud
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='02f401c8b6a9$b1e062e0$ad289e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@ozlabs.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 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 NNTP newsgroup(s).