TPM2 (Trusted Platform Module) userspace development
 help / color / mirror / Atom feed
From: Duncan.Palmer at data61.csiro.au
To: tpm2@lists.01.org
Subject: Re: [tpm2] NVRAM_write, BUFFER_SIZE is 0
Date: Tue, 24 Apr 2018 12:51:49 +0000	[thread overview]
Message-ID: <1524574309106.7317@data61.csiro.au> (raw)
In-Reply-To: 6594cb44-a95c-f40d-6d20-8e784f9c13c1@intel.com

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Done. I hadn't submitted a pull request before as I was unsure whether this issue was related to the TPM I'm using (which doesn't seem commonly used), or more generally applicable.

Duncan Palmer
Senior Software Engineer | Autonomous Systems
Data61 | CSIRO
E duncan.palmer(a)csiro.au
Queensland Centre for Advanced Technologies (QCAT),
1 Technology Court, Pullenvale QLD, 4069
www.data61.csiro.au

CSIRO’s Digital Productivity business unit and NICTA have joined forces to create digital powerhouse Data61

________________________________________
From: Tadeusz Struk <tadeusz.struk(a)intel.com>
Sent: 19 April 2018 04:17
To: Palmer, Duncan (Data61, Pullenvale); ian.justin.oliver(a)gmail.com; tpm2(a)lists.01.org
Subject: Re: [tpm2] NVRAM_write, BUFFER_SIZE is 0

On 04/17/2018 03:24 PM, Duncan.Palmer(a)data61.csiro.au wrote:
> We see the same behaviour on an Intel NUC5i7. I haven't looked at the capabilities reported by the TPM device on that platform. The attached patch (setting max_data_size = MAX_NV_BUFFER_SIZE when max_data_size is reported as 0), sorts the problem out.
>

Hi Duncan,
Could you please send a Pull Request with your fix to the tools repo.

Thanks,
--
Tadeusz


             reply	other threads:[~2018-04-24 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 12:51 Duncan.Palmer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-30 18:12 [tpm2] NVRAM_write, BUFFER_SIZE is 0 Roberts, William C
2018-04-26 22:15 Duncan.Palmer
2018-04-25 17:02 Ian Oliver
2018-04-25 16:29 Roberts, William C
2018-04-24 14:47 Ian Oliver
2018-04-18 18:17 Tadeusz Struk
2018-04-18  8:07 Ian Oliver
2018-04-17 22:24 Duncan.Palmer
2018-04-17 11:10 Ian Oliver

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=1524574309106.7317@data61.csiro.au \
    --to=tpm2@lists.01.org \
    /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