linux-kernel - Re: FPGA programming driver architecture

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200901082357.24432.florian@openwrt.org>
Date:	Thu, 8 Jan 2009 23:57:21 +0100
From:	Florian Fainelli <florian@...nwrt.org>
To:	"Leon Woestenberg" <leon.woestenberg@...il.com>
Cc:	"Thiago Galesi" <thiagogalesi@...il.com>,
	"Hugo Villeneuve" <hugo@...ovil.com>, linux-kernel@...r.kernel.org,
	linux-embedded@...r.kernel.org
Subject: Re: FPGA programming driver architecture

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@...nwrt.org
http://openwrt.org
-------------------------------

Download attachment "signature.asc " of type "application/pgp-signature" (198 bytes)