On 2023-04-03, Wolf wrote: >> Control: severity 1033845 important >> >> Given that this only affects a single platform, and there are other >> tested working boot options for this platform, I am downgrading the >> severity to important. > > So far ok if you consider it so. > > Actually I thought 'severity' because more or less you brick it if you > install on the > internal emmc due to the boot selection and you have to recover with > screwdriver, DIP > switching off the internal emmc, booting from the microSD and stopping at the > u-boot > prompt, DIP switching on the internal emmc and rescanning the mmc's to be > able to boot.
I had not extensively considered that angle... >> So far I have only ever tested booting from microSD... > > Yes, that works, as long as nothing bad is installed on the internal emmc or > SPL. Did you mean SPI? At any rate, yeah, from what I recall the boot order defined in rom for most rockchip systems is SPI, eMMC, microSD ... (basically from the least removable to the most removable) >> Did this work on previous versions? > > Not with the Debian u-boot package, because I could boot Debian with the > pre-installed and > I just recently upgraded the u-boot, because I wanted the u-boot prompt on > LCD. Ok, so it is not a regression. >> Does it work on the version in experimental (currently 2023.04~rc5*)? > > No, it does not: > pinebook-pro-rk3399_defconfig of 2023.04~rc5: > # CONFIG_SPL_MTD_SUPPORT is not set > # CONFIG_MMC_HS200_SUPPORT is not set > # CONFIG_SPL_MMC_HS200_SUPPORT is not set Yeah, I figured that it wouldn't, but sometimes settings change or get renamed or fixed in some other way. Nevertheless, worth trying. > However, the SPL settings are just precaution, because I have the intention > to try again > installing u-boot in SPL if I find time enough to do so, also for > brick/recover actions. SPI? >> Would you consider submitting a patch upstream? > > Sure, I can do so however, I was reading that a bug report should be always > done to the distribution. As a simple rule, sure, but it is always a judgement call. I do not think we are patching anything hugely relevent in the Debian packaging here (slight chance the rockchip USB related patches are relevent, but I would guess very slight). > Anyway, should I then report in general u-boot related bugs with patches > upstream? If you are up to it, that can be helpful as it will eventually land in Debian (and other distros) that way. It can still be useful to file a bug with Debian in case it make sense to backport a patch from upstream, too. This way we can track when the issue is resolved. So, in some cases, file bugs/patches/etc in both. :) > Because there is another bug screwing up the LCD on reboot or just a reset > command > from u-boot prompt and if I have time enough I might hunt it. I have never had reboot work reliably on the pinebook-pro... Thanks for poking at all this! live well, vagrant
signature.asc
Description: PGP signature
