You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the switch to using a Makefile and binary debs from the archive for u-boot it is not easily possible anymore to patch the bootloader i.e. for addon boards that need to be initialized before a kernel loads etc ...
the old setup that was building u-boot from upstream source had well dcumented ways of adding patches and modifying u-boot build configuration for addon hardware (even by following the generic snapcraft documentation about patching and building snaps) so people could follow manufacturer instructions easily. It would be nice to have ways of cusomization documented for the new setup of the snap.
The text was updated successfully, but these errors were encountered:
Do you have specific examples of specific patches for addon boards not supported by the current gadget?
Can you provide pointers to sample "manufacturer instructions" too please?
The old setup did not support newere pi models, and there were differences between core and classic images. The current setup gave us a broader support of more pi models, to the point of being interchangeable (i.e. the same sdcard can be unplugged and plugged into a different Pi model and still boot).
With the switch to using a Makefile and binary debs from the archive for u-boot it is not easily possible anymore to patch the bootloader i.e. for addon boards that need to be initialized before a kernel loads etc ...
the old setup that was building u-boot from upstream source had well dcumented ways of adding patches and modifying u-boot build configuration for addon hardware (even by following the generic snapcraft documentation about patching and building snaps) so people could follow manufacturer instructions easily. It would be nice to have ways of cusomization documented for the new setup of the snap.
The text was updated successfully, but these errors were encountered: