henrik at henriknordstrom.net
Thu Oct 13 19:22:51 UTC 2011
Been a rather intense discussion regarding U-Boot on IRC today, and time
for some reflections and a little decision to be taken.
In stage3 we do have an u-boot package which provides uboot images for
pandaboard, trimslice, beagleboard and some more. The pandaboard
requires u-boot on the boot media, while on trimslice the vendor
provided u-boot is in reality quite sufficient and stored separately in
a nor flash chip.
Several (myself included) thinks it would be good if Fedora fully
supported some boards, with both kernel & up to date bootloader
(u-boot). But u-boot is not a fedora package today and will require both
willing maintainers and package review to happen.
So time for some questions.
Should Fedora for ARM officially support for some well known boards?
Do you think Fedora should provide the bootloader for well known boards
where the required board support is merged mainline?
Do you know anyone who would be willing to help maintain u-boot within
Should u-boot images then also be provided for boards without a trivial
recovery mechanism in case an u-boot update fails? Where there is a risk
of creating bricks if the user do not have jtag access to their board.
Note: Supporting u-boot on boards without mainline u-boot support is not
More information about the arm