Hi Jan,
On Sun, 12 Feb 2023 at 22:33, Jan Kiszka wrote:
>
> On 13.02.23 05:26, Simon Glass wrote:
> > Hi Jan,
> >
> > On Tue, 7 Feb 2023 at 11:39, Simon Glass wrote:
> >>
> >> Hi Jan,
> >>
> >> On Tue, 7 Feb 2023 at 09:45, Jan Kiszka wrote:
> >>>
> >>> On 07.02.23 16:28, Simon Glass wrote:
> >>
On 13.02.23 05:26, Simon Glass wrote:
> Hi Jan,
>
> On Tue, 7 Feb 2023 at 11:39, Simon Glass wrote:
>>
>> Hi Jan,
>>
>> On Tue, 7 Feb 2023 at 09:45, Jan Kiszka wrote:
>>>
>>> On 07.02.23 16:28, Simon Glass wrote:
Hi Jan,
On Mon, 6 Feb 2023 at 04:57, Jan Kiszka wrote:
>
>
Hi Jan,
On Tue, 7 Feb 2023 at 11:39, Simon Glass wrote:
>
> Hi Jan,
>
> On Tue, 7 Feb 2023 at 09:45, Jan Kiszka wrote:
> >
> > On 07.02.23 16:28, Simon Glass wrote:
> > > Hi Jan,
> > >
> > > On Mon, 6 Feb 2023 at 04:57, Jan Kiszka wrote:
> > >>
> > >> On 06.02.23 11:47, Jan Kiszka wrote:
> > >>
Hi Jan,
On Tue, 7 Feb 2023 at 09:45, Jan Kiszka wrote:
>
> On 07.02.23 16:28, Simon Glass wrote:
> > Hi Jan,
> >
> > On Mon, 6 Feb 2023 at 04:57, Jan Kiszka wrote:
> >>
> >> On 06.02.23 11:47, Jan Kiszka wrote:
> >>> On 04.02.23 23:26, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 3 Fe
On 07.02.23 16:28, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 6 Feb 2023 at 04:57, Jan Kiszka wrote:
>>
>> On 06.02.23 11:47, Jan Kiszka wrote:
>>> On 04.02.23 23:26, Simon Glass wrote:
Hi Jan,
On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>
> On 03.02.23 19:51, Tom Rini wr
Hi Jan,
On Mon, 6 Feb 2023 at 04:57, Jan Kiszka wrote:
>
> On 06.02.23 11:47, Jan Kiszka wrote:
> > On 04.02.23 23:26, Simon Glass wrote:
> >> Hi Jan,
> >>
> >> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
> >>>
> >>> On 03.02.23 19:51, Tom Rini wrote:
> On Fri, Feb 03, 2023 at 01:26:37PM
On 06.02.23 11:47, Jan Kiszka wrote:
> On 04.02.23 23:26, Simon Glass wrote:
>> Hi Jan,
>>
>> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>>
>>> On 03.02.23 19:51, Tom Rini wrote:
On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka
>
> There ar
On 04.02.23 23:26, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>
>> On 03.02.23 19:51, Tom Rini wrote:
>>> On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
>>>
From: Jan Kiszka
There are many ways to get a signed firmware for the IOT
Hi Jan,
On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>
> On 03.02.23 19:51, Tom Rini wrote:
> > On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
> >
> >> From: Jan Kiszka
> >>
> >> There are many ways to get a signed firmware for the IOT2050 devices,
> >> namely for the parts under
On Sat, Feb 04, 2023 at 07:34:46AM +0100, Jan Kiszka wrote:
> On 03.02.23 19:51, Tom Rini wrote:
> > On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
> >
> >> From: Jan Kiszka
> >>
> >> There are many ways to get a signed firmware for the IOT2050 devices,
> >> namely for the parts unde
On 03.02.23 19:51, Tom Rini wrote:
> On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
>
>> From: Jan Kiszka
>>
>> There are many ways to get a signed firmware for the IOT2050 devices,
>> namely for the parts under user-control. This script documents one way
>> of doing it, given a sign
On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka
>
> There are many ways to get a signed firmware for the IOT2050 devices,
> namely for the parts under user-control. This script documents one way
> of doing it, given a signing key. Augment the board documentation wi
From: Jan Kiszka
There are many ways to get a signed firmware for the IOT2050 devices,
namely for the parts under user-control. This script documents one way
of doing it, given a signing key. Augment the board documentation with
the required procedure around it.
Signed-off-by: Jan Kiszka
---
d
13 matches
Mail list logo