This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Difference between u-boot-omap3.git and u-boot-ti.git repositories

Other Parts Discussed in Thread: AM3517

As I see, TI's PSP are based on http://arago-project.org/git/projects/

For example http://arago-project.org/git/projects/x-load-omap3.git and http://arago-project.org/git/projects/u-boot-omap3.git

But projects "Das U-BOOT" and "X-Load" have their own repositories. X-load located at http://gitorious.org/ x-load-omap3 , u-boot located at http://git.denx.de/?p=u-boot/u-boot-ti.git;a=summary

I need splashscreen support at my AM3517EVM, and it seems that splashscreen based on u-boot-ti.git require less effort because of DSS support in u-boot (see   http://git.denx.de/?p=u-boot/u-boot-ti.git;a=commit;h=de701d118380de12a48c8a4fb345e9f909329432 )

Last synchronization between arago and denx was done 2010-06-17 (see http://arago-project.org/git/projects/?p=u-boot-omap3.git;a=commit;h=530135dcacac278798346ad5825c03131ce51772 ) and it is too late.

Two repositories   http://arago-project.org/git/projects/u-boot-omap3.git and   http://git.denx.de/u-boot-ti.git have realization of non-overlapping new features. This way, u-boot at arago doesn't has changes from 2010-06-17 which was made in denx u-boot such as advanced memcpy(), memset(), DSS support, directory moved arch/arm/cpu/cortexa8 to armv7 etc.

I see Vaibhav Hiremath making changes to both repositories, and want to understand the difference between repositories. Thus, TI suppose both repositories.

As I suppose:

1.  one day arago u-boot will have synchronization with denx u-boot, and DSS support will be done in next TI's PSP. Is it right?

2. I don't know how changes from arago u-boot will be copied to denx u-boot. Manually by TI engineers? How often?

3. What for  there are two u-boot repositories for one big task?   http://arago-project.org/git/projects/u-boot-omap3.git and    http://git.denx.de/u-boot-ti.git

  • I will answer the question w.r.t u-boot-ti.

    u-boot-ti is synced up with mainline u-boot at all times.

    Patches that are devloped in other TI trees are sent for review to the u-boot mailing list.

    This review time is sometimes unpredictable due to the very nature of working in the open source community.

    Sometimes trivial patches that TI engineers develop are rejected in the community. Hence it is not always easy for an arago u-boot tree to be in sync with mainline u-boot and u-boot-ti.

    The intention is to have all the patches in arago u-boot in sync with mainline u-boot but this usually takes time.

    Also an arago based u-boot will be more stable as mainline u-boot is undergoing regular feature changes. At this very time, major feature upgrades are being made to the OMAP support in U-Boot. spl is being enhanced in u-boot.

    -_Sandeep

     

  • Sandeep Paulraj,

    what is secondary program loader ? File README.SPL in u-boot-ti doesn't  have enough information. Is u-boot really SPL and therefore x-loader FPL (first program loader) ?

  • And other question.

    I have information   from ScantiRUS official TI's distributor  that TI will support  AM3517 system-on-module http://www.sauris.de/som.htm

    I work with this modules.  But there are no support for this som and board in mainline u-boot and arago u-boot. I received X-loader and u-boot with that board (they are based on LogicPD am3517evm board from TI's PSP 03.00.01.06), and they are very old and not fully work (for example, no ethernet support in u-boot).

    What is the right way to add support for this board (ScantiRUS build this board)  at arago projects (x-loader, u-boot, kernel) and mainline u-boot-ti and mainline x-load? I want to send that information to ScantiRus to doing that.

    We are planning to use this SOM at our products. I am customer of Sauris SOM, not designer. And I am not satisfied that Sauris SOM is not in TI's supported trees of x-loader, u-boot, kernel.