From mboxrd@z Thu Jan  1 00:00:00 1970
From: Florian Fainelli <florian@openwrt.org>
Subject: Re: FPGA programming driver architecture
Date: Thu, 8 Jan 2009 23:57:21 +0100
Message-ID: <200901082357.24432.florian@openwrt.org>
References: <20081212150314.6ea24996.hugo@hugovil.com> <82ecf08e0901081414u15af3c2dy9c88a242db024dc7@mail.gmail.com> <c384c5ea0901081447i5ad807b3yb0ec3adebeaa46a0@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1407056.eZfqosaT1b";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Return-path: <linux-embedded-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:sender:from:to:subject:date
         :user-agent:cc:references:in-reply-to:mime-version:content-type
         :content-transfer-encoding:message-id;
        bh=a4LLlRq2WagW7/GSq0qo/bjWUV7ok5qgKBRwlXSZHKY=;
        b=fEnh+/fL99n+zgPz1yOiJIZkHPVGC3yQfzUnng4pTJhYtUCE+pTJbqaUxlreBJAmnB
         SVvoC0iA29AmtjLm5DTuSMOfRaybsCIwNLTMF1qbpCdy6AnfAD8TISVrg20XlGVkzMVF
         aEkhSWqyimE6LZsXQKYsk/C7z5OmjlA7vRfMg=
In-Reply-To: <c384c5ea0901081447i5ad807b3yb0ec3adebeaa46a0@mail.gmail.com>
Sender: linux-embedded-owner@vger.kernel.org
List-ID: <linux-embedded.vger.kernel.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

--nextPart1407056.eZfqosaT1b
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello,

Le Thursday 08 January 2009 23:47:58 Leon Woestenberg, vous avez =E9crit=A0:
> 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=20
pointer to the data and the size of the blob.
=2D-=20
Best regards, Florian Fainelli
Email : florian@openwrt.org
http://openwrt.org
=2D------------------------------

--nextPart1407056.eZfqosaT1b
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAklmhNIACgkQlyvkmBGtjyZVwgCfRdq0d7DUxbQLSm1+jqHTBbNg
x4wAoLRizBd5SyVIt+Ch3utQBXAOYSCr
=JyIa
-----END PGP SIGNATURE-----

--nextPart1407056.eZfqosaT1b--