- API changes for the latest driver (retreiving output configuration)
- updated info on gateware installation
- dropped 2.6.24 support
- consistency fixes (Time-stamps -> timestamps, etc.)
- moved raw I/O info into an appendix for developers.

The official release bitstreams are available at the Fine Delay
project website, along with release info and changelog.

This tool is deprecated, please use lib/ and tools/ tools instead.

To get the output configuration, a simple readback of the
sysfs start/end/delta parameters is not enough, because
start and end are affected by delay-offset and the tdc
offset. This patch addresses the problem in an incomplete
manner

The usual boring stuff to shut up the compiler warnings like
  fdelay-read.c:57: warning: format ‘%lli’ expects type ‘long long int’,
  but argument 3 has type ‘uint64_t’

We need to know the programmed delay, hence this extends the API
of the library to recover it in ps units. The ensuing arithmetic
is also added

A channel start, end and delta time registers are exported
read-only through sysfs to allow easy readback of the configured
values.

Now we can read back the programmed values of output registers,
so we allow its readout from user space

This patch unifies VIC interrupt handling by removing VIC support code from the driver
and using the one provided by the carrier. Since the SVEC now supports IRQs too, both
carriers can benefit from interrupts.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Meanwhile, turn ZIO to @sc{zio} in the whole manual.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

moreover, I was reading the hardware fifo both at interrupt level and
at tasklet level.  The tasklet read-out is mandatory if we are using
a timer instead of an interrupt (the timer is the tasklet function),
but should be avoided if we have interrupts.

Sometimes I got duplicate samples because the tasklet reading the
hardware fifo was preempted by the interrupt handler.

Now I can stamp 50kHz bursts withouth data loss, provided the zio
buffer is big enough.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Now that we are self-timed, the only reason white the active input
block is null may be a zio buffer-full situation.  We need to keep
the loop running anyways (by discarding one sample), because we miss
notification when the buffer has new space.

We can't change zio to this aim, as it would be extra code in a hot
path: we'd better loose one block when the buffer is full, we would
loose it soon after anyways, since the system is overloaded.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This was not possible with the older zio, but now we have support
for that.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Changing critical trigger parameters forces an abort of pending
blocks.  This means that a running reader will loos its own active
block when lib/fdelay-pulse is called (the incoming samples are not
lost, but the reader must be restarted).

The previous code would work with the new self-timed feature in recent
zio master, but by now this patch allows remaining at zio-1.0 -- in
the "fixes" branch.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Juan David Gonzalez Cobas <dcobas@cern.ch>

Although the standard include path in the build tree is
declared in the makefile, deployment of the library in a separate
environment will rely on coexistent lib and kernel .h files,
hence the double quotes

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Juan David Gonzalez Cobas <dcobas@cern.ch>

doc: added some info about SVEC, documented WR options in fdelay-board-time and mentioned fdelay-pulse-tom. VME-specific documentation still to be done.