From: Lars-Peter Clausen <lars@metafoo.de>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: linux-iio@vger.kernel.org, greg@kroah.com,
linux-kernel@vger.kernel.org, federico.vaga@gmail.com,
dcobas@cern.ch, siglesia@cern.ch, manohar.vanga@cern.ch
Subject: Re: [RFC PATCH 0/7] Introducing ZIO, a new I/O framework
Date: Sat, 26 Nov 2011 19:09:20 +0100 [thread overview]
Message-ID: <4ED12B50.9090206@metafoo.de> (raw)
In-Reply-To: <cover.1322328073.git.rubini@gnudd.com>
On 11/26/2011 06:30 PM, Alessandro Rubini wrote:
> This RFC patch-set introduces the ZIO framework for input/output,
> which will be used in the new series of drivers by the BE-CO-HT
> group at CERN.
>
> The use-case it is meant to cover is very fast I/O with
> hardware-provided timestamps. The first production driver we will
> support is a 100Ms/s 4-channel 14-bit ADC (developed on ohwr: see
> http://www.ohwr.org/projects/fmc-adc-100m14b4cha ). We need similar
> bandwidth on output.
>
> The synchronization engine of that FMC card and other ones is going to
> be White Rabbit (http://www.ohwr.org/projects/white-rabbit).
>
> Currently, the patch-set includes one example driver (zio-zero)
> that behaves like /dev/zero and /dev/urandom. Other drivers will
> come soon, both demo and real hardware.
>
> Slides for a tutorial on the design ideas are online here:
> http://www.ohwr.org/attachments/881/zio-111123.pdf
>
> A list of pending issues and development plans is online at:
> http://www.ohwr.org/projects/zio/wiki/Todo
You've Cc'ed the IIO mailinglist, so you know about the IIO framework. Could
you explain why you need a new framework and your devices can't be supported by
the IIO framework? After a first quick glance ZIO looks to me like a subset of IIO.
- Lars
next prev parent reply other threads:[~2011-11-26 18:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 17:30 [RFC PATCH 0/7] Introducing ZIO, a new I/O framework Alessandro Rubini
2011-11-26 17:30 ` [RFC PATCH 1/7] Documentation: add docs for drivers/zio Alessandro Rubini
2011-11-26 20:00 ` Greg KH
2011-11-26 21:48 ` Federico Vaga
2011-11-26 22:16 ` Jonathan Cameron
2011-11-26 22:53 ` Alessandro Rubini
2011-12-06 5:12 ` Randy Dunlap
2011-11-26 17:30 ` [RFC PATCH 2/7] include/linux: add headers " Alessandro Rubini
2011-11-26 20:02 ` Greg KH
2011-11-26 21:46 ` Federico Vaga
2011-11-27 9:32 ` Greg KH
2011-11-28 14:56 ` Federico Vaga
2011-11-30 6:21 ` Greg KH
2011-11-26 17:30 ` [RFC PATCH 3/7] drivers/zio: core files for the ZIO input/output Alessandro Rubini
2011-11-26 20:03 ` Greg KH
2011-11-26 22:58 ` Federico Vaga
2011-11-27 9:33 ` Greg KH
2011-11-28 14:59 ` Federico Vaga
2011-11-26 17:30 ` [RFC PATCH 4/7] drivers/zio: add triggers and buffers Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 5/7] drivers/zio: add the zio-zero device driver Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 6/7] drivers/zio: add user-space tool zio-dump Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 7/7] zio: insert in Kbuild so it is actually compiled Alessandro Rubini
2011-11-26 18:09 ` Lars-Peter Clausen [this message]
2011-11-26 19:11 ` [RFC PATCH 0/7] Introducing ZIO, a new I/O framework Alessandro Rubini
2011-12-01 21:41 ` Linus Walleij
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=4ED12B50.9090206@metafoo.de \
--to=lars@metafoo.de \
--cc=dcobas@cern.ch \
--cc=federico.vaga@gmail.com \
--cc=greg@kroah.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@cern.ch \
--cc=rubini@gnudd.com \
--cc=siglesia@cern.ch \
/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).