On Thu, 1 Aug 2019 at 14:00, Janne Karhunen wrote:
>
> On Thu, Aug 1, 2019 at 10:58 AM Sumit Garg wrote:
>
> > > Anyway, just my .02c. I guess having any new support in the kernel for
> > > new trust sources is good and improvement from the current state. I
> > > can certainly make my stuff work
On Thu, Aug 1, 2019 at 10:58 AM Sumit Garg wrote:
> > Anyway, just my .02c. I guess having any new support in the kernel for
> > new trust sources is good and improvement from the current state. I
> > can certainly make my stuff work with your setup as well, what ever
> > people think is the best
On Thu, 1 Aug 2019 at 13:00, Janne Karhunen wrote:
>
> On Thu, Aug 1, 2019 at 9:50 AM Rouven Czerwinski
> wrote:
>
> > > I'm aware of it - I have implemented a large part of the GP TEE APIs
> > > earlier (primarily the crypto functions). Does the TEE you work with
> > > actually support GP proper
On Thu, Aug 1, 2019 at 9:50 AM Rouven Czerwinski
wrote:
> > I'm aware of it - I have implemented a large part of the GP TEE APIs
> > earlier (primarily the crypto functions). Does the TEE you work with
> > actually support GP properly? Can I take a look at the code?
>
> AFAIK Sumit is working wit
On Thu, 2019-08-01 at 09:36 +0300, Janne Karhunen wrote:
> On Wed, Jul 31, 2019 at 5:23 PM Sumit Garg
> wrote:
>
> > > I guess my wording was wrong, tried to say that physical TEEs in
> > > the
> > > wild vary massively hardware wise. Generalizing these things is
> > > rough.
> > >
> >
> > Ther