[meta-ti] [RESEND: PATCH 2/3] keystone2: u-boot: update to add gph support

[Karicheri, Muralidharan]

>> > >> See below about pointing SRC_URI to an internal git server.
>> > >>
>> > >>
>> > >> >  BRANCH = "master"
>> > >> >
>> > >> > -# DEV.MCSDK-03.00.00.07
>> > >> > -SRCREV = "82f40e857d853165310d0753e79235aefb65d7ba"
>> > >>
>> > >> Please use the format above - it avoid unnecessary breakages when
>> > >> git-ls-remote is not working...
>> >
>> > Adding a commit id means every time we push something to master, I
>> > need to go and change this. This is not practical. Better point to the
>> > tip for getting the latest for nightly. What am I missing?
>> 
>> The problem is that meta-ti is public and constantly used by many people outside of TI -
>> every time they parse the recipe, it will hit the server. If you point to arago-project.org, it
>> may bring it down, as we have seen before.
>> If you point it to your internal git server, that is not accessible from outside of TI, it will
>> break parsing for everyone and render meta-ti unusable!
>> 
>> See my next comment for details on how to do it in meta-arago instead.
>> 
>> 
>> > >> > +# for nightly switch the two below #SRCREV =
>> > >> > +"DEV.MCSDK-2013-01.10"
>> > >> > +SRCREV = "${AUTOREV}"
>> > >>
>> > >> Same as before - please no AUTOREVs in meta-ti.
>> > >>
>> > >> If you need to track daily/nightly progress from an internal git
>> > >> server, please use a .bbappend in meta-arago, while keeping meta-ti
>> > >> pointing to a piblic git server and using a specific commit ID. Let
>> > >> me know if you need existing examples - we just released Core
>> > >> TI-SDK 2013.04.00 which used to track the latest linux-ti-staging kernel by setting
>> AUTOREV in meta-arago.
>> > >>
>> >
>> > I don't know. Please give me an example or help me figure this out.
>> 
>> Use something as simple as below, but for the kernel:
>> http://arago-project.org/git/?p=meta-
>> arago.git;a=commitdiff;h=32ec5282fd0248581d57ed2a0d66d4c47c275e8c

Hao,

Can you make an update for this in meta-arago so that our nightly points to tip of the master or whatever branch?

Denys,

So for each of the repos, do we have to use a xxx.bbappend, where xxx is u-boot, boot-monitor and linux-keystone?
So I assume the build still uses the meta-ti version of the recipe, but override the SRCREV with whatever set in xxx.bbappend?

Murali