Re: [tegrarcm PATCH v1 2/4] Add option --ml_rcm <rcm_ml_blob>

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/08/2016 06:21 PM, Jimmy Zhang wrote:
Stephen Warren wrote at Monday, March 07, 2016 12:16 PM:
On 03/04/2016 04:44 PM, Jimmy Zhang wrote:
This option along with "--pkc <keyfile>" allows user to generate
signed query version rcm, miniloader rcm and signed bootloader
(flasher). With these signed blob, user will then be able to run
tegrarcm on a fused system without keyfile.

That says "without keyfile", yet ...

Andrew helped me updating commit messages as below:

This option along with "--pkc <keyfile>" allows user to generate
signed query version rcm, miniloader rcm and signed bootloader
  (flasher). With the signed blob, user will then be able to later run
tegrarcm on a fused system without needing the actual keyfile.

I'd suggest just the following; that uses "signed blob" without actually mentioning that any such thing exists.

This feature allows generation of a signed blob that can later be used to communicate with a PKC-enabled Tegra device without access to the PKC. The --pkc option is required when generating the blob.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [ARM Kernel]     [Linux ARM]     [Linux ARM MSM]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux