Re: [PATCH v3 0/7] Introduction of a remoteproc tee to load signed firmware

2024-02-23 Thread Arnaud POULIQUEN
On 2/22/24 10:55, Naman Jain wrote: > On 2/22/2024 2:17 PM, Arnaud POULIQUEN wrote: >> Hello Naman, >> >> On 2/22/24 06:43, Naman Jain wrote: >>> On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: Updates from the previous version [1]: This version proposes another approach based on

Re: [PATCH v3 0/7] Introduction of a remoteproc tee to load signed firmware

2024-02-22 Thread Naman Jain
On 2/22/2024 2:17 PM, Arnaud POULIQUEN wrote: Hello Naman, On 2/22/24 06:43, Naman Jain wrote: On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: Updates from the previous version [1]: This version proposes another approach based on an alternate load and boot of the coprocessor. Therefore, the

Re: [PATCH v3 0/7] Introduction of a remoteproc tee to load signed firmware

2024-02-22 Thread Arnaud POULIQUEN
Hello Naman, On 2/22/24 06:43, Naman Jain wrote: > On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: >> Updates from the previous version [1]: >> >> This version proposes another approach based on an alternate load and boot >> of the coprocessor. Therefore, the constraint introduced by

Re: [PATCH v3 0/7] Introduction of a remoteproc tee to load signed firmware

2024-02-21 Thread Naman Jain
On 2/14/2024 10:51 PM, Arnaud Pouliquen wrote: Updates from the previous version [1]: This version proposes another approach based on an alternate load and boot of the coprocessor. Therefore, the constraint introduced by tee_remoteproc is that the firmware has to be authenticated and loaded

[PATCH v3 0/7] Introduction of a remoteproc tee to load signed firmware

2024-02-14 Thread Arnaud Pouliquen
Updates from the previous version [1]: This version proposes another approach based on an alternate load and boot of the coprocessor. Therefore, the constraint introduced by tee_remoteproc is that the firmware has to be authenticated and loaded before the resource table can be obtained. The