From: Florian Fainelli <florian@openwrt.org>
To: "Leon Woestenberg" <leon.woestenberg@gmail.com>
Cc: "Thiago Galesi" <thiagogalesi@gmail.com>,
"Hugo Villeneuve" <hugo@hugovil.com>,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org
Subject: Re: FPGA programming driver architecture
Date: Thu, 8 Jan 2009 23:57:21 +0100 [thread overview]
Message-ID: <200901082357.24432.florian@openwrt.org> (raw)
In-Reply-To: <c384c5ea0901081447i5ad807b3yb0ec3adebeaa46a0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
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
-------------------------------
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-08 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 20:03 FPGA programming driver architecture Hugo Villeneuve
2008-12-13 12:58 ` Florian Fainelli
2008-12-15 18:16 ` Hugo Villeneuve
2009-01-08 20:18 ` Hugo Villeneuve
2009-01-08 22:14 ` Thiago Galesi
2009-01-08 22:47 ` Leon Woestenberg
2009-01-08 22:57 ` Florian Fainelli [this message]
2009-01-08 23:07 ` Leon Woestenberg
2009-01-09 3:14 ` Duane Ellis
2009-01-09 12:24 ` Alexander Clouter
2009-01-09 15:07 ` Hugo Villeneuve
2009-01-09 23:40 ` Hans J. Koch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200901082357.24432.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=hugo@hugovil.com \
--cc=leon.woestenberg@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thiagogalesi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox