Altera_Forum
Honored Contributor
19 years agoU-Boot git repository
Hi All,
CVS support for u-boot is EOL: http://forum.niosforum.com/forum/index.php...indpost&p=15735 (http://forum.niosforum.com/forum/index.php?act=st&f=18&t=4025&hl=&view=findpost&p=15735) A git repository has been setup at psyent.com specifically to support Nios II. The u-boot maintainers will now be able to pull from this repo directly into the main source tree ... so hopefully this will help speed things up. Currently the psyent repo contains only the patches that are still pending under the old u-boot patch system -- this is tagged "NIOS2-5_0_0". More updates/features soon -- as time permits. Here's how to get the latest code: method 1: clone the psyent repository<span style="color:blue"># # Just get everything from psyent, the default branch will be 'nios2' $ git clone http://www.psyent.com/git/uboot (http://www.psyent.com/git/uboot) u-boot.git </span> method 2: clone the main repository, pull from psyent<span style="color:blue"># # Clone the main source repo -- without the current patches $ git clone rsync://source.denx.net/git/u-boot.git u-boot.git # # Create the 'nios2' branch $ cd u-boot.git $ git branch -f nios2 master $ git checkout nios2 # # Pull the nios2 branch from psyent $ git pull http://www.psyent.com/git/uboot (http://www.psyent.com/git/uboot) nios2</span> I will eventually produce some beginner docs to help WRT git/u-boot and deposit them in the Wiki (many thanks to hippo). =========================================================== Now, the side-effects: -- GOOD: You need git ... you will be able to keep your source tree (and private brances) up to date very easily by pulling from the main repo (general u-boot updates) and from psyent (Nios II updates). -- GOOD: Contributing to u-boot is easier. You can send me patches, I'll add them to the psyent repo & Wolfgang can pull from psyent. Or you can just setup your own repo. -- BAD: You need git ... if you're developing in a linux/unix environment, you can start learing git without much trouble. If you're not, you can try using the git cygwin port -- but this can be problematic. If you go this route, I recommend you get the latest cygwin. Either way, git is not the easiest system to use -- but with a little effort you'll find it's quite powerful. -- BAD: Limited tarball updates. I will update the u-boot source tarball (cygwin friendly) at psyent as time permits -- but this is not a high priority. Regards, --Scott