From: "Getz, Robin" <robin.getz@analog.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Lars-Peter Clausen <lars-peter.clausen@analog.com>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Userspace libs
Date: Wed, 13 Feb 2013 14:12:57 -0500 [thread overview]
Message-ID: <201302131412.58742.robin.getz@analog.com> (raw)
Jonathan:
We made an "iio-scope" - a real time visualiser which runs natively on the
embedded hardware. The application supports plotting of the captured data in
three different modes (time domain, frequency domain and constatation).
Description (and screen shots) are at:
http://wiki.analog.com/resources/eval/user-guides/ad-fmcomms1-ebz/software/linux/applications/iio_scope
Source is at:
https://github.com/analogdevicesinc/iio-oscilloscope
As you can see, it includes some of your code:
https://github.com/analogdevicesinc/iio-oscilloscope/blob/master/iio_utils.h
Which (I think) is still in ./staging/iio/Documentation/ [1]
We build on some of that:
https://github.com/analogdevicesinc/iio-oscilloscope/blob/master/iio_utils.c
Which really isn't specific to the scope, and could be pushed to where ever we
decide the .h file lives (this is a question/suggestion).
We also have a network stack for IIO.
http://wiki.analog.com/resources/tools-software/linux-software/iio_cmdsrv
https://github.com/analogdevicesinc/iio-cmdsrv
I would like to re-write some of the existing iio-utils.h (so iio device
context is managed by the application), to become a little more thread
friendly, and also merge in some of the networking piece - so when using a
headless embedded device - userspace doesn't need to change/manage things
much.
Is there a list of other things people want to see from userspace? [2]
-Robin
[1] Which reminds me - is this planned on moving out
of ./drivres/staging/iio/Documentation into ./Documentation/iio ?
[2] I have been going through:
- zio-dump http://www.ohwr.org/projects/zio/wiki/Readme
- Comedilib various
?
next reply other threads:[~2013-02-13 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 19:12 Getz, Robin [this message]
2013-02-16 12:46 ` Userspace libs Jonathan Cameron
2013-02-18 20:15 ` Getz, Robin
2013-02-19 8:38 ` Manuel Stahl
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=201302131412.58742.robin.getz@analog.com \
--to=robin.getz@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@cam.ac.uk \
--cc=lars-peter.clausen@analog.com \
--cc=linux-iio@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.