Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] tpm2-tss: new package
Date: Wed, 14 Mar 2018 13:29:09 -0300 (BRT)	[thread overview]
Message-ID: <1938724924.1859970.1521044949745.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <87r2oscocc.fsf@dell.be.48ers.dk>

> From: "Peter Korsgaard" <peter@korsgaard.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>, "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> Cc: "buildroot" <buildroot@buildroot.org>
> Sent: Saturday, March 10, 2018 5:43:47 AM
> Subject: Re: [git commit] tpm2-tss: new package

>>>>>> "Carlos" == Carlos Santos <casantos@datacom.ind.br> writes:
> 
> >> Thomas asked on IRC why this was x86 only. Can you explain why?
> 
> > Because it needs a hardware TPM, which as far as I know is available
> > only in some Intel processors (I tested it in a C3000 SOC).
> 
> Aren't TPM2 devices still available as small microcontrollers connected
> to the main processor over i2c/spi? I've seen ARM boards with such
> TPM1.2 devices, and I think Thomas mentioned an ARM board with a TPM2
> device connected over SPI.
> 
> In general, unless there is a build time dependency on architecture
> specific files or the package is very specific to a SoC or board I
> prefer to not hide packages, even if it is unlikely to be used on other
> architectures.
> 
> So I think we should remove the dependencies from tpm2-tss.

I agree.

-- 
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent 
success of having your words and actions judged by your reputation, 
rather than the other way about.? ? Christopher Hitchens

      reply	other threads:[~2018-03-14 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08  8:58 [Buildroot] [git commit] tpm2-tss: new package Peter Korsgaard
2018-03-08 19:53 ` Carlos Santos
2018-03-09 21:26   ` Peter Korsgaard
2018-03-10  1:09     ` Carlos Santos
2018-03-10  8:43       ` Peter Korsgaard
2018-03-14 16:29         ` Carlos Santos [this message]

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=1938724924.1859970.1521044949745.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --cc=buildroot@busybox.net \
    /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