== Dave Martin <dmart> ==
=== Activity ===
==== hardware-n-kernel-standard-architecture ====
* VFP coredumps patch moving forwards after some fixes.
gdb/bfd support now implemented by Ulrich Weigand and
confirmed to work.
* Spent a bit of time investigating Thumb-2 for imx51 kernels,
resulting in some upstream patch discussions.
==== miscellaneous ====
* Minor ongiong activity helping support linaro validation
farm activities (network, u8500 bringup)
=== Plans ===
* Ping upstream re outstanding patches.
* Assess ftrace status.
* Write up the output from the Freescale i.MX BSP review
discussion, and post for comment.
=== Absences ===
* Apr 21 2011 - May 2 2011 (unconfirmed)
Nicolas, here are a couple more changes needed for the 11.05 release.
The most important one is Shawn's patch to add a 'dtbs' rule for
building all the configured dtb files which is needed for packaging.
The second adds device tree support for the IGEP which has been build
tested, but that's it since I don't have hardware and I've not
cornered anyone to test it yet. I've got it at the top of tree so you
can just commit HEAD~1 if you're not comfortable merging that one yet.
Can I get a volunteer with an IGEP to test this tree and make sure it
boots with the devicetree?
Thanks,
g.
The following changes since commit 7c4bc9c2662c6d9840afed0e29eb01314af9bb78:
ARM: Only allow PM_SLEEP with CPUs which support suspend (2011-04-04
00:25:21 -0400)
are available in the git repository at:
git://git.secretlab.ca/git/linux-2.6 devicetree/arm-linaro-2.6.38
Grant Likely (1):
arm/dt: Add basic devicetree support to IGEPv2 and v3
Shawn Guo (1):
arm/dt: Add a make rule to build dtb for enabled boards
arch/arm/Makefile | 2 +-
arch/arm/boot/Makefile | 2 ++
arch/arm/boot/dts/isee-igep-v2.dts | 7 +++++++
arch/arm/boot/dts/isee-igep-v3.dts | 7 +++++++
arch/arm/mach-exynos4/Makefile.boot | 2 ++
arch/arm/mach-mx5/Makefile.boot | 5 +++++
arch/arm/mach-omap2/Makefile.boot | 6 ++++++
arch/arm/mach-omap2/board-igep0020.c | 6 ++++++
arch/arm/mach-omap2/board-igep0030.c | 6 ++++++
arch/arm/mach-tegra/Makefile.boot | 2 ++
arch/arm/mach-versatile/Makefile.boot | 2 ++
11 files changed, 46 insertions(+), 1 deletions(-)
create mode 100644 arch/arm/boot/dts/isee-igep-v2.dts
create mode 100644 arch/arm/boot/dts/isee-igep-v3.dts
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
Hey Paul,
As promised, here is my list of topics, tasks and priorities for the
11.11 cycle. It's a bit of a rough list, but I'll refine it as we get
closer to UDS
Boot Architecture
- Refine UEFI position paper (draft of position paper will be prepared
before UDS)
- Refine boot architecture technical recommendations paper (draft will
be prepared before UDS)
- must include reference implementation (based on existing u-boot;
not talking about writing something new here)
- Upgrade procedure for OS
- Upgrade procedure for Firmware
- Security concerns?
- Must guarantee reliability (no bricked boards).
- Discuss kexec bootloader, possibly implement for 11.11 cycle
- Implement appending of device tree and initrd to zImage
- To support minimal bootloader and kexec bootloaders.
- Simplify the process of installing a boot image.
- Implement device tree bindings to describing boot method
- So that Linux knows how to upgrade the kernel and possibly the bootloader.
- SDcard? NAND? NOR? Which partition? etc.
I've got a lot of topics on boot architecture. Most of the needed
technology is in place, but I think it is needed to document best
practices and methods that should be used when designing a system.
What technologies, why, how to put them together, and how to
maintain/support them. It's important to get the guidelines out onto
paper instead of as 'tribal knowledge'
Device Tree
- device tree board description and implementations for:
- The omap3 boards are the priority since there are numerous
expansion boards that can be described (Zippy, trainer, etc) which is
an excellent use-case.
- mx51 & mx53 eval and efika boards
- samsung eval boards
- OMAP3 BeagleBoard, Overo and IGEP boards.
- device tree SoC descriptions for SoCs
- A lot of work has already been done for Samsung and Freescale
SoCs. It would be very interesting to converting an entire SoC over
to use device tree with dtb linked into the kernel for bootloaders
that cannot pass a dtb blob. That would eliminate the problem of
duplicate setup paths
- Would also need task to support linking multiple .dtbs into the kernel
- Complete clock bindings - mostly depends on common clock framework
- Complete virq implementation - **critical task**
Linux ARM Maintainership/Vision
- Full multiplatform - Support multiple SoC families with a single kernel
- to avoid either/or decisions when adding new features to the kernel
- have guidelines for how new interfaces should be defined.
Example: right now struct clk has a different implementation for every
SoC, and only one can be compiled in at a time. New interfaces should
be runtime pluggable wherever possible
- to increase code coverage for allyesconfig/allmodconfig.
- Document best practices for Linux driver model
- Where does data come from (probed, device tree, platform_data)
- How to generalize as much device registration as possible
- How to get away from big lists of devices in board-*.c files.
- How to reduce code duplication.
Basically, I'd like to encourage embedded Linux engineers to think
about the wider scope for the code that they write. To ask themselves
if the work they are doing could be useful to the wider ARM Linux
infrastructure. I'm not sure how to translate the above items into
blueprints, but I think the tasks resolve to writing a lot of
documentation and articles, and probably reviewing a lot of code.
You can probably take the first level bullet points in each category
as names for blueprints. My priorities are to make sure at least one
platform has a 100% complete device tree implementation by the 11.11
release, and that there is a good set of documentation to go with it
covering both boot architecture and device tree. I'd actually like to
see 2 or 3 platforms with a complete implementation, but I'd rather
see 1 platform will a full solution than 3 half baked ones. Close
second is the boot architecture documentation and any associated
sample implementation.
Loïc, David, I'm sure I've missed some of the topics we've talked
about. Is there anything else you can think of that should be added
to this list?
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* Working RCU priority boosting bug: reproduced slowdown (not hang)
* Coded and tested diagnostics to track down this bug
* Found and fixed one bug, more bugs remain
* Worked more stuck TSC license requests
== Miscellaneous ==
* Pulled in kfree_rcu() patches from Lai Jiangshan: Nice API addition and code-size reduction
*
== Per Forlin <perfor> ==
=== Highlights ===
* mmc none blocking implementation is more stable, but there are
still some issues when running stress tests for many hours.
* In contact with developer at Samsung that is interested in testing
my code on the Samsung SoC.
* Started to think about storage work for next cycle
=== Plans ===
* Make all stress tests to pass for mmc code and send out patches on 2.6.39-rc
* Assist in writing storage spec
* Continue supporting testing of my mmc code on other boards.
== Jason Liu <Jasnliu> ==
=== Highlights ===
====DT====
* The basic DT for imx51 babbage, genesi efika mx and imx53 loco
board support done, merged into linaro kernel git.
====Kernel kexec ====
* preparation for the kexec test on freescale platforms.
====Misc====
* John has merged the following patches into linaro uboot git.
1. mx53loco: set mmc env to MMC slot1:
http://lists.denx.de/pipermail/u-boot/2011-March/089000.html
2. fsl_esdhc: Fix multi-block read restriction on i.MX53 eSDHCv2:
http://lists.denx.de/pipermail/u-boot/2011-March/089023.html
=== Plans ===
* Kexec test on freescale platforms
===Issues===
*
