From: Nishanth Menon <nm@ti.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: Tom Rini <trini@konsulko.com>, <u-boot@lists.denx.de>,
Vignesh Raghavendra <vigneshr@ti.com>, Kamlesh <kamlesh@ti.com>,
Vibhore Vardhan <vibhore@ti.com>,
Wadim Egorov <w.egorov@phytec.de>
Subject: Re: [PATCH 0/2] docs: AM62x: Remove SW_PRNG Flag for OPTEE
Date: Mon, 4 Dec 2023 13:30:31 -0600 [thread overview]
Message-ID: <20231204193031.57p64bitdb7agoh7@client> (raw)
In-Reply-To: <20231201102954.47582-1-d-gole@ti.com>
On 15:59-20231201, Dhruva Gole wrote:
> The CFG_WITH_SOFTWARE_PRNG option was needed once when there were some
> issues with system crashes/ hangs after a suspend-resume cycle. However
> this seems to no longer be the case with newer firmwares, and this
> config is not needed for basic boot support of the SoC either, hence
> remove it from the docs.
>
> Cc: Kamlesh <kamlesh@ti.com>
> Cc: Vibhore Vardhan <vibhore@ti.com>
> Cc: Wadim Egorov <w.egorov@phytec.de>
>
> Dhruva Gole (2):
> doc: board: beagle: am62x_beagleplay: Delete SW_PRNG flag for OPTEE
> doc: board: ti: am62x_sk: Remove SW_PRNG Flag for OPTEE
>
> doc/board/beagle/am62x_beagleplay.rst | 1 -
> doc/board/ti/am62x_sk.rst | 1 -
> 2 files changed, 2 deletions(-)
>
NAK to the series. RNG seed is needed for KASLR. either enable h/w RNG
or at least enable S/W RNG in OPTEE.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-12-04 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:29 [PATCH 0/2] docs: AM62x: Remove SW_PRNG Flag for OPTEE Dhruva Gole
2023-12-01 10:29 ` [PATCH 1/2] doc: board: beagle: am62x_beagleplay: Delete SW_PRNG flag " Dhruva Gole
2023-12-04 19:29 ` Nishanth Menon
2023-12-05 14:46 ` Andrew Davis
2023-12-05 15:22 ` Nishanth Menon
2023-12-05 16:38 ` Andrew Davis
2023-12-01 10:29 ` [PATCH 2/2] doc: board: ti: am62x_sk: Remove SW_PRNG Flag " Dhruva Gole
2023-12-04 19:30 ` Nishanth Menon [this message]
2023-12-05 5:27 ` [PATCH 0/2] docs: AM62x: " Dhruva Gole
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=20231204193031.57p64bitdb7agoh7@client \
--to=nm@ti.com \
--cc=d-gole@ti.com \
--cc=kamlesh@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vibhore@ti.com \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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.