From: atull@opensource.altera.com (atull)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] fpga mgr: socfpga: Expose support for encrypted bitstreams
Date: Sun, 13 Nov 2016 16:37:20 -0600 [thread overview]
Message-ID: <alpine.DEB.2.10.1611131630510.2735@atull-VirtualBox> (raw)
In-Reply-To: <20161107001326.7395-5-moritz.fischer@ettus.com>
On Mon, 7 Nov 2016, Moritz Fischer wrote:
> Expose support for on the fly decryption of bitstreams.
> This needs no additional work or configuration,
> so just expose the new capability.
Hi Moritz,
When we talked about this, I was thinking about the arria10
support which I'd done more recently. c5 and a10 are
quite different here.
The c5 datasheet:
https://www.altera.com/literature/hb/cyclone-v/cv_5v4.pdf
Look for the 'stat' register on page 4-12 onwards. This
register exposes the setting of the msel pins (are a dipswitch
on some boards). The msel pins determine the programming
mode and whether it is expecting an encrypted and/or
compressed bitstream. So you could read this reg and
set the capabilities accordingly.
For arria10, encryption is enabled and if the bitstream
says it's encrypted, the driver handles it.
Alan
>
> Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
> Cc: Alan Tull <atull@opensource.altera.com>
> Cc: Michal Simek <michal.simek@xilinx.com>
> Cc: S?ren Brinkmann <soren.brinkmann@xilinx.com>
> Cc: linux-kernel at vger.kernel.org
> Cc: linux-arm-kernel at lists.infradead.org
> ---
>
> Alan,
>
> can you please let me know if that works this way, or where to find
> information on encrypted bitstreams? I have a CycloneV SoCFPGA to test
> on ...
>
> Cheers,
>
> Moritz
> ---
> drivers/fpga/socfpga.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/fpga/socfpga.c b/drivers/fpga/socfpga.c
> index fd9760c..ab57ec0c 100644
> --- a/drivers/fpga/socfpga.c
> +++ b/drivers/fpga/socfpga.c
> @@ -579,6 +579,7 @@ static int socfpga_fpga_probe(struct platform_device *pdev)
>
> fpga_mgr_cap_zero(&caps);
> fpga_mgr_cap_set(FPGA_MGR_CAP_FULL_RECONF, caps);
> + fpga_mgr_cap_set(FPGA_MGR_CAP_DECRYPT, caps);
>
> return fpga_mgr_register(dev, "Altera SOCFPGA FPGA Manager",
> &socfpga_fpga_ops, caps, priv);
> --
> 2.10.0
>
>
WARNING: multiple messages have this Message-ID (diff)
From: atull <atull@opensource.altera.com>
To: Moritz Fischer <moritz.fischer@ettus.com>
Cc: <linux-kernel@vger.kernel.org>,
<moritz.fischer.private@gmail.com>, <michal.simek@xilinx.com>,
<soren.brinkmann@xilinx.com>,
<linux-arm-kernel@lists.infradead.org>, <julia@ni.com>
Subject: Re: [PATCH 4/4] fpga mgr: socfpga: Expose support for encrypted bitstreams
Date: Sun, 13 Nov 2016 16:37:20 -0600 [thread overview]
Message-ID: <alpine.DEB.2.10.1611131630510.2735@atull-VirtualBox> (raw)
In-Reply-To: <20161107001326.7395-5-moritz.fischer@ettus.com>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On Mon, 7 Nov 2016, Moritz Fischer wrote:
> Expose support for on the fly decryption of bitstreams.
> This needs no additional work or configuration,
> so just expose the new capability.
Hi Moritz,
When we talked about this, I was thinking about the arria10
support which I'd done more recently. c5 and a10 are
quite different here.
The c5 datasheet:
https://www.altera.com/literature/hb/cyclone-v/cv_5v4.pdf
Look for the 'stat' register on page 4-12 onwards. This
register exposes the setting of the msel pins (are a dipswitch
on some boards). The msel pins determine the programming
mode and whether it is expecting an encrypted and/or
compressed bitstream. So you could read this reg and
set the capabilities accordingly.
For arria10, encryption is enabled and if the bitstream
says it's encrypted, the driver handles it.
Alan
>
> Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
> Cc: Alan Tull <atull@opensource.altera.com>
> Cc: Michal Simek <michal.simek@xilinx.com>
> Cc: Sören Brinkmann <soren.brinkmann@xilinx.com>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> ---
>
> Alan,
>
> can you please let me know if that works this way, or where to find
> information on encrypted bitstreams? I have a CycloneV SoCFPGA to test
> on ...
>
> Cheers,
>
> Moritz
> ---
> drivers/fpga/socfpga.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/fpga/socfpga.c b/drivers/fpga/socfpga.c
> index fd9760c..ab57ec0c 100644
> --- a/drivers/fpga/socfpga.c
> +++ b/drivers/fpga/socfpga.c
> @@ -579,6 +579,7 @@ static int socfpga_fpga_probe(struct platform_device *pdev)
>
> fpga_mgr_cap_zero(&caps);
> fpga_mgr_cap_set(FPGA_MGR_CAP_FULL_RECONF, caps);
> + fpga_mgr_cap_set(FPGA_MGR_CAP_DECRYPT, caps);
>
> return fpga_mgr_register(dev, "Altera SOCFPGA FPGA Manager",
> &socfpga_fpga_ops, caps, priv);
> --
> 2.10.0
>
>
next prev parent reply other threads:[~2016-11-13 22:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 0:13 [PATCH 0/4] fpga mgr: Add support for capabilities & encrypted bistreams Moritz Fischer
2016-11-07 0:13 ` Moritz Fischer
2016-11-07 0:13 ` [PATCH 1/4] fpga mgr: Introduce FPGA capabilities Moritz Fischer
2016-11-07 0:13 ` Moritz Fischer
2016-11-14 14:01 ` atull
2016-11-14 14:01 ` atull
2016-11-14 14:06 ` atull
2016-11-14 14:06 ` atull
2016-11-14 17:26 ` Moritz Fischer
2016-11-14 17:26 ` Moritz Fischer
2016-11-14 23:23 ` atull
2016-11-14 23:23 ` atull
2016-11-07 0:13 ` [PATCH 2/4] fpga mgr: Expose FPGA capabilities to userland via sysfs Moritz Fischer
2016-11-07 0:13 ` Moritz Fischer
2016-11-14 14:33 ` atull
2016-11-14 14:33 ` atull
2016-11-07 0:13 ` [PATCH 3/4] fpga mgr: zynq: Add support for encrypted bitstreams Moritz Fischer
2016-11-07 0:13 ` Moritz Fischer
2016-11-08 18:32 ` Sören Brinkmann
2016-11-08 18:32 ` Sören Brinkmann
2016-11-08 18:59 ` Moritz Fischer
2016-11-08 18:59 ` Moritz Fischer
2016-11-15 2:42 ` atull
2016-11-15 2:42 ` atull
2016-11-15 3:25 ` Moritz Fischer
2016-11-15 3:25 ` Moritz Fischer
2016-11-07 0:13 ` [PATCH 4/4] fpga mgr: socfpga: Expose " Moritz Fischer
2016-11-07 0:13 ` Moritz Fischer
2016-11-13 22:37 ` atull [this message]
2016-11-13 22:37 ` atull
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=alpine.DEB.2.10.1611131630510.2735@atull-VirtualBox \
--to=atull@opensource.altera.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.