So unfortunately its a few days late due to me being on vacation and the
omap dss merge snafu I hit Thursday that has since been resolved (thanks
Nico & Deepak!)
Anyway, the 11.07 freeze kernel is available here:
git://git.linaro.org/people/jstultz/android.git linaro-android-3.0
And is tagged as: linux-linaro-3.0-2011.07-1-android-0
I've tested both PandaBoard and BeagleXM(a2) successfully.
Outstanding issues:
===================
ADB Panic on panda:
https://bugs.launchpad.net/linaro-android/+bug/807230
Have a fix, waiting for maintainer comment, will apply soon.
BeagleXM (revC) HDMI issues:
https://bugs.launchpad.net/linaro-android/+bug/812097
I can't reproduce. Need confirmation the board doesn't have hw issues.
Some help from TI folks would be good.
So far that's all I'm tracking for the Android 11.07 release. Let me
know if anything else kernel wise needs to be added to my radar.
thanks
-john
On Tue, 2011-07-05 at 18:51 +0530, ashishj3 wrote:
> This driver adds support for the watchdog functionality provided by the Dialog
> Semiconductor DA9052 PMIC chip.
>
> Signed-off-by: David Dajun Chen <dchen(a)diasemi.com>
> Signed-off-by: Ashish Jangam <ashish.jangam(a)kpitcummins.com>
> ---
If there are no comments then can you ACK this patch?
On Thu, Jul 21, 2011 at 13:24, Paul Sokolovsky
<paul.sokolovsky(a)linaro.org> wrote:
> I have following scenario:
>
> 1. Submitted a change for branch X to Gerrit.
> 2. In the meantime, I also created a personal branch Y in the same
> repository for integration testing.
> 3. Once that branch Y is pushed into Gerrit, the original change
> (still designated for branch X) is closed as "Merged", with comment
> added "Change has been successfully pushed into branch Y."
>
> For me, this is not expected behavior - the change isn't merged, until
> it lands into the designated branch, personal development branches and
> stuff don't count.
>
> So, is this expected behavior from Gerrit (2.2.1), does it always work
> this way, or can it be configured to be branch-strict, and if no, what
> are recommendations and best practices for manual/automated integration
> testing of changes?
I thought we fixed this. Maybe its only fixed in "master" and hasn't
been released yet?
The old logic matched on Change-Id alone, and allowed a change to be
closed if that Change-Id was pushed into any branch. IIRC current
master matches on Change-Id *AND* branch pair, so pushing a commit
with the same Change-Id into a different branch won't close the open
change.
Hy Andy,
These are the required changes to make SGX to work with the external
module, as we had for 2.6.38.
These patches are just a forward port of the same patches from 2.6.38,
will try to ping the original authors to see why this is still not
upstream.
Cheers!
The following changes since commit 5b14e370cca884fa86471e909512f65b06dcaec2:
config non drm sgx (2011-07-18 11:52:26 +0100)
are available in the git repository at:
git://git.linaro.org/people/rsalveti/linux-linaro-3.0.git
rsalveti-tilt-for-andy
Hemant Hariyani (1):
Kernel changes for hwmod and omap_device initialization for GPU.
Vikram Pandita (1):
OMAP4: SGX-KM: Enable SGX initialisation
arch/arm/mach-omap2/devices.c | 59 +++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 84 ++++++++++++++++++++++++++++
arch/arm/plat-omap/include/plat/gpu.h | 33 +++++++++++
3 files changed, 176 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/plat-omap/include/plat/gpu.h
--
Ricardo Salveti de Araujo
Given the focus of my team's efforts, it's perhaps a bit silly that we
haven't been running our own tests regularly. In any case, I've just
set up a quick n' dirty jenkins job that sets up lava-dev-tool, runs
lava-dev-tool sequence and puts the results here:
http://validation.linaro.org/jenkins/job/lava-selftest/lastSuccessfulBuild/…
which perhaps isn't an ideal summary, but it's a start. More
information on the errors will be buried in the logs somewhere :)
Cheers,
mwh