* Rick Thomas [2022-06-22 20:05]:
> Great! Thanks! Now for testing: what exactly should I do with this
> tar-ball? I've been relying on Martin's instruction page at
> https://www.cyrius.com/debian/kirkwood/openrd/install/ which only
> mentions downloading two files (uImage and uInitrd) and
On Wed, Jun 22, 2022, at 7:27 AM, Cyril Brulebois wrote:
>> (If it builds, can you upload the images somewhere so Rick can test
>> them?)
>
> Sure, that was the plan all along.
>
> https://people.debian.org/~kibi/openrd4bullseye/ has the tarball after a
> full debian-installer build (it'll stay
Hi,
The next point release for "bullseye" (11.4) is scheduled for Saturday,
July 9th. Processing of new uploads into bullseye-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Martin Michlmayr (2022-06-22):
> I think you completely reverted commit e799d626f4. You should only
> revert the change to build/config/armel/kirkwood/netboot.cfg but not
> the change to build/boot/arm/armel-kirkwood-u-boot-image-config
> (since OpenRD for u-boot was removed).
Sorry, didn't pay
Hi Martin,
Martin Michlmayr (2022-06-09):
> 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
* Cyril Brulebois [2022-06-22 15:39]:
> > Basically to revert the change to build/config/armel/kirkwood/netboot.cfg
> > from commit e799d626f45e9c706d05003e3112d481db2870a9
> Tried that, building in bullseye_armel-dchroot on amdahl (following
> instructions at
6 matches
Mail list logo
