[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 00/19] hw/arm/raspi: Improve Raspberry Pi 2/3 reliability
From: |
Bonnans, Laurent |
Subject: |
Re: [PATCH 00/19] hw/arm/raspi: Improve Raspberry Pi 2/3 reliability |
Date: |
Wed, 16 Oct 2019 09:57:29 +0000 |
On 9/26/19 7:34 PM, Philippe Mathieu-Daudé wrote:
> Hi,
>
> I previously posted a RFC for the Raspberry Pi 4:
> https://www.mail-archive.com/address@hidden/msg642241.html
> and got it almost working (boots Linux kernel to userland, sadly
> I'm still having timeout issues with the eMMC block).
> However since it is quite usable, I started to clean up to post
> the series and realized it is way too big for Peter Maydell, so
> I'm following his rule of thumb by splitting in 3 sets of ~20
> functional patches.
>
> In this first series, we pay old debts with these models. Linux
> evolved and recent kernels were barely usable. U-boot now ticks,
> Linux stops to Oops every so and then. We can use more than one
> console at a time (think pppd?).
>
> Then we add various tests to confirm our effort made sense, and
> to avoid regressions.
>
> Laurent, Cheng, do you mind testing on U-Boot?
Great, thanks a lot Phil!
We've managed to run u-boot with serial output and switch to the kernel
read from the same sd card image we use on real hardware.
It also requires the small hack to make qemu simulate the early boot
sequence from the rpi firmware, following the explanations of Peter:
mkimage -A arm -T kernel -C none -O linux -a 0x800 -e 0x800 -d
u-boot.bin u-boot.img
qemu ... -kernel u-boot.img ...
After that, we are getting kernel panics at the point where our
initramfs' init get executed. We are not yet sure about the exact
reason, but that's still a great improvement.
Laurent
> In the next part we'll improve/update the MBox/Properties and the
> interrupt controller blocks.
>
> Finally the last part adds the raspi4.
>
> Please review.
>
> Regards,
>
> Phil.
>