Hi Boris,
> Boris Brezillon hat am 7. Mai 2018 um 09:11
> geschrieben:
>
>
> On Sun, 6 May 2018 01:56:36 +0200 (CEST)
> Stefan Wahren wrote:
>
> > > Boris Brezillon hat am 5. Mai 2018 um 20:00
> > > geschrieben:
> > >
> > >
> > > On Sat, 5 May 2018 19:44:57 +0200 (CEST)
> > > Stefan Wahr
On Sun, 6 May 2018 01:56:36 +0200 (CEST)
Stefan Wahren wrote:
> > Boris Brezillon hat am 5. Mai 2018 um 20:00
> > geschrieben:
> >
> >
> > On Sat, 5 May 2018 19:44:57 +0200 (CEST)
> > Stefan Wahren wrote:
> >
> > > Hi Stefan,
> > >
> > > > Stefan Schake hat am 5. Mai 2018 um 19:29
> >
> Boris Brezillon hat am 5. Mai 2018 um 20:00
> geschrieben:
>
>
> On Sat, 5 May 2018 19:44:57 +0200 (CEST)
> Stefan Wahren wrote:
>
> > Hi Stefan,
> >
> > > Stefan Schake hat am 5. Mai 2018 um 19:29
> > > geschrieben:
> > >
> > >
> > > On Sat, May 5, 2018 at 1:47 PM, Stefan Wahren
> > >
Hi,
after submit of the latest bcm2835 clock fixes, i thought this issue has been
fixed. But i've seen this issue with current mainline 4.17-rc3
(bcm2835_defconfig) on Raspberry Pi 1 B (using U-Boot TFTP Boot). Strangly i
couldn't reproduce this issue with same kernel but using only the Foundat
Hi Stefan,
> Stefan Schake hat am 5. Mai 2018 um 19:29 geschrieben:
>
>
> On Sat, May 5, 2018 at 1:47 PM, Stefan Wahren wrote:
> > Hi,
> >
> > after submit of the latest bcm2835 clock fixes, i thought this issue has
> > been fixed. But i've seen this issue with current mainline 4.17-rc3
> >
Hi Boris,
> Boris Brezillon hat am 5. Mai 2018 um 14:24
> geschrieben:
>
>
> On Sat, 5 May 2018 13:47:25 +0200 (CEST)
> Stefan Wahren wrote:
>
> > Hi,
> >
> > after submit of the latest bcm2835 clock fixes, i thought this issue has
> > been fixed. But i've seen this issue with current main
On Sat, 5 May 2018 19:44:57 +0200 (CEST)
Stefan Wahren wrote:
> Hi Stefan,
>
> > Stefan Schake hat am 5. Mai 2018 um 19:29
> > geschrieben:
> >
> >
> > On Sat, May 5, 2018 at 1:47 PM, Stefan Wahren
> > wrote:
> > > Hi,
> > >
> > > after submit of the latest bcm2835 clock fixes, i thought t
On Sat, May 5, 2018 at 1:47 PM, Stefan Wahren wrote:
> Hi,
>
> after submit of the latest bcm2835 clock fixes, i thought this issue has been
> fixed. But i've seen this issue with current mainline 4.17-rc3
> (bcm2835_defconfig) on Raspberry Pi 1 B (using U-Boot TFTP Boot). Strangly i
> couldn't
On Sat, 5 May 2018 13:47:25 +0200 (CEST)
Stefan Wahren wrote:
> Hi,
>
> after submit of the latest bcm2835 clock fixes, i thought this issue has been
> fixed. But i've seen this issue with current mainline 4.17-rc3
> (bcm2835_defconfig) on Raspberry Pi 1 B (using U-Boot TFTP Boot). Strangly i