From: Richard Gong <richard.gong@linux.intel.com>
To: Moritz Fischer <mdf@kernel.org>
Cc: gregkh@linuxfoundation.org, trix@redhat.com,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
dinguyen@kernel.org, sridhar.rajagopal@intel.com,
richard.gong@intel.com
Subject: Re: [PATCHv2 1/5] firmware: stratix10-svc: add COMMAND_AUTHENTICATE_BITSTREAM flag
Date: Tue, 1 Dec 2020 14:52:11 -0600 [thread overview]
Message-ID: <48b61d87-331a-6dba-212e-8b6748429afe@linux.intel.com> (raw)
In-Reply-To: <X8aXNKNIPl+piFO+@archbook>
Hi Moritz,
On 12/1/20 1:19 PM, Moritz Fischer wrote:
> Hi Richard,
>
> On Tue, Dec 01, 2020 at 01:30:16PM -0600, Richard Gong wrote:
>
>>> Can U-Boot determine whether it's the new or old flow? Can you set a
>>> different compatible value in your device-tree, to disambiguate
>>> behaviors?
>>>
>>
>> The boot flow is determined by defconfig during compilation, which means
>> each boot flow will have its own defconfig.
>>
>> SDM firmware loads SPL into OCRAM, then SPL will load the apporiate ATF or
>> U-boot into the DRAM according to the setting of CONFIG_SPL_ATF. If
>> CONFIG_SPL_ATF=y, SPL loads ATF and then jumps to ATF. ATF setups EL3
>> environment and initialize the PSCI services.
>>
>> CONFIG_SPL_ATF is not set for the old boot flow.
>
> So you know at (U-Boot) build time? Can you just pass a different DT to
> the kernel in that case?
>
Yes, we have decided the boot flow at build time. Starting from the next
release, our U-boot will use the ATF boot flow.
Per my limited knowledge in U-boot, I don't think we can follow your
suggestion. Or it will take a lot of efforts to achieve.
I think that back compatibility is your main concern, correct? the issue
does exist with the old boot flow and old firmware, whenever the
customers try to use authentication. Unfortunately we can't update
U-boot or firmware that has been released.
The authentication feature is supported only at the ATF boot flow,
updated kernel and firmware. We will have a well-documented document to
inform our customers that if they want to have authentication feature,
they need to upgrade the latest U-boot, kernel and firmware.
We always encourage our customers to take the latest U-boot, kernel and
firmware releases in their developments.
> - Moritz
>
Regards,
Richard
next prev parent reply other threads:[~2020-12-01 20:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 14:29 [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region richard.gong
2020-11-18 14:29 ` [PATCHv2 1/5] firmware: stratix10-svc: add COMMAND_AUTHENTICATE_BITSTREAM flag richard.gong
2020-11-18 15:30 ` Moritz Fischer
2020-11-18 18:16 ` Richard Gong
2020-11-22 1:10 ` Moritz Fischer
2020-11-30 18:55 ` Richard Gong
2020-12-01 4:31 ` Moritz Fischer
2020-12-01 19:30 ` Richard Gong
2020-12-01 19:19 ` Moritz Fischer
2020-12-01 20:52 ` Richard Gong [this message]
2020-11-18 14:29 ` [PATCHv2 2/5] fpga: fpga-mgr: add FPGA_MGR_BITSTREM_AUTHENTICATION flag richard.gong
2020-11-18 14:29 ` [PATCHv2 3/5] fpga: of-fpga-region: add authenticate-fpga-config property richard.gong
2020-11-18 14:29 ` [PATCHv2 4/5] dt-bindings: fpga: " richard.gong
2020-11-18 14:29 ` [PATCHv2 5/5] fpga: stratix10-soc: extend driver for bitstream authentication richard.gong
2020-12-14 14:03 ` [PATCHv2 0/5] Extend Intel service layer, FPGA manager and region Richard Gong
2020-12-14 14:05 ` Greg KH
2020-12-14 14:43 ` Richard Gong
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=48b61d87-331a-6dba-212e-8b6748429afe@linux.intel.com \
--to=richard.gong@linux.intel.com \
--cc=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=richard.gong@intel.com \
--cc=sridhar.rajagopal@intel.com \
--cc=trix@redhat.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;
as well as URLs for NNTP newsgroup(s).