I think we always mess this up on Launch, our main development repo’s are on https://git.beagleboard.org/ Sadly this gitlab server on aws tends run out of bandwidth once hit by everyone…
I’m working syncing our github mirrors:
OpenSBI:
- Fast Mirror: GitHub - beagleboard/beaglev-ahead-opensbi: Mirror of: https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-opensbi.git
- BeagleBoard git: BeagleV-Ahead / beaglev-ahead-opensbi · GitLab
U-Boot:
- Fast mirror: GitHub - beagleboard/beaglev-ahead-u-boot: Mirror of: https://git.beagleboard.org/beaglev-ahead/beaglev-ahead-u-boot
- BeagleBoard git: BeagleV-Ahead / beaglev-ahead-u-boot · GitLab
Linux:
- Fast mirror: GitHub - beagleboard/linux at beaglev-v5.10.113-1.1.2
- BeagleBoard git: Files · beaglev-v5.10.113-1.1.2 · BeagleBoard.org / Linux · GitLab
Yocto:
- Fast mirror: GitHub - beagleboard/xuantie-yocto
- BeagleBoard git: BeagleV-Ahead / xuantie-yocto · GitLab
Ubuntu:
- Fast mirror: GitHub - beagleboard/xuantie-ubuntu: Mirror of: https://git.beagleboard.org/beaglev-ahead/xuantie-ubuntu
- BeagleBoard git: BeagleV-Ahead / xuantie-ubuntu · GitLab
TH1520 Main repos
Warning, gitee tends to be slow in the US, so don’t hit it too hard with a ton of git clone’s… For this reason i had to mirror a bunch of their repo’s to make yocto usable…
Why do we have our own gitlab, which tends to have load issues… (We have our CI hardware behind gitlab to make development even more fun! 
)