Messages in this thread | | | From | Florian Fainelli <> | Subject | Re: FPGA programming driver architecture | Date | Thu, 8 Jan 2009 23:57:21 +0100 |
| |
Hello,
Le Thursday 08 January 2009 23:47:58 Leon Woestenberg, vous avez écrit : > Indeed. > > The programming back end should be generic enough so that it can use > other subsystems. > > The FPGA configuration interface could be on the memory bus (and in > many cases the DMA helpers can be used) or behind a PCI bus, or can > even have SPI etc front-ends. > > In general the programming API should accept a blob of data, > preferably in one chunk (pointer plus length) or at least 4kB chunks > or so, so that configuration is not severy overheaded by a callback > per byte (or even bit).
That's the idea behind using request_firmware, which provides you with both a pointer to the data and the size of the blob. -- Best regards, Florian Fainelli Email : florian@openwrt.org http://openwrt.org ------------------------------- [unhandled content-type:application/pgp-signature] | |