Richard/Saul, Updating the SRCREVs to take into acccount the utrace update from Tom. With this, the stage is set for systemtap support. The following changes since commit

From: Alexander Holler <holler@...> commit e2a346a2a054f702fd76f328ff747b9ad9264a4c from git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git Without msecure beeing high

From: Jingdong Lu <jingdong.lu@...> arm: omap3: beagle: Ensure msecure is mux'd to be able to set the RTC Fixes bug [YOCTO #767] Alexander Holler (1): arm: omap3: beagle: Ensure msecure

Yes, I agree. Jingdong should generate a new patch by cherry-pick or format-patch. Liming Wang

Hi Richard,

These are merged, and pushed. I put this in a common location so all BSPs have the changes. I'm doing some final build testing now, but I'll have a SRCREV update for this later

Hi Dongxiao, Whats interesting there is the relatively large sys times compared to user. Any idea why that's happening? Spinning locks? Agreed, this isn't as good as we'd hoped for :(. I think we

Op 16 jun 2011, om 16:45 heeft Darren Hart het volgende geschreven: FWIW, it survives warm resests. regards, Koen

Agreed. I will just pull the patch and add Jingdong as the Integrated-by. -- Darren -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

It's likely just a glitch in patch generation. Jindong: did you cherry-pick or git am this for the import into your tree ? Or did you use another technique ? If done properly, the author is always

And we don't want the bug tracking information directly in the kernel commits, it just ends up cluttering things. It's fine to include this in the 0/N email, but not in the commit message

Op 16 jun 2011, om 08:07 heeft Jingdong Lu het volgende geschreven: When I do 'git show e2a346a2a054f702fd76f328ff747b9ad9264a4' I get: commit e2a346a2a054f702fd76f328ff747b9ad9264a4c Author:

It's fine if you break this line into two lines. I think it's best to put your comment in the top line. Liming Wang

From: Jingdong Lu <jingdong.lu@...> commit e2a346a2a054f702fd76f328ff747b9ad9264a4c from git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git arm: omap3: beagle: Ensure

From: Jingdong Lu <jingdong.lu@...> Ensure msecure is mux'd to be able to set the RTC for beagleboard. Fixes bug [YOCTO #767] Jingdong Lu (1): RTC: Ensure msecure is mux'd to be able to

Ack'd. For me, this is reasonable. Having a working RTC even if it doesn't survive power cycle is worth having. In particular, since the patch is simple. perfect. This is key. We must have this in

The signal "msecure" on TPS65950 connects to "msecure" on OMAP3530 and setting/writing RTC register is controlled by OMAP3530 "msecure". So we should pull the "msecure" high on OMAP3530 so that we can

The autoconf'ing is sort of arbitrary at the moment. Depending on what is staged the results may vary. So some way of creating a cache is nice since it can be used to verify if package rebuild

Hi Richard, Recently I was doing the "configure optimization" feature and collecting data for it. The main logic of this feature is straight forward: 1. Use the diff file as autoreconf cache. (I