REVIEW REQUEST: Wiki updated for Beagle REV C4 with u-boot source link

Hello all,

I have tried integrating the wiki that I populated for RevC and the
one populated by Robert PJ

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv3

I have uploaded the u-boot that I was working on for REV C4 @
http://git.gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4.git

I will re-work on the patches and post the same on u-boot GIT.

Please review the wiki and let me know your comments for
incorporating. Meanwhile I will also re-look at the content.

Thanks.

Regards,
Khasim

Hello all,

I have tried integrating the wiki that I populated for RevC and the
one populated by Robert PJ

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv3

Another validation wiki, shouldn't there be only one?

I have uploaded the u-boot that I was working on for REV C4 @
http://git.gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4.git

Oh, another git tree! Shouldn't we be trying to decrease the number of git trees instead creating more and more? The effort spent to create such forks would be better spent trying to get things upstream so we don't even need these forks.

regards,

Koen

Hello all,

I have tried integrating the wiki that I populated for RevC and the
one populated by Robert PJ

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv3

Another validation wiki, shouldn't there be only one?

Yes, this should be the final one, will delete previous one when this
gets accepted.

I have uploaded the u-boot that I was working on for REV C4 @
http://git.gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4.git

Oh, another git tree! Shouldn't we be trying to decrease the number of git trees instead creating more and more? The effort spent to create such forks would be better spent trying to get things upstream so we don't even need these forks.

My initial plan was to just get patches upstream but things didn't go
that smooth, in the mean time there were requests for complete source
code for u-boot on rev C4. This should be a very temporary place
holder, till I get my patches accepted upstream.

Regards,
Khasim

The patches have been at http://www.angstrom-distribution.org/demo/beagleboard/u-boot/ for a month now, I still don't see why there needs to be yet another git tree.

If there are issues getting the patches accepted it might be possible
to have a branch on the u-boot git.
At least that keeps stuff centralized.
Actually there is already a TI tree over there:
http://git.denx.de/?p=u-boot/u-boot-ti.git;a=summary
suggest to align within TI

FM

Hello all,

I have tried integrating the wiki that I populated for RevC and the
one populated by Robert PJ

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv3

Another validation wiki, shouldn't there be only one?

Yes, this should be the final one, will delete previous one when this
gets accepted.

I have uploaded the u-boot that I was working on for REV C4 @
http://git.gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4.git

Oh, another git tree! Shouldn't we be trying to decrease the number of git trees instead creating more and more? The effort spent to create such forks would be better spent trying to get things upstream so we don't even need these forks.

My initial plan was to just get patches upstream but things didn't go
that smooth, in the mean time there were requests for complete source
code for u-boot on rev C4. This should be a very temporary place
holder, till I get my patches accepted upstream.

The patches have been at http://www.angstrom-distribution.org/demo/beagleboard/u-boot/ for a month now, I still don't see why there needs to be yet another git tree.

ok, may be I can just add a link to these instead of another GIT tree.
I think u-boot.bin is also available.

Regards,
Khasim

Hello all,

I have tried integrating the wiki that I populated for RevC and the
one populated by Robert PJ

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv3

Another validation wiki, shouldn't there be only one?

Yes, this should be the final one, will delete previous one when this
gets accepted.

I have uploaded the u-boot that I was working on for REV C4 @
http://git.gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4.git

Oh, another git tree! Shouldn't we be trying to decrease the number of git trees instead creating more and more? The effort spent to create such forks would be better spent trying to get things upstream so we don't even need these forks.

My initial plan was to just get patches upstream but things didn't go
that smooth, in the mean time there were requests for complete source
code for u-boot on rev C4. This should be a very temporary place
holder, till I get my patches accepted upstream.

If there are issues getting the patches accepted it might be possible
to have a branch on the u-boot git.
At least that keeps stuff centralized.
Actually there is already a TI tree over there:
http://git.denx.de/?p=u-boot/u-boot-ti.git;a=summary
suggest to align within TI

This TI tree is not internal, it is for the custodian to merge the
patches. The patches have to go through regular reviews and accepted
on u-boot list before making into the tree.

Therefore I hosted to a Gitorious branch for others to see my patches
or changes that I will be doing for getting the patches accepted.

Regards,
Khasim

I'm pretty confused on three points:

1. I thought the u-boot changes needed for Beagleboard C4 were being compiled by the openembedded.org development branch, e.g. the item below with the asterisk (*):

[rlc@deafeng29 openembedded]$ git branch
* org.openembedded.dev
   stable/2009

So, isn't bitbaking the beagleboard-demo-image going to give me a u-boot that works on C4?

Let's say my assumption above is incorrect. Given that:

2. How do I pull from the u-boot git branch listed below -- what git commands do I need? (Sorry, I'm still new to git.)

3. How do I compile the git branch listed below so that I can get my very own working u-boot for C4?

Thanks

Bob Cochran