From: Denis Osterland-Heim <denis.osterland@diehl.com>
To: "sha@pengutronix.de" <sha@pengutronix.de>
Cc: "r.czerwinski@pengutronix.de" <r.czerwinski@pengutronix.de>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] nvmem: ocotp: add support to revoke keys
Date: Tue, 16 Mar 2021 08:03:01 +0000 [thread overview]
Message-ID: <6005b0a0b4ac43ef1955de68612039e8e9451117.camel@diehl.com> (raw)
In-Reply-To: <20210315080437.GF23724@pengutronix.de>
Hi Sascha,
Am Montag, den 15.03.2021, 09:04 +0100 schrieb Sascha Hauer:
> Hi Denis,
>
> On Fri, Mar 12, 2021 at 02:39:40PM +0000, Denis Osterland-Heim wrote:
> > Hi,
> >
> > It would be no problem to do it in a script.
> > I did it as a fist prove of concept.
> > My opinion is, that this hard coded implementation give stronger
> > guarantee that this code is really executed.
>
> You could also create a C function which you call from your board code.
good Idea
>
> >
> > I would love to implement the HAB to check FIT signatures,
> > but with MMU enabled it will not work AFAIK and code requiring MMU disabled is not welcome.
>
> Are you sure it doesn't work? What I know is that the jump table for the
> HAB function is placed in the zero page which is set to faulting
> normally when the MMU is enabled. If that's the only problem we could
> solve that.
I would like to give it a try.
enable CONFIG_ARCH_HAS_ZERO_PAGE
zero_page_access();
pvt->some_function();
zero_page_faulting();
right?
Regards, Denis
>
> Sascha
>
>
Diehl Connectivity Solutions GmbH
Geschäftsführung: Horst Leonberger
Sitz der Gesellschaft: Nürnberg - Registergericht: Amtsgericht
Nürnberg: HRB 32315
________________________________
Der Inhalt der vorstehenden E-Mail ist nicht rechtlich bindend. Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Informieren Sie uns bitte, wenn Sie diese E-Mail faelschlicherweise erhalten haben. Bitte loeschen Sie in diesem Fall die Nachricht.
Jede unerlaubte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt.
- Informationen zum Datenschutz, insbesondere zu Ihren Rechten, erhalten Sie unter:
https://www.diehl.com/group/de/transparenz-und-informationspflichten/
The contents of the above mentioned e-mail is not legally binding. This e-mail contains confidential and/or legally protected information. Please inform us if you have received this e-mail by
mistake and delete it in such a case. Each unauthorized reproduction, disclosure, alteration, distribution and/or publication of this e-mail is strictly prohibited.
- For general information on data protection and your respective rights please visit:
https://www.diehl.com/group/en/transparency-and-information-obligations/
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-03-16 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:07 Denis Osterland-Heim
2021-03-12 10:15 ` Rouven Czerwinski
2021-03-12 14:39 ` Denis Osterland-Heim
2021-03-15 8:04 ` Sascha Hauer
2021-03-16 8:03 ` Denis Osterland-Heim [this message]
2021-03-16 8:11 ` sha
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=6005b0a0b4ac43ef1955de68612039e8e9451117.camel@diehl.com \
--to=denis.osterland@diehl.com \
--cc=barebox@lists.infradead.org \
--cc=r.czerwinski@pengutronix.de \
--cc=sha@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox