On 10/07/2013 05:07 PM, H. Peter Anvin wrote: > Special soft IP presenting a PCI device to the host. ok. It means that you should need just different backend for this device which is able to communicate over PCI. I still can't see why this case should be problematic for this fpga manager. As Jason pointed if this is just about JTAG emulation and your data is in different format then you have to create your backend which will support this configuration. I will want to look at gpio jtag emulation to be able to program different board. We have this support for u-boot and doing in Linux should be also possible. I think the question is if we can live with 2/3 user interfaces. I tend to keep firmware one because it is covering a lot of common use cases and it can be easily to use. And then I don't have any preference if sysfs or char device is better. Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/ Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
Attachment:
signature.asc
Description: OpenPGP digital signature
