Hi Geert,
> > That would not work with kernel freezes unfortunately. Debugging those with
> > nondeterministicly invisible kernel prints would be painful, I believe.
>
> Unfortunately AFAIK the PS3 doesn't have any other "synchronous" output we
> can use for debugging (like flashing the power
Hi Fredrik,
On Thu, Jul 19, 2018 at 10:14 PM Fredrik Noring wrote:
> > > > so I added a sleep with
> > > >
> > > > + msleep(1);
> >
> > I can't see where you added the sleep, but 10s seems excessive.
> > If the real reason is the need to wait for an interrupt for
> > ps3fb_sync_image(),
Hi Geert, Geoff,
> > > so I added a sleep with
> > >
> > > + msleep(1);
>
> I can't see where you added the sleep, but 10s seems excessive.
> If the real reason is the need to wait for an interrupt for
> ps3fb_sync_image(),
> then waiting for 40 ms should be sufficient? Or am I missing
Hi Geert, Fredrik,
On 07/19/2018 12:45 AM, Geert Uytterhoeven wrote:
>> On 07/14/2018 09:49 AM, Fredrik Noring wrote:
>>>
>>> et voilà, the screen came alive and the kernel panic was revealed! It seems
>>> the kernel panics so fast that the PS3 frame buffer is unprepared. This is,
>>> of course,
Hi Geoff, Frederik,
On Thu, Jul 19, 2018 at 12:40 AM Geoff Levand wrote:
> On 07/14/2018 09:49 AM, Fredrik Noring wrote:
> > so I added a sleep with
> >
> > + msleep(1);
I can't see where you added the sleep, but 10s seems excessive.
If the real reason is the need to wait for an
Hi Fredrik,
On 07/14/2018 09:49 AM, Fredrik Noring wrote:
> so I added a sleep with
>
> + msleep(1);
> +
> return 0;
>
> et voilà, the screen came alive and the kernel panic was revealed! It seems
> the kernel panics so fast that the PS3 frame buffer is unprepared. This is,
> of
