Bug#1016963: Please test u-boot for rock-pi-4-rk3399
On 2023-01-05, Christopher Obbard wrote: > On Thu, 2023-01-05 at 13:21 -0300, Walter Lozano wrote: >> Thank you for your help here! I also did some testing, and everything >> looks OK. The only thing to mention is that the the script >> u-boot-install-rockchip does not auto detect my board. >> >> The case statement is >> ``` >> "Radxa ROCK Pi 4") >> TARGET="/usr/lib/u-boot/rock-pi-4-rk3399" >> ``` > > Ah, good catch! > > For compatiblity with mainline (debian) kernel, that line should > probably be updated to: > > "Radxa ROCK Pi 4A"|"Radxa ROCK Pi 4A+"|"Radxa ROCK Pi > 4B"|"Radxa ROCK Pi 4B+") > > > The Radxa kernel[1] 4.14 branches use "ROCK PI 4A" and "ROCK PI 4B", we > could add those in if we really wanted to. The 5.10 based kernels use > devicetrees based on mainline, so are unaffected. I would definitely be amenable to such a patch, although probably best in a separate bug report and/or merge request. Could even use some wildcards, if appropriate. live well, vagrant signature.asc Description: PGP signature
Bug#1016963: Please test u-boot for rock-pi-4-rk3399
On Thu, 2023-01-05 at 13:21 -0300, Walter Lozano wrote: > Hi Christopher and Vagrant > > On 1/5/23 12:10, Christopher Obbard wrote: > > On Wed, 2022-12-28 at 15:53 -0800, Vagrant Cascadian wrote: > > > On 2022-12-28, Vagrant Cascadian wrote: > > > > On 2022-12-22, Vagrant Cascadian wrote: > > > > > On 2022-08-20, Vagrant Cascadian wrote: > > > > > > On 2022-08-10, Vagrant Cascadian wrote: > > > > > > > This bug is just to delay migration to testing while more > > > > > > > platforms get > > > > > > > tested. If you have a relevent board, please consider > > > > > > > testing > > > > > > > and > > > > > > > reporting the status: > > > > > > > > > > > > > > https://wiki.debian.org/U-boot/Status > > > > > > > > I have not received many test results for current or even > > > > remotely > > > > recent u-boot platforms in Debian, and u-boot has been blocked > > > > from > > > > migration to testing partly because of this. > > > > > > > > As the bookworm freeze approaches, this is getting to be... > > > > worrysome! > > > > > > > > If you have access to any of these boards, please consider > > > > testing > > > > u-boot versions as packaged in debian for versions from debian > > > > stable > > > > (2021.01*), testing (2022.04*), unstable (2022.10*) and > > > > experimental > > > > (2023.01-rc*) and updating the wiki page if successful and/or > > > > replying > > > > to 1016...@bugs.debian.org with a positive confirmation... > > > > > > > > ...and if not successful, filing bugs against the relevent u- > > > > boot-* > > > > packages and marking them as blocking 1016963. > > > > > > rock-pi-4-rk3399 > > > > Hi Walter, Hi Vagrant, > > > > > > I tested this board and updated the wiki. All looks fine to me. > > > > - rock-pi-4-rk3399, on rock-pi-4b, 2023.01-rc4+dfsg-1 from > > experimental > > - SD boot: works > > - MAC address: correctly derived from serial number > > > > > > - rock-pi-4-rk3399, on rock-pi-4b, 2022.10+dfsg-2 from unstable > > - SD boot: works > > - MAC address: correctly derived from serial number > > > > Thank you for your help here! I also did some testing, and everything > looks OK. The only thing to mention is that the the script > u-boot-install-rockchip does not auto detect my board. > > The case statement is > ``` > "Radxa ROCK Pi 4") > TARGET="/usr/lib/u-boot/rock-pi-4-rk3399" > ``` Ah, good catch! For compatiblity with mainline (debian) kernel, that line should probably be updated to: "Radxa ROCK Pi 4A"|"Radxa ROCK Pi 4A+"|"Radxa ROCK Pi 4B"|"Radxa ROCK Pi 4B+") The Radxa kernel[1] 4.14 branches use "ROCK PI 4A" and "ROCK PI 4B", we could add those in if we really wanted to. The 5.10 based kernels use devicetrees based on mainline, so are unaffected. Thanks! Chris [1]: https://github.com/radxa/kernel/blob/stable-4.4-rockpi4/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4a.dts > > fails since the string in my case is only "ROCK Pi 4". Of course, by > setting TARGET variable I can upgrade it without problems. I don't > consider this an issue and it is probably related to the kernel I am > using, since I have used as starting point the images from Radxa [1]. > > Regards, > > Walter > > [1] https://wiki.radxa.com/Rockpi4/downloads >
Bug#1016963: Please test u-boot for rock-pi-4-rk3399
Hi Christopher and Vagrant On 1/5/23 12:10, Christopher Obbard wrote: On Wed, 2022-12-28 at 15:53 -0800, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: On 2022-12-22, Vagrant Cascadian wrote: On 2022-08-20, Vagrant Cascadian wrote: On 2022-08-10, Vagrant Cascadian wrote: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze approaches, this is getting to be... worrysome! If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... ...and if not successful, filing bugs against the relevent u-boot-* packages and marking them as blocking 1016963. rock-pi-4-rk3399 Hi Walter, Hi Vagrant, I tested this board and updated the wiki. All looks fine to me. - rock-pi-4-rk3399, on rock-pi-4b, 2023.01-rc4+dfsg-1 from experimental - SD boot: works - MAC address: correctly derived from serial number - rock-pi-4-rk3399, on rock-pi-4b, 2022.10+dfsg-2 from unstable - SD boot: works - MAC address: correctly derived from serial number Thank you for your help here! I also did some testing, and everything looks OK. The only thing to mention is that the the script u-boot-install-rockchip does not auto detect my board. The case statement is ``` "Radxa ROCK Pi 4") TARGET="/usr/lib/u-boot/rock-pi-4-rk3399" ``` fails since the string in my case is only "ROCK Pi 4". Of course, by setting TARGET variable I can upgrade it without problems. I don't consider this an issue and it is probably related to the kernel I am using, since I have used as starting point the images from Radxa [1]. Regards, Walter [1] https://wiki.radxa.com/Rockpi4/downloads -- Walter Lozano Collabora Ltd.
Bug#1016963: Please test u-boot for rock-pi-4-rk3399
On Wed, 2022-12-28 at 15:53 -0800, Vagrant Cascadian wrote: > On 2022-12-28, Vagrant Cascadian wrote: > > On 2022-12-22, Vagrant Cascadian wrote: > > > On 2022-08-20, Vagrant Cascadian wrote: > > > > On 2022-08-10, Vagrant Cascadian wrote: > > > > > This bug is just to delay migration to testing while more > > > > > platforms get > > > > > tested. If you have a relevent board, please consider testing > > > > > and > > > > > reporting the status: > > > > > > > > > > https://wiki.debian.org/U-boot/Status > > > > I have not received many test results for current or even remotely > > recent u-boot platforms in Debian, and u-boot has been blocked from > > migration to testing partly because of this. > > > > As the bookworm freeze approaches, this is getting to be... > > worrysome! > > > > If you have access to any of these boards, please consider testing > > u-boot versions as packaged in debian for versions from debian > > stable > > (2021.01*), testing (2022.04*), unstable (2022.10*) and > > experimental > > (2023.01-rc*) and updating the wiki page if successful and/or > > replying > > to 1016...@bugs.debian.org with a positive confirmation... > > > > ...and if not successful, filing bugs against the relevent u-boot-* > > packages and marking them as blocking 1016963. > > rock-pi-4-rk3399 Hi Walter, Hi Vagrant, I tested this board and updated the wiki. All looks fine to me. - rock-pi-4-rk3399, on rock-pi-4b, 2023.01-rc4+dfsg-1 from experimental - SD boot: works - MAC address: correctly derived from serial number - rock-pi-4-rk3399, on rock-pi-4b, 2022.10+dfsg-2 from unstable - SD boot: works - MAC address: correctly derived from serial number
Bug#1016963: Please test u-boot for rock-pi-4-rk3399
On 12/28/22 20:53, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: On 2022-12-22, Vagrant Cascadian wrote: On 2022-08-20, Vagrant Cascadian wrote: On 2022-08-10, Vagrant Cascadian wrote: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze approaches, this is getting to be... worrysome! If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... ...and if not successful, filing bugs against the relevent u-boot-* packages and marking them as blocking 1016963. rock-pi-4-rk3399 Sorry for the late reply, let me run some tests and confirm the status. Regards, -- Walter Lozano Collabora Ltd.
Bug#1016963: Please test u-boot for rock-pi-4-rk3399
On 2022-12-28, Vagrant Cascadian wrote: > On 2022-12-22, Vagrant Cascadian wrote: >> On 2022-08-20, Vagrant Cascadian wrote: >>> On 2022-08-10, Vagrant Cascadian wrote: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status > > I have not received many test results for current or even remotely > recent u-boot platforms in Debian, and u-boot has been blocked from > migration to testing partly because of this. > > As the bookworm freeze approaches, this is getting to be... worrysome! > > If you have access to any of these boards, please consider testing > u-boot versions as packaged in debian for versions from debian stable > (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental > (2023.01-rc*) and updating the wiki page if successful and/or replying > to 1016...@bugs.debian.org with a positive confirmation... > > ...and if not successful, filing bugs against the relevent u-boot-* > packages and marking them as blocking 1016963. rock-pi-4-rk3399 live well, vagrant signature.asc Description: PGP signature
