Vagrant, see below: * Martin Michlmayr <t...@cyrius.com> [2019-08-06 20:10]: > I noticed that there are no pre-built images for OpenRD in buster > anymore. > > I found: > > commit e799d626f45e9c706d05003e3112d481db2870a9 > Author: Vagrant Cascadian <vagr...@debian.org> > Date: Wed Dec 5 17:45:22 2018 +0100 > > [armel] Disable OpenRD targets, no longer present in u-boot. > > While it's true that there are no u-boot images for OpenRD anymore, > I think the installer and kernel should still work fine (people can > install u-boot from stretch or even use the Marvell u-boot that ships > with the device). > > I think the part of the commit above that removed openrd from > build/config/armel/kirkwood/netboot.cfg should be reverted. > (the change to build/boot/arm/armel-kirkwood-u-boot-image-config > is obviously fine) > > I don't have an OpenRD anymore but I can probably find someone if > testing is required.
I became aware recently that this was never fixed. Rick Thomas has two OpenRD (Ultimate and Client) and could test the images. Since bullseye is the last release to support these devices (I think? I never know what the status of armel is), I wonder if it would make sense to add the images back to d-i in a point release. Basically to revert the change to build/config/armel/kirkwood/netboot.cfg from commit e799d626f45e9c706d05003e3112d481db2870a9 Vagrant, do you think you could do a bullseye d-i checkout, make that change and make the OpenRD images available for Rick to test? (I don't have any ARM machines) -- Martin Michlmayr https://www.cyrius.com/
