Time to leave 2.6.38 behind and move on! We now have a 2.6.39 based
Linaro kernel which can be viewed here:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-2.6.39.git;a=summary
or cloned from either of those:
git://git.linaro.org/kernel/linux-linaro-2.6.39.githttp://git.linaro.org/git/kernel/linux-linaro-2.6.39.git
This will continue to evolve as this is just the beginning for that
tree, so more stuff will be merged. Only smoke tested on a Dove board,
and compile tested for OMAP so far.
Most of the ARM related patches which made their way into v3.0-rc1 in
mainline are included. However there might still be patches that were
included in linaro-2.6.38 which are missing from linaro-2.6.39 at the
moment. I might forward port some of them according to their
importance, their look, or even my mood. So if you need extra patches
on top of what's currently there please tell me and don't just assume I
will pick them up from linaro-2.6.38 automatically (this is reverse
garbage collection i.e. I'll simply leave unwanted patches behind).
This is also a good opportunity for landing teams to test their
git-rebase skills and move ahead to linaro-2.6.39.
Enjoy!
Nicolas
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Completed the power measurement with and without memory regions patches,
but did not find any savings in power consumed.
* Did further testing at hardware level (with only u-boot executing, no linux)
and found a issue with memory controller settings. After fixing the issue,
there is about 60mA of savings when all the banks of the 4 DDR3 modules
connected to one memory controller are kept in precharge power-down
mode versus when read/write activity are active on them.
* Submitted third version of the clkdev patches.
=== Plans ===
* Re-run the tests with memory regions patches. Also find a test
equipment that can provide average power consumed when a
test case is executed.
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* RCU priority boosting in mainline seems to have quieted down.
* Participated in LKML discussions on memory regions (it appears that Intel would prefer to ignore memory regions in favor of requiring a GPU on all systems).
* Continued working on ARM server whitepaper.
* Attended more public plan reviews.
== Miscellaneous ==
* Processed more license requests.
* Miscellaneous RCU maintainership work.
== Niklas Hernaeus <nhe> ==
=== General activity ===
* Viewed the device-tree code.
* Studied the new blueprints for device-tree for u8500.
* Tried to dabble with the dtc. -> going to contact gcl.
== Dave Martin <dmart> ==
=== General Activity ===
* Some kernel patch work:
* Proposed a couple of suggestions for avoiding
misalignment of data structures in assembler.
* Some discussion with Will Deacon on a generic backend for
turning the MMU off so that this doesn't have to be
reinvented by kexec and hibernation code. (There seems
to be no reasonably correct implementation of this in the
kernel as yet, which is one of the reasons kexec has
never worked reliably for ARM.)
* Investigating how the kernel boot protocol can be
clarified for better Thumb-2 compatibility.
* More activity on minor bugs in gas:
* http://sourceware.org/bugzilla/show_bug.cgi?id=12848
(ARM: Thumb-2: Range check on b.w is off by a factor of
2)
* http://sourceware.org/bugzilla/show_bug.cgi?id=12854
(ARM: Nonsensical argument shift specifications accepted
for LSL/LSR/ASR/ROR mnemonics)
=== linaro-kernel-o-standard-arch ===
* Testing of the linux-linaro-2.6.39 and linux-linaro-oneiric
trees with Thumb-2:
* Generic Thumb-2 booting didn't work because of breakage
by a random patch. Spent some time trying to debug
this-- Now fixed by a patch from Nicolas Pitre. (He beat
me to it!)
* vexpress now works in Thumb-2
* OMAP new works in Thumb-2
* mx51evk status still to be determined
* Did some investigation into what mx51evk is using FIQ for.
Some compatibility issues for Thumb-2: still need to follow
up with the the imx guys.
=== Plans ===
* Ping John Rigby again re enabling Thumb-2 for the vexpress
kernel.
* Check whether the new kernel trees work in Thumb-2 on
mx51evk and follow up with Freescale landing team.
=== Issues ===
* Some disruption due to an office relocation. Mostly back to
normal now.
== Per Forlin <perfor> ==
=== Highlights ===
* Set up pandaboard for wifi using wl12xx driver.
* I couldn't get wl12xx_sdio_test to work, instead I used the normal
wl12xx wifi driver to study the execution flow.
* Made the conclusion that mmc async request function in core.c is
applicable for SDIO as well.
=== Completed WIs===
* https://blueprints.edge.launchpad.net/linux-linaro/+spec/mmc-async-request
* Set up SDIO client for test purposes, wl12xx on pandaboard: DONE
* investigate if/how SDIO clients may utilize async request support
in core.c: DONE
=== Plans ===
* Rebase mmc async request on Linux 3.0 and submit
== Manjunath G Kondaiah <manjugk> ==
=== Highlights ===
* Started adapting regulator data to DT structures for OMAP panda board
- looking into modifications for i2c controller and twl-core driver
- used grant's beagle board i2c modification as reference.
- facing issues with getting data from DT structure into twl-core
driver...debug in progress
* DT Documentation reading in progress
- Documentation/devicetree/bindings/i2c
- Documentation/devicetree/booting-without-of.txt
- http://devicetree.org/Device_Tree_Usage
-Manjunath
== Shawn Guo (shawnguo) ==
=== Device Tree ===
* None
=== ARM/imx consolidation ===
* Converted gpio-mxc and gpio-mxs to use basic_mmio_gpio and
generic irq chip
* Converted mx5 interrupt controller tzic to use generic irq chip
=== Misc ===
* [Bug 754254] imx51 randomly truncates serial input at 31
characters. This is a system performance issue caused by lacking
of card detection interrupt support in esdhc driver. The patch
submitted for upstream is below.
http://thread.gmane.org/gmane.linux.kernel.mmc/8495
=== Plan ===
* imx consolidation and device-tree stuff
--
Regards,
Shawn
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Finishing up coordination of 11.11 work
* Traveled to Austin to meet with Kiko, Zach, Paul L., and Mouni to
discuss various topics includingr:
* Continuous integration/validation cycle
* Android LEB deliverables and kernel ownership
* Test framework needs from kernel team and vice versa
* How to get Landing Teams more upstream focused
* IRC meeting with Arnd and Per to go over storage BPs for 11.11
* Linus W. from ST-E joining KWG
=== Plans for Next Week ===
*Start work on "ARM Porting Guide"
* Various 1:1s with team members
* Device Tree coordination meeting
(Deepak, Grant, Manju, Shawn, Niklas, Thomas, Linus)
* Storage work coordination meeting
(Deepak, Arnd, Per, Venkat, Tixy)
* Put together slides for upstreaming/consolidation update to TSC (Due June 22)
* Close out on kernel monthly release process for 11.11 cycle
=== Upcoming Travel/Time Off ===
Out Friday June 17th - Mon June 20th,
(in the middle of the woods no Internet or phone access)
Hi,
I had a really good meeting with Paul Larson this week to discuss
the automated test framework that Linaro is developing and wanted
to follow up with the team on brainstorming around what we want
to be running on a regular basis to test the kernels. The current testing
includes:
"x11perf",
"gtkperf",
"glmemperf",
"posixtestsuite",
"gmpbench",
"pybench",
"stream"
I think the obvious missing one is LTP which Shawn is working on
getting up and running on ARM for the 11.11 cycle. Arnd's flash
testing tool might also be a good fit, but I am not sure of the side
effects it might have to the underlying device after extended use.
I also think that adding board specific tests such as "run i2cdetect
and validate that we see all the devices we expect" is something
useful to do in the long-term to validate that driver changes, DT
updates, etc do not break support for a given board.
I'm interested in hearing ideas that others have on what kinds of
tests we should be running.
Thanks,
~Deepak
