On Fri, Jul 31, 2026 at 01:26:39PM +0000, Brice GIBOUDEAU wrote: > Yes I can provide a set of patchs and contribute to your version but for that > there is two things we should tackle before. > - If you have a reference on how to contribute to OpenWrt the proper way > please share it.
The best would be (unfortuantely) to use a Github pull request as that triggers a lot of CI to statically analyse, test-build and have some bots look at your work. If you don't want to use Github, sending a patch series using git-format-patch or git-send-email to this mailing list is also acceptable. Read this: https://openwrt.org/submitting-patches > - I would like to enable other routers before pushing this to OpenWrt > official repo. For now there is only one Board. I need contributors before to > extend a bit what I have done that is very specific to one hardware release. While uboot-mvebu (like all uboot-* packages) covers a whole SoC family, a build is by nature always for a single specific board. Getting more boards supported is of course always nice, but by no means required to first add support for a specific single board. Having that in our repo and automatically generating (~ daily) snapshot builds will also give it more visibility, and more likely attract testers and other contributors to work on similar boards with the same SoC. Out of experience, once a first boards is supported, many other boards based on the same SoC follow quickly. That being said, a platform-specific README covering the recovery methods available (JTAG, some BootROM feature to load from the UART or via USB, or load from external/removable storage...) which come handy during development or with a bricked board is of course also appreciated and will help others with similar boards to dare to attack theirs without being afraid of producing a brick and needing to wire up the flash chip to an external programmer. Cheers Daniel > > Regards > > "Daniel Golle" [email protected] – July 31, 2026 at 3:00 PM > > Hi, > > > > On Fri, Jul 31, 2026 at 01:24:43PM +0200, Brice GIBOUDEAU via openwrt-devel > > wrote: > > > Hello, > > > > > > I’m sharing some work I did to fix a mistake I did by erasing my U-Boot > > > without a backup… yes I know ;-) > > > > > > If this work can be useful for some of you I put the link to the repo > > > below and if some of you want to enable it on other WRTxxx products don’t > > > hesitate to contribute. > > > > > > My work is based on the upstream version of U-Boot and not the very aging > > > version provided by Linksys. > > > > > > You can find it here: > > > > > > https://github.com/TheMiNuS/wrt1900acsv2-uboot > > > > We generally like to host replacement (and enhanced) loaders for > > supported devices. The way do this is typically a set of patches > > including defconfig and maybe a default environment, on top of > > mainline U-Boot. In this particular case, imho it would be the best to > > extend > > https://github.com/openwrt/openwrt/tree/main/package/boot/uboot-mvebu > > instead of having a patch set (leave alone an opqaue source tree) for > > a single board. If you can extract your work into patches to be > > applied there, that would be the best. Create all patches in a way > > that can be applied upstream -- not all of your work may be suitable > > or target upstream, but hardware drivers and defconfig typically the > > answer is typically 'yes'. > > > > If you have questions or need any help with that, let me know. > > > > _______________________________________________ > > openwrt-devel mailing list > > [email protected] > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
