From: phil@pjd.me.uk (Philip Downer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: FPGA registers userspace interface?
Date: Mon, 03 Jan 2011 13:00:30 +0000 [thread overview]
Message-ID: <4D21C86E.6060503@pjd.me.uk> (raw)
In-Reply-To: <AANLkTikyfdSftQYmjsNZkzmTKO3K79_Jz7kzgK7_sWGy@mail.gmail.com>
On 03/01/11 12:47, Kfir Lavi wrote:
> I have a FPGA that is constantly changing (its on development phase).
> I want to let userspace app to update those registers, but don't want to
> create an API yet.
> What is the best way to open a range of registers to userspace, so no
> driver update is required?
When I had to do this recently I used sysfs, I have no idea if it's the
best way but it certainly was very effective. Remember in sysfs that
each file should only have one value.
Once it's setup though you can just write to the sysfs files, I started
by writing simple perl scripts to test things before starting to write
more complex apps.
HTH
Phil
next prev parent reply other threads:[~2011-01-03 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 12:47 FPGA registers userspace interface? Kfir Lavi
2011-01-03 12:57 ` Daniel Baluta
2011-01-03 13:00 ` Philip Downer [this message]
2011-01-03 15:09 ` Kfir Lavi
2011-01-03 15:21 ` Kfir Lavi
2011-01-03 20:52 ` Daniel Baluta
2011-01-03 21:29 ` Greg KH
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=4D21C86E.6060503@pjd.me.uk \
--to=phil@pjd.me.uk \
--cc=kernelnewbies@lists.kernelnewbies.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).