From: Markku Savela <msa@moth.iki.fi>
To: Mimi Zohar <zohar@linux.ibm.com>, linux-integrity@vger.kernel.org
Cc: "Peter Hüwe" <PeterHuewe@gmx.de>
Subject: Re: IMA fails to see TPM chip (rpi3, linaro optee)
Date: Thu, 21 Feb 2019 15:23:57 +0200 [thread overview]
Message-ID: <88215b47-976c-96d5-1098-40868d28d576@moth.iki.fi> (raw)
In-Reply-To: <776f0386-6c4d-9ad4-929c-44ba9fd4c9d0@moth.iki.fi>
On 21/02/2019 15:17, Markku Savela wrote:
>
>> Right, for rpi-4.14.y kernel, reverting commit acddd39 ("clk-bcm2835:
>> Read max core clock from firmware") allows the TPM to be initialized
>> prior to IMA, but is probably not the right solution.
>
> .. I'm not able to find this commit from linaro git (I don't know what
> command to use...).
...that is, the "obvious" one fails to produce anything usefull...
git show acddd39
fatal: ambiguous argument 'acddd39': unknown revision or path not in the
working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
...and have no idea how to fix it.
next prev parent reply other threads:[~2019-02-21 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 9:36 IMA fails to see TPM chip (rpi3, linaro optee) Markku Savela
2019-02-18 10:13 ` Markku Savela
2019-02-20 8:14 ` Markku Savela
2019-02-21 9:08 ` Markku Savela
2019-02-21 12:49 ` Mimi Zohar
2019-02-21 13:17 ` Markku Savela
2019-02-21 13:23 ` Markku Savela [this message]
2019-02-26 8:12 ` Markku Savela
2019-02-26 12:14 ` Mimi Zohar
2019-02-26 12:38 ` Ard Biesheuvel
2019-02-26 14:04 ` Mimi Zohar
2019-02-26 18:09 ` Jarkko Sakkinen
2019-02-26 19:05 ` Mimi Zohar
2019-03-07 17:15 ` James Bottomley
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=88215b47-976c-96d5-1098-40868d28d576@moth.iki.fi \
--to=msa@moth.iki.fi \
--cc=PeterHuewe@gmx.de \
--cc=linux-integrity@vger.kernel.org \
--cc=zohar@linux.ibm.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).