summaryrefslogtreecommitdiff
path: root/include/linux/fpga
diff options
context:
space:
mode:
authorJason Gunthorpe <jgunthorpe@obsidianresearch.com>2017-02-01 22:48:43 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-02-10 17:20:44 +0300
commitb496df86ac1bbe393a55ddbfed35d46e74ef9767 (patch)
tree0f87f727e68acab692280c556f6376237a68c64a /include/linux/fpga
parent6b45e0f24c7b5316dea7ed5995e1b809a3266b43 (diff)
downloadlinux-b496df86ac1bbe393a55ddbfed35d46e74ef9767.tar.xz
fpga zynq: Check the bitstream for validity
There is no sense in sending a bitstream we know will not work, and with the variety of options for bitstream generation in Xilinx tools it is not terribly clear what the correct input should be. This is particularly important for Zynq since auto-correction was removed from the driver and the Zynq hardware only accepts a bitstream format that is different from what the Xilinx tools typically produce. Worse, the hardware provides no indication why the bitstream fails, it simply times out if the input is wrong. The best option here is to have the kernel print a message informing the user they are using a malformed bistream and programming failure isn't for any of the myriad of other reasons. Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> Acked-by: Moritz Fischer <moritz.fischer@ettus.com> Acked-by: Alan Tull <atull@opensource.altera.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/linux/fpga')
0 files changed, 0 insertions, 0 deletions