Hi Heiko,
> Hello Lukasz,
>
> Am 22.02.2018 um 14:03 schrieb Lukasz Majewski:
> > Hi Stefano,
> >
> >> Hi Lukasz,
> >>
> >> On 22/02/2018 12:52, Lukasz Majewski wrote:
> >>> Hi Stefano,
> >>>
> If the bootcounter address is in a cached memory,
> a flush of dcache must occur
Hello Lukasz,
Am 22.02.2018 um 14:03 schrieb Lukasz Majewski:
Hi Stefano,
Hi Lukasz,
On 22/02/2018 12:52, Lukasz Majewski wrote:
Hi Stefano,
If the bootcounter address is in a cached memory,
a flush of dcache must occur after updateing the bootcounter.
Issue found on i.MX6 where
Hi Stefano,
> Hi Lukasz,
>
> On 22/02/2018 12:52, Lukasz Majewski wrote:
> > Hi Stefano,
> >
> >> If the bootcounter address is in a cached memory,
> >> a flush of dcache must occur after updateing the bootcounter.
> >>
> >> Issue found on i.MX6 where bootcounter is put into the internal
> >>
Hi Lukasz,
On 22/02/2018 12:52, Lukasz Majewski wrote:
> Hi Stefano,
>
>> If the bootcounter address is in a cached memory,
>> a flush of dcache must occur after updateing the bootcounter.
>>
>> Issue found on i.MX6 where bootcounter is put into the internal
>> (cached) IRAM.
>>
>>
Hi Stefano,
> If the bootcounter address is in a cached memory,
> a flush of dcache must occur after updateing the bootcounter.
>
> Issue found on i.MX6 where bootcounter is put into the internal
> (cached) IRAM.
>
> Signed-off-by: Stefano Babic
> ---
>
If the bootcounter address is in a cached memory,
a flush of dcache must occur after updateing the bootcounter.
Issue found on i.MX6 where bootcounter is put into the internal
(cached) IRAM.
Signed-off-by: Stefano Babic
---
drivers/bootcount/bootcount.c | 3 +++
1 file changed,
6 matches
Mail list logo