- 01 Jul, 2014 1 commit
-
-
Tomasz Wlostowski authored
This patch allows to load an userspace-provided bitstream to a SVEC card through sysfs attributes. It does not rely on kernel firmware loader mechanism (so the gateware files are not restricted to /lib/firmware directory). Userspace communication is ensured through firmware_blob and firmware_cmd sysfs entries. The former inputs the bitstream in PAGESIZEd chunks, the latter receives gateware update start/finish commands.
-
- 12 Jun, 2014 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 11 Jun, 2014 1 commit
-
-
Federico Vaga authored
The kbuild environment writes into 'obj' the path to the output directory automatically. This avoid us to specify 'M' Signed-off-by: Federico Vaga <federico.vaga@cern.ch> Acked-by: Alessandro Rubini <rubini@gnudd.com>
-
- 12 May, 2014 1 commit
-
-
Tomasz Wlostowski authored
-
- 11 May, 2014 1 commit
-
-
Tomasz Wlostowski authored
-
- 09 May, 2014 1 commit
-
-
Tomasz Wlostowski authored
-
- 02 Apr, 2014 5 commits
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
- 01 Apr, 2014 1 commit
-
-
Tomasz Wlostowski authored
-
- 26 Mar, 2014 1 commit
-
-
Tomasz Wlostowski authored
This lets us use the driver without re-declaring every SVEC in the CCDB to have window size of 0x80000.
-
- 25 Mar, 2014 1 commit
-
-
Tomasz Wlostowski authored
kernel: prevent creating an A24 window at 0xf00000 (Tsi148 uses same address range for its internal regs)
-
- 06 Mar, 2014 6 commits
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
Conflicts: kernel/svec-sysfs.c
-
Tomasz Wlostowski authored
Previous size of 0x100000 allowed for up to 16 cards configured in A24. We have some crates with more than 16 slots.
-
- 17 Jan, 2014 1 commit
-
-
Juan David González Cobas authored
The new vme_addr sysfs attribute had incorrect validation: it was the old value stored in the card structure who was validated by mistake. Moreover, the vme_addr is an offset, so it has to be compared with the configured size, not the end of the (absolute) vme address range of the board.
-
- 10 Dec, 2013 2 commits
-
-
Juan David González Cobas authored
Use the vme_<whatever> convention
-
Juan David González Cobas authored
-
- 08 Dec, 2013 3 commits
-
-
Juan David González Cobas authored
-
Juan David González Cobas authored
-
Juan David González Cobas authored
We should use at least 27e6b00, to avoid the readl/writel naming conflicts addressed by that commit
-
- 22 Nov, 2013 3 commits
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
kernel: fix edge emulation timeout & check for subsequent VIC IRQs before returning from the handler. The latter keeps handling VIC irqs in a loop until none of the IRQ lines is active anymore. This prevents situations when two or more IRQs come almost simultaneously (e.g. reading sychronized sample buffers) and the one with lower priority gets starved.
-
Tomasz Wlostowski authored
-
- 18 Nov, 2013 1 commit
-
-
Tomasz Wlostowski authored
-
- 24 Oct, 2013 1 commit
-
-
Tomasz Wlostowski authored
-
- 27 Sep, 2013 9 commits
-
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
The VIC is the standard BE-CO-HT module for multiplexing FPGA-internal IRQ sources. Support for it in the carrier driver is provided for convenience of FMC driver developers. More info in the svec-sw manual.
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-
Tomasz Wlostowski authored
-