Userspace libs
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
?
Jonathan Cameron
maintainerQuoted 25 lines · Robin
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_scopeSource is at:
https://github.com/analogdevicesinc/iio-oscilloscopeAs 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.cWhich 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
Quoted 7 lines
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.
All the above looks good and it is very nice to have some non trivial userspace support. I'll be happy to see any updates/cleanups to iio-utils.h but keep in mind that it is only really meant to be a trivial in kernel tree example. The original plan was to have a separately maintained userspace library to do things 'properly'. I guess it depends on exactly
what changes you are thinking of. The networking stuff in particular
might introduce some non kernel dependencies that may or may not be a problem.
Quoted 3 lines
Is there a list of other things people want to see from userspace? [2]
Nope. Probably should be though. Well volunteered!
Right now we don't really have a clean list of what people want on the kernel side, just a lot of randomly scattered mailing list threads.
Quoted 4 lines
-Robin
[1] Which reminds me - is this planned on moving out
of ./drivres/staging/iio/Documentation into./Documentation/iio?
err. Yes. Keep forgetting to do it. Ah well next cycle ;) Lots of stuff still to move in general.
Quoted 11 lines
[2] I have been going through:
- zio-dump http://www.ohwr.org/projects/zio/wiki/Readme
- Comedilib various
?--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat 16 Feb 2013 07:46, Jonathan Cameron pondered:
Quoted 2 lines · Robin
Quoted 1 line
Jonathan:
[snip]
Quoted 10 lines
Quoted 5 lines
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.All the above looks good and it is very nice to have some non trivial userspace support. I'll be happy to see any updates/cleanups to
iio-utils.hbut keep in mind that it is only really meant to be a trivial in kernel tree example.
is there any performance metrics that we want the in-tree version to hit?
The existing versions are certainly slim on memory, but use malloc, which may cause memory leaks if the person on the application side isn't careful freeing things, or cause performance issues, or just cause plain failures in low memory embedded systems...
Quoted 2 lines
The original plan was to have a separately maintained userspace library to do things 'properly'.
Where was this suppost to live?
Quoted 1 line
I guess it depends on exactly what changes you are thinking of.
There are some features which we use to "self-discover" the installed devices/drivers.
return a string of names
handle unsigned ints in the read/write functions
Some minor stuff.
Quoted 3 lines
The networking stuff in particular
might introduce some non kernel dependencies that may or may not be a problem.
Ack - I think that sits beside yours. iio_utils_attach.h and the network one is iio_utils_net.h (ot something like that). It's the same structures, similar function names, it's does it include a IP address, or a path...
Quoted 5 lines
Quoted 1 line
Is there a list of other things people want to see from userspace? [2]
Nope. Probably should be though. Well volunteered!
Right now we don't really have a clean list of what people want on the kernel side, just a lot of randomly scattered mailing list threads.
Any in specific stand out?
Quoted 6 lines
Quoted 3 lines
[1] Which reminds me - is this planned on moving out
of ./drivres/staging/iio/Documentation into./Documentation/iio?err. Yes. Keep forgetting to do it. Ah well next cycle ;) Lots of stuff still to move in general.
Thanks.
Quoted 9 lines
Quoted 9 lines
[2] I have been going through:
- zio-dump http://www.ohwr.org/projects/zio/wiki/Readme
- Comedilib various
?--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Robin,
Quoted 8 lines · Robin
On Sat 16 Feb 2013 07:46, Jonathan Cameron pondered:
Quoted 2 lines · Robin
Quoted 1 line
Jonathan:
[snip]
Quoted 2 lines
The original plan was to have a separately maintained userspace library to do things 'properly'.
Where was this suppost to live?
We started a project on sourceforge some time ago. It's currently a bit out of date, but you're welcome to throw away the existing parts and replace it with your code. The main tool right now is called 'lsiio' and does the same as 'lsusb' or 'lspci'.
http://sourceforge.net/projects/iioutils/
Signature · 2 lines
Regards, Manuel Stahl