mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Moritz Fischer <moritz.fischer@ettus.com>, Alan Tull <atull@kernel.org>
Cc: "Michal Simek" <michal.simek@xilinx.com>,
	linux-fpga@vger.kernel.org,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] fpga: Add flag to indicate bitstream needs decrypting
Date: Wed, 15 Feb 2017 19:07:37 +0100	[thread overview]
Message-ID: <cc914f09-662a-e47d-d399-08036ee2e17c@xilinx.com> (raw)
In-Reply-To: <CAAtXAHfkiRYD68BRydFFd4OmdHaf9A+kmyOLkH0qNM8VL7G2Og@mail.gmail.com>

On 15.2.2017 19:02, Moritz Fischer wrote:
> On Wed, Feb 15, 2017 at 5:30 PM, Alan Tull <atull@kernel.org> wrote:
>> On Wed, Feb 15, 2017 at 9:03 AM, Michal Simek <michal.simek@xilinx.com> wrote:
> 
>>>>  #define FPGA_MGR_PARTIAL_RECONFIG    BIT(0)
>>>>  #define FPGA_MGR_EXTERNAL_CONFIG     BIT(1)
>>>> +#define FPGA_MGR_DECRYPT_BITSTREAM   BIT(2)
>>>>
>>>>  /**
>>>>   * struct fpga_image_info - information specific to a FPGA image
>>>>
>>>
>>> Isn't it better to state that bitstream is encrypted
>>> instead of saying that bitstream requires decryption?
>>
>> Such as FPGA_MGR_ENCRYPTED_BITSTREAM  ?
> 
> Yeah, can do. This was basically a 'redo' of my earlier 'capability' based
> patchset. There it made more sense to have a 'can decrypt' capability.

Just keep in your mind that there are use cases where you also need to
pass keys.

Thanks,
Michal

      reply	other threads:[~2017-02-15 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  0:31 mdf
2017-02-15  0:31 ` [PATCH 2/2] fpga: zynq: Add support for encrypted bitstreams mdf
2017-02-15 15:03 ` [PATCH 1/2] fpga: Add flag to indicate bitstream needs decrypting Michal Simek
2017-02-15 16:30   ` Alan Tull
2017-02-15 18:02     ` Moritz Fischer
2017-02-15 18:07       ` Michal Simek [this message]

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=cc914f09-662a-e47d-d399-08036ee2e17c@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=atull@kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moritz.fischer@ettus.com \
    --cc=soren.brinkmann@xilinx.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

Powered by JetHome