Hi,
I've just made some small improvements to status.linaro.org to make it
easier to keep running.
Firstly, at the bottom of every page is now the time at which the page
was last updated. If it's more than an hour ago then the site isn't
updating.
If it's not updating then follow the "Update log" link to take a look
at why. This records each attempt to update and any exceptions that
prevented it from happening. It rotates once a day so you may need
to look at the "yesterday" link to see why.
If there's a bug you can use the "Bugs" link to search for and report
it.
If you want to check the code use the "Code" link.
Finally, if you want to see the config, to see what is being tracked,
and to update it, then use the "Config" link.
Thanks,
James
When building with the make O= option some of the dependenccies
and include files can't be resolved. This patch corrects the paths
so that the files can be found.
Thsis is a patch For Chunsangs repo at :
git://git.linaro.org/people/chunsangjeong/mali.git
Signed-off-by: Angus Ainslie <angus.ainslie(a)linaro.org>
---
drivers/gpu/arm/mali/Makefile | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/arm/mali/Makefile b/drivers/gpu/arm/mali/Makefile
index 47a147d..8481706 100755
--- a/drivers/gpu/arm/mali/Makefile
+++ b/drivers/gpu/arm/mali/Makefile
@@ -10,12 +10,12 @@
OSKOS :=linux
FILES_PREFIX=
-MALI_FILE_PREFIX := drivers/gpu/arm/mali
+MALI_FILE_PREFIX := $(srctree)/drivers/gpu/arm/mali
KBUILDROOT =
# Add platform configuration file for Mali
ifeq ($(CONFIG_ARCH_EXYNOS4),y)
-MACHDIR := arch/arm/mach-exynos4
+MACHDIR := $(srctree)/arch/arm/mach-exynos4
MALICONFIGDIR :=$(MACHDIR)/include/mach/mali
endif
--
1.7.4.1
Enclosed please find the link to the Weekly Status report
for the kernel working group for the week ending 2011-07-15.
== Meeting Minutes ==
https://wiki.linaro.org/WorkingGroups/Kernel/Meetings/2011-07-11
== Weekly Status Report ==
https://wiki.linaro.org/WorkingGroups/Kernel/Status/2011-07-14
== Summary ==
* Released initial linaro+android-3.0 kernel branch
* Device Tree
* migrating imx driver to device tree aware, serial, fec, gpio, esdhc and
spi are basically done.
* Moving tegra over to use the device tree, most of the devices being
initialized using the device tree.
* Booted Snowball, with DT.
* Experimentally merged the ael tree with linux-linaro-2.6.39.
* Submitted kprobe Thumb-2 support patches for review.
* Merged branches for omap, imx, at91, davinci, ... into arm-soc.git.
* mmc non-blocking patchset v9 is merged in mmc-next for 3.1
* Multiple posting of patch series to contribute to the single kernel
image
* Merged multiple patches into linaro-2.6.39
Regards,
--
Mounir Bsaibes
Project Manager
Follow Linaro.org:
facebook.com/pages/Linaro/155974581091106http://twitter.com/#!/linaroorghttp://www.linaro.org/linaro-blog <http://www.linaro.org/linaro-blog>
Key Points for wider discussion:
Snowball Android is now building on the build server:
https://android-build.linaro.org/builds/~linaro-android/leb-snowball/
Team Highlights:
Busybox is compiling now and work continues to complete the Android
integration
MLO integration into TI 3.0 LEB started.
Multimedia test script is completed. It will be put in LEB but excluding the
required (large) media files. Download link will appear to user.
Integrating the Build server output to LAVA ongoing.
gcc 4.6 successfully integrated in Linaro Android build. Dbus code cleanup
was required and changes will be upstreamed to AOSP.
Miscellaneous:
----
This status can be found at
https://wiki.linaro.org/Platform/Android/Status/2011-07-14
Hi all,
I was looking at git.linaro.org and I'd like to propose some consistency
in naming our git trees and in how we branch them. The main reason
for this from my perspective is to make it easy to point someone
from a partner team or from a partner''s customer to the git server and
have them quickly figure out what they need to pull. Right now we have:
Generic Linaro Kernels:
kernel/linux-linaro-${version}
Freescale:
bsp/freescale/linux-2.6-imx.git
bsp/freescale/linux-linaro-natty.git
bsp/freescale/linux-meta-linaro-natty.git
bsp/freescale/mx5-gpu.git
bsp/freescale/mx5-vpu.git
bsp/freescale/u-boot-linaro-natty.git
Samsung:
bsp/samsung/linux-linaro-2.6.39.git
bsp/samsung/u-boot-insignal-dev.git
bsp/samsung/u-boot.git
ST-E:
bsp/st-ericsson/firmware-ux500.git
bsp/st-ericsson/linux-2.6.34-ux500.git
bsp/st-ericsson/linux-2.6.35-ux500.git
bsp/st-ericsson/linux-2.6.38-snowball.git
bsp/st-ericsson/linux-2.6.38-ux500.git
bsp/st-ericsson/u-boot-ux500.git
TI:
people/andygreen/kernel-tilt.git
Each of the trees have various tags and branches based on how each
team and developer
works and I don't want to ask folks to change what they are doing for
their day to work.
What I'd like to see is a a separate set of official trees that only
get updated with bits that
we are ready for non-Linaro developers to use, do not get rebased, and
get tagged at the
end of each monthly cycle. My proposal:
kernel/linux-linaro-$version with tags for each monthly release:
v$version-$milestone-$buildcount
kernel/linux-linaro-android-$version with tags for each monthly
release: android-v$version-$milestone-$buildcount
kernel/$soc/linux-linaro-$version with tags for each monthly release:
$bsp-v$version-$milestone-$buildcount
kernel/$soc/linux-linaro-android-$version with tags for each monthly
release: $bsp-android-v$version-$milestone-$buildcount
Comments?
~Deepak