== 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===
*
== Device Tree ==
* Posted the patch that builds .dtb files for boards enabled by
config option. Got good suggestion from Rob Herring to improve.
Will re-spin soon.
* Tried to play linux-linaro-natty tree a little bit to get .dtb file
built in linux-image-*.deb. But I can not post patch for merging
until John Rigby sync this tree with Nico's latest kernel tree.
* Will work on l-m-c to get .dtb installed on boot partition.
== Misc ==
* Read the thread of Linus' complaint on messy ARM platform codes.
--
Regards,
Shawn
== John Stultz <jstultz_*> ==
=== Highlights ===
* Presented internal preview of my ELC talk "Android OS on Servers?"
* Sent pull request to tglx for RTC fixups for 2.6.39
* Sent current AlarmTimers patch queue to lkml for comment
* Implemented timekeeping_inject_sleeptime to handle proper
CLOCK_BOOTIME functionality on systems that don't support
read_persistent_clock
* Identified USB regression on OMAP3
* https://bugs.edge.launchpad.net/linux-linaro/+bug/747639
=== Plans ===
* Hopefully more discussion on Alarm Timers patchset
* Implement permissions capability and policy switch for alarm timers
* Update Linaro Android tree to include latest Linaro tree
* Look into ADB issue reported by Jermey Chang
* Regenerate Android trivial tree
=== Issues ===
* OMAP3 USB regression is blocking Linaro Android tree update
* Panda DSS boot panic is blocking Linaro Android tree update
* Need to get mini-usb cable to test gadget support on beagle board for
ADB support.
== Dave Martin <dmart> ==
=== Activity ===
==== hardware-n-kernel-standard-architecture ====
* Wrote and posted a patch to add VFP state to coredumps.
* Queried on lkml regarding the enabling of the generic
PTRACE_GET/SETREGSET calls.
==== miscellaneous ====
* Helped davepigott bring up the Samsung smdkv310 board.
=== Plans ===
* Give davepigott the info on reflashing U-Boot on the
validation lab u8500 boards.
* Write up the output from the Freescale i.MX BSP review
discussion, and post for comment.
=== Absences ===
* (none)
Hi Nicolas,
Here are the device tree changes for 2.6.38 rebased onto your new
branch. I had to rebase instead of just asking you to pull directly
since I have a number of patches in my test tree that are merged in a
different form in your tree.
For those of you working on DT support for the 11.05 release, please
test against this branch and make sure everything is still working for
you.
g.
The following changes since commit f302d2ec52bfb0d9ae2bb7fbff957f3f6ea71f45:
ARM: 6826/1: Merge v6 and v7 DEBUG_LL DCC support (2011-03-28 14:45:57 -0400)
are available in the git repository at:
git://git.secretlab.ca/git/linux-2.6 devicetree/arm-linaro-2.6.38-rebuilt
Grant Likely (15):
driver-core: remove conditionals around devicetree pointers
dt: Refactor of_platform_bus_probe()
dt: protect against NULL matches passed to of_match_node()
dt: eliminate OF_NO_DEEP_PROBE and test for NULL match table
dt: add of_platform_populate() for creating device from the device tree
dt: add of_platform_prepare() to match nodes with static platform_devices
tty/serial: Relax the device_type restriction from of_serial
arm/dt: Make __vet_atags also accept a dtb image
arm/dt: consolidate atags setup into setup_machine_atags
arm/dt: probe for platforms via the device tree
arm/dt: Basic versatile devicetree support
arm/dt: Basic tegra devicetree support
arm/dt: Add Pandaboard devicetree support
dt: add documentation of ARM dt boot interface
arm/dt: Add dt machine definition
Jeremy Kerr (1):
arm/dt: Allow CONFIG_OF on ARM
Jon Medhurst (1):
arm/dt: Add basic device tree support for Beagleboad
Rob Herring (1):
arm/dt: Add dtb make rule
Thomas Abraham (1):
dt/arm: Add basic device tree support for smdkv310 board
Documentation/arm/Booting | 33 ++-
Documentation/devicetree/booting-without-of.txt | 44 +++-
arch/arm/Kconfig | 7 +
arch/arm/Makefile | 3 +
arch/arm/boot/Makefile | 4 +
arch/arm/boot/dts/exynos4-smdkv310.dts | 31 ++
arch/arm/boot/dts/omap3-beagle.dts | 7 +
arch/arm/boot/dts/omap4-panda.dts | 11 +
arch/arm/boot/dts/skeleton.dtsi | 13 +
arch/arm/boot/dts/tegra-harmony.dts | 7 +
arch/arm/boot/dts/versatile-ab.dts | 7 +
arch/arm/boot/dts/versatile-pb.dts | 7 +
arch/arm/include/asm/mach/arch.h | 18 ++
arch/arm/include/asm/prom.h | 37 +++
arch/arm/include/asm/setup.h | 5 +
arch/arm/kernel/Makefile | 1 +
arch/arm/kernel/devtree.c | 147 ++++++++++
arch/arm/kernel/head-common.S | 24 ++-
arch/arm/kernel/head.S | 8 +-
arch/arm/kernel/setup.c | 97 ++++---
arch/arm/mach-exynos4/mach-smdkv310.c | 6 +
arch/arm/mach-omap2/board-omap3beagle.c | 6 +
arch/arm/mach-omap2/board-omap4panda.c | 6 +
arch/arm/mach-tegra/board-harmony.c | 6 +
arch/arm/mach-versatile/core.c | 1 +
arch/arm/mach-versatile/versatile_ab.c | 6 +
arch/arm/mach-versatile/versatile_pb.c | 6 +
arch/arm/mm/init.c | 11 +
arch/powerpc/platforms/52xx/mpc52xx_common.c | 10 +-
drivers/i2c/busses/i2c-ocores.c | 14 +-
drivers/i2c/i2c-core.c | 2 -
drivers/mmc/host/mmc_spi.c | 4 -
drivers/net/ethoc.c | 8 +-
drivers/of/address.c | 14 +
drivers/of/base.c | 3 +
drivers/of/platform.c | 347 +++++++++++++++++++----
drivers/spi/pxa2xx_spi.c | 2 -
drivers/spi/pxa2xx_spi_pci.c | 2 -
drivers/spi/xilinx_spi.c | 6 -
drivers/tty/serial/of_serial.c | 18 +-
include/linux/device.h | 7 +-
include/linux/i2c.h | 2 -
include/linux/of.h | 4 +-
include/linux/of_address.h | 1 +
include/linux/of_platform.h | 8 +-
45 files changed, 850 insertions(+), 161 deletions(-)
create mode 100755 arch/arm/boot/dts/exynos4-smdkv310.dts
create mode 100644 arch/arm/boot/dts/omap3-beagle.dts
create mode 100644 arch/arm/boot/dts/omap4-panda.dts
create mode 100644 arch/arm/boot/dts/skeleton.dtsi
create mode 100644 arch/arm/boot/dts/tegra-harmony.dts
create mode 100644 arch/arm/boot/dts/versatile-ab.dts
create mode 100644 arch/arm/boot/dts/versatile-pb.dts
create mode 100644 arch/arm/include/asm/prom.h
create mode 100644 arch/arm/kernel/devtree.c
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
Hello everyone,
As I've been working on the integration of the latest developments and
fixes from upstream into the linaro-2.6.38 kernel lately, it became
quickly evident that major merge conflicts were to be expected. The
problem stems from the fact that we opened the 2.6.38 branch early i.e.
around the 2.6.38-rc5 kernel. Many patches that were merged into the
Linaro kernel have been subsequently modified by their respective
maintainers until they were merged upstream, meaning that what we have
now in mainline is different from what the Linaro kernel tree has. This
creates several issues:
- It is hard to verify that what is in the Linaro tree is actually the
latest and the best version of a patch.
- Merging additional fixes from upstream often ends up in merge
conflicts requiring manual resolution, sometimes non-trivial ones,
which is in itself a bug hazard.
- People wanting to contribute patches to the Linaro kernel potentially
have to create a different patch than what they would submit
upstream.
Given those issues, I decided to rebuild the linaro-2.6.38 branch from
scratch to see where that would bring me. And as could be expected, the
result looks nicer and it is much easier to work with than the current
tree. For example, this allowed me to merge the latest OMAP support
from mainline as is, including the latest fixes, without any need for
backport work nor major conflict resolution. Another advantage is that
the commit SHA1 references are now identical in most cases to what can
be found into mainline.
So... my question is: should we switch to this rebuilt tree or not?
There are drawbacks with such a move of course:
- All the testing done so far would be void. This is however not as
bad as this may look as the rebuilt kernel contains fixes for existing
bugs in the current tree, and the rebuilt kernel is using patches
that have and still are being tested by a wider community.
- I didn't forward port a couple series of patches that are available
in the current Linaro tree and not in mainline yet, including:
* DT support (Grant Likely)
* DVFS and PM for OMAP (Vishwanath Sripathy, Vishwanath BS)
* Some ux500 fixups (Linus Walleij)
* clock debug information (Yong Shen)
* Samsung CPUIDLE (Amit Kachhap)
So I would prefer if the people responsible for those patches did
resubmit their patches once they apply to the new tree (that should
be even easier now to apply patches that were meant for mainline).
- The history of the rebuilt tree is obviously different from the
current tree's. This means special care when updating to the new
tree with Git.
But overall I think there are more advantages than disadvantages for
such a move. What other people think?
The current rebuilt tree can be seen at:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-2.6.38.git;a=shortlog;h=…
or obtained from:
git://git.linaro.org/kernel/linux-linaro-2.6.38.git (the "rebuilt" branch)
Nicolas
== Device Tree ==
* Squash sdhci-pltfm-driver-self-registration series which becomes
one patch of sdhci-pltfm&OF-driver-consolidation series
* Sent a fec dt patch to fix build failure with pure non-dt kernel
* Tested dtb-append patch v3 from John Bonesio on mx51 babbage and
found non-dt kernel works fine, but dt kernel fails
== Misc ==
* Reviewed and tested fec improving patch from Lothar
--
Regards,
Shawn
== Jason Liu <Jasnliu> ==
=== Highlights ===
====DT====
* Work on the six step as Grant shows in the link:
http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-March/005024.html,
for the uboot part, I have already mailine it
for i.mx51 babbage board. As for other part, work is in progress.
I will send the whole patch set to grant soon.
====Kernel configuration ====
* NONE
====Misc====
* Some uboot patch upstream for bug fix which reported by FSL linaro
landing team.
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
* Kernel patch upstream for dmabounce bug fix.
* Cache coherency issue analysis and fix for i.mx51 SDIO driver.
=== Plans ===
* DT support for i.mx51/i.mx53 part.
===Issues===
* NONE
== Thomas Abraham <thomas_ab> ==
=== Highlights ===
* Submitted a basic device tree patch for smdkv310 board for inclusion
in smdkv310 hardware pack
* Submitted second version of prerequisite patchset for device tree
support on s5pv310
(http://www.spinics.net/lists/linux-samsung-soc/msg04439.html)
* Working on adding device tree based clock lookup code (based on
of_clock_add_provider)
=== Plans ===
* Submit a third version of s5pv310 dt patchset with clock lookup,
serial, watchdog and sdhci driver support.
=== Issues ===
* None.
== Kernel Development ==
* Reviewed drivers: MEI, cg2900, 23c2510, spear13xx-pcie
* Continued guiding the graduation of the IIO drivers from staging
== Flash memory ==
* Discussed about DRM features for SD cards
* Integrated results from flashbench-results mailing list into wiki
== Other ==
* Reinstalled my workstation with Natty
== Storage performance ==
=== mmc async (optimizations for dma) ===
* Tuned DT (http://www.scsifaq.org/RMiller_Tools/dt.html) together
with fault generation
in order to test error handling in mmc async implementation
* Fix bugs in mmc async implementation (ongoing)
=== mmc trim ===
* Extended trim test cases with secure erase and trim but write
performance (after trim) is still not as high as expected. I probably
need to go over the eMMC spec again to find my mistakes.
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* Attended TSC meeting in Bangalore
* Pushed several more license approvals through the process.
== Issues ==
* -next testing located a bug in RCU priority boosting, which I am working.
Hello!
Please note that the earlier of the two calls will be at 8AM PDT
(3PM GMT, 4PM London time). The second of the two calls will be
12 hours later.
For other timezones, I recommend:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Thanx, Paul
I.e. does CONFIG_THUMB2_KERNEL imply ARMv7 or newer?
I assume this is the intent as arch/arm/Kconfig has
depends on CPU_V7 && !CPU_V6 && !CPU_V6K && EXPERIMENTAL
and there are no hits for the string "v6t" in the source tree
--
Tixy
Hello Folks,
This is my first post to the list. I have been investigating porting
software to the Linaro system (on OMAP 4) and I came across this issue.
Basically, the kernel appears to report that it does not provide Robust
Mutex support? This would seem to be some kind of kernel build/configuration
issue?
The reason I'm asking is that our software system checks for (and uses)
robust mutex features and I had originally built everything on the Ubuntu
10.10 release for Pandaboard only to discover this problem. I tried an 11.04
alpha 3 install on my Pandaboard and robust mutex appeared to work, so I
transferred all our work to that... But now again (after a few updates on
that system) robust mutex seems to be again turned off somewhere.
Any suggestions on how to resolve? Should one expect robust mutex
support?
-Sincerely,
Todd Pack
== John Stultz <jstultz> ==
=== Highlights ===
* Worked on my Android ELC presentation
* CLOCK_BOOTTIME was merged into 2.6.39
* Released initial omap4 defconfig for Linaro Android kernel
* Reviewed PTP patchset on lkml
* Assisting another team with customer NTP issue.
* Identified and resolved a RTC regression with Xen
* Discussed issues surrounding the new direction of the RTC drivers
=== Plans ===
* Presenting my ELC presentation internally, get feedback
* Push Xen RTC fix to mainline
* Spend some additional time debugging the NTP issue I'm assisting with
* Try to get some time to focus on Panda HDMI functionality with
Android kernel
=== Issues ===
* Still have the config work that is getting pinched for time. May need
some extra assistance with those work items.
== Dave Martin <dmart> ==
=== Activity ===
==== hardware-n-kernel-standard-architecture ====
* Put out an RFC regarding how VFP/NEON state should be
represented in core files. Agreed with Ulrich Weigand that
there should be a new note, with structure matching that
yielded by the PTRACE_GETVFPREGS call.
==== miscellaneous ====
* Some time spent helping work around network issues in the
Linaro Cambridge office. Set up a fallback DNS/DHCP server
in case of a repeat of the router failures observed
previously.
* Some time spent helping Dave Pigott get up to speed.
* Set up an iMX53 loco board in the Linaro Cambridge office.
* Some more time spent dealing with ARM internal issues.
=== Plans ===
* Try and reflash U-Boot on the validation lab u8500 boards.
* Set up the remaining Freescale boards in validation lab.
* Write up the output from the Freescale i.MX BSP review
discussion, and post for comment.
=== Issues ===
* iMX53 loco boards can't auto-power-on, which is a problem
for the validation farm.
ericm and the Freecale guys are investigating possible
workarounds.
=== Absences ===
* (none)
This patch series adds the infrastructure required to support kprobes in
Thumb code. As it stands, it allows probes to be inserted onto NOP
instructions.
Work Remaining
--------------
- Add decoding and emulation code for all the different Thumb
instructions.
- Make framework test for probes on conditionally executed instructions
and not execute callback functions if the relevant condition isn't
met.
- Write test code for all Thumb and ARM instruction types. (Does Linux
have in tree test code or do I need to stash this elsewhere?)
Open Issue
----------
32-bit Thumb breakpoints may straddle two memory words, which means
that when we set or clear them there is a window of opportunity where
another CPU may only see half of the new instruction and execute
invalid code. To prevent this I've used stop_machine() to get all
CPUs to synchronously modify the instruction and update their
I-caches. To my thinking, something like this would also be needed so
that other CPUs see the new instruction, otherwise they could
indefinately be executing the old one from their local I-cache.
The problem with using stop_machine() is that the breakpoint setting
code is called from enable_kprobe() which holds the text_mutex and
has this comment which says:
since [the breakpoint setting code] doesn't use stop_machine(),
this doesn't cause deadlock on text_mutex. So, we don't
need get_online_cpus()
Now I am using stop_machine() I need to understand what the
consequences and alternatives are.
I do note, that when probes are disabled, the existing ARM kprobe
implementation uses stop_machine() and we have a similar issue with
this being called from disarm_kprobe() which takes the text_mutex.
== m-y ==
=== Highlights ===
* Patch set for DMA support in USB for U8500 was sent to linux-usb. No
comments so far.
* Patch set v2 is now in internal review.
=== Plans ===
* AB8500 USB transceiver power management
* Bug # 709245.
Thanks,
--
Mian Yousaf Kaukab
== Merge window status ==
* My final BKL patches were all merged.
* unicore32 architecture was merged, I've spent a lot of time
reviewing that in the past.
== Kernel development ==
* Did a review of the IIO (industrial I/O) code in drivers/staging,
from which an extensive discussion started
* Reviewed arm vt8500 clock code and LPS001WP pressure sensor
* and continued commenting on drivers I previously reviewed
== Flash memory performance ==
* Incorporated new measurements from other people into survey
* Updated wiki page
== Device Tree ==
* Sent out the v2 of mx51-platform-dt-clock
* Studied and tested Grant's preregister branch on babbage board
* Sent out sdhci-device-self-registration patch set for review
== Misc ==
* Prepare document for Hungary VISA application
--
Regards,
Shawn
== Storage performance mmc async liability ==
* Added basic fault generation in core.c, using fault injection
framework, to trigger error handling in the mmc async block device
implementation
* Run DT (http://www.scsifaq.org/RMiller_Tools/dt.html) on top of a
vanilla kernel with the fault generation successfully. Next step if to
run this on mmc async and fix bugs. When stable I will rebase on
2.6.39 and post patches.
== absence ==
2,5 days last week due to child sickness
=== planned absence ===
No sickness in sight yet
== Dave Martin <dmart> ==
=== Activity ===
==== hardware-n-kernel-standard-architecture ====
* Some discussion with Tixy about the proposed Thumb-2 kprobes
work.
==== miscellaneous ====
* Holiday
* Some time spent dealing with ARM internal issues.
=== Plans ===
* Post an RFC proposal for adding the NEON/VFP state in
coredumps.
* Try and reflash U-Boot on the validation lab u8500 boards.
* Set up the remaining Freescale boards in validation lab.
* Write up the output from the Freescale i.MX BSP review
discussion, and post for comment.
=== Issues ===
* (none)
=== Absences ===
* (none)
CC'ing linaro-kernel(a)lists.linaro.org and dropping other CC's...
On Fri, 2011-03-18 at 13:20 +0000, Dave Martin wrote:
> On Fri, Mar 18, 2011 at 7:18 AM, Tixy <tixy(a)yxit.co.uk> wrote:
> > On Thu, 2011-03-17 at 19:08 -0400, Nicolas Pitre wrote:
> >> On Thu, 17 Mar 2011, Tixy wrote:
> > [...]
> >> > I also have the first draft of a test framework so I can start working
> >> > on on implementing emulation code for the rest of the Thumb
> >> > instruction set, that could take a while longer ;-) (I plan on adding
> >> > test cases for the current ARM instruction simulation as well).
> >>
> >> Hmmm... How are you doing that? To me this always seemed to be as hard
> >> to make such test framework error free as ensuring that the tested code
> >> is itself error free in the first place.
> >
> > True, but hopefully the bugs in each won't usually cancel each other out
> > and lead to false test passes. Any way, I need some test code otherwise
> > I won't have a simple way of exercising the emulation code I write.
> >
> > The testing method I hit upon was this:
> >
> > probe_before:
> > nop;
> > probe_test:
> > add r0, r1, r2
> > probe_after:
> > nop;
> >
> > Pass 1:
> > - Insert probe_before and probe_after
> > - Run code
> > - When handler 'before' runs, modify register context with test values
> > - When handler 'after' runs, save register context
> >
> > Pass 2:
> > - Insert probe_test
> > - Do same as Pass 1
> > - Verify saved register context is identical to Pass 1.
> >
> > I do the above two passes twice, the second time with CPSR inverted and
> > with the registers not used by the tested instruction also inverted (to
> > more robustly detect if they accidentally get corrupted).
> >
> > I plan on doubling up the passes as well to add setting an IT State, as
> > some instructions behave different in an IT block by not modifying CPSR.
> >
> > I'll have to add support for testing LDR, STR and friends, plus anything
> > else as needed.
>
> I feel that it's important to get some initial, incomplete
> implementation patches out for review as soon as feasible, since that
> gives people the best opportunity to comment or express any concerns
> on the implementation strategy.
I'll aim to post a patch to linaro-kernel by Monday which will have the
Thumb NOP probing work. It'll act as a catalyst for discussing issues
and coding decisions. I'm new to git and patches, so I'll do some tests
with creating local branches and emailing patches to myself first :-)
I won't post the test code yet as that is very much work in progress,
though for anyone curious I put it at http://tixy.me.uk/kprobe-test.c
(I knew I would eventually find a use for the Web server I put on my
Sheevaplug :-)
>
> The testing ideas look like a good start. Can the framework be
> applied to ARM as well as Thumb? It looks at first glance like it
> can, and it would be good to cover the ARM case in the testing if
> there's no test framework already.
Should work with ARM as well with some small tweaking.
> Branch-like instructions are an interesting case, since these often
> occur as specific encodings of otherwise non-branch-like instructions
> (for example, LDR, LDM/POP, MOV{S} etc.)
For branches, test code would need an extra probe at the branch target
(and one at the instruction before to trap miscalculated branches.)
But writing test code is probably a lot less work than actually writing
the simulation code in the kprobe implementation. That has to cope with
all the different instruction types, the test framework would just needs
one or two test types implementing.
> Coming up with all the appropriate test cases could be quite a bit of
> work too, since there is not the same level or orthogonality in the
> instruction set encoding as you get with ARM.
Again, I think this is more of a problem for the implementation of
kprobes, not the test cases. For Thumb, we do have some factors making
it simpler that appears at first sight though...
For 16-bit instructions there are whole swathes of instructions which
only operation on low registers. These can all use the same simulation
code which just restores r0-r7,cpsr, executes the original instruction,
then saves r0-r7,cpsr again. (I realised this after writing my first
half dozen simulation functions :-)
For 32-bit instructions, many of the operations on PC are illegal or
Undefined behaviour; so we can probably get away with ignoring these
cases.
Cheers
--
Tixy
Hi Nicholas,
Pawel Moll submitted a patch to linux-arm-kernel and the
linux-mmc mailing lists to improve the Versatile Express
MMC problem (Launch pad bug #632798). I have tried this
fix on my vexpress and it does improve the mmc throughput.
Can we pull this patch into the current Linaro kernel?
http://permalink.gmane.org/gmane.linux.kernel.mmc/6634
Thanks,
Matt
Hello!
Any nominations for invitations to LDS in May?
Thanx, Paul
----- Forwarded message from Michael Opdenacker <michael.opdenacker(a)linaro.org> -----
Date: Wed, 09 Mar 2011 22:15:18 +0100
From: Michael Opdenacker <michael.opdenacker(a)linaro.org>
To: techleads(a)linaro.org
CC: Rob Coombs <rob.coombs(a)linaro.org>,
Stephen Doel <stephen.doel(a)linaro.org>, mgt(a)linaro.org,
asac(a)linaro.org
Subject: Re: LDS - Candidate list for Sponsorship (travel paid)
(mgt(a)linaro.org)
Organization: Linaro
Hi tech leads,
Did you have time about who you would like to invite at LDS, and if
needed, pay for their costs?
I added some suggestions about people who could be interesting to lock
with us for 5 days. I'm not only thinking about people from the
mainstream projects we contribute to, but also about open-source
projects who use or could use our deliverables.
See the shared document and the notes I added:
https://spreadsheets.google.com/a/linaro.org/ccc?key=0AjOUcebQ3tSidHhqdzdyb…
<https://spreadsheets.google.com/a/linaro.org/ccc?key=0AjOUcebQ3tSidHhqdzdyb…>
These were just suggestions. You decide who you would like to invite in
our working groups.
Thank you in advance,
Cheers,
Michael.
On 02/08/2011 10:05 AM, Rob Coombs wrote:
> Hi Stephen,
>
> We already have a shared document
> https://spreadsheets.google.com/a/linaro.org/ccc?key=0AjOUcebQ3tSidHhqdzdyb…
> <https://spreadsheets.google.com/a/linaro.org/ccc?key=0AjOUcebQ3tSidHhqdzdyb…>
>
> Please continue to edit this.
>
> Thanks,
>
> Rob
>
> On 8 February 2011 06:14, Stephen Doel <stephen.doel(a)linaro.org
> <mailto:stephen.doel@linaro.org>> wrote:
>
> Hi All,
>
> This list is to gather together candidates from a) the Linux
> community and b) key corporate accounts & relationships.
>
> Please can you help build the list so we can start the
> invitations. We're looking to sponsor around 10 people again, as
> an example attached is the list from Florida.
>
> I expect we'd want to start arranging invites from 21 February, so
> input before then please.
>
> Stephen
>
>
> On 2 February 2011 14:27, <rob.coombs(a)linaro.org
> <mailto:rob.coombs@linaro.org>> wrote:
>
> I've shared LDS - Candidate list for Sponsorship (travel
> paid)
> <https://spreadsheets.google.com/a/linaro.org/ccc?key=0AjOUcebQ3tSidHhqdzdyb…>
>
>
> Message from rob.coombs(a)linaro.org
> <mailto:rob.coombs@linaro.org>:
>
> Please add possible candidate names for sponsoring travel costs to LDS in May.
>
>
> Click to open:
>
> * LDS - Candidate list for Sponsorship (travel paid)
> <https://spreadsheets.google.com/a/linaro.org/ccc?key=0AjOUcebQ3tSidHhqdzdyb…>
>
>
> Google Docs makes it easy to create, store and share online
> documents, spreadsheets and presentations.
> Logo for Google Docs <https://docs.google.com/a/linaro.org>
>
>
>
>
> --
> Thx
>
> Stephen Doel
> Linaro Ltd
> Chief Operating Officer
> +44 77 66 014 247
>
>
>
>
> --
> ==========================
> Rob Coombs - Head of Global Alliances
> Linaro
> Liberty House,
> Moorbridge Rd,
> Maidenhead
> Berkshire SL6 8LT
> Direct: +44 (0) 1628 427794
> Mobile: +44 (0) 7747801576
> Email: rob.coombs(a)linaro.org <mailto:rob.coombs@linaro.org>
> www.linaro.org <http://www.linaro.org>
>
--
Michael Opdenacker - Community Manager
Linaro, http://linaro.org
Cell: +33 621 604 642
IRC: 'opm' in #linaro on irc.freenode.net
----- End forwarded message -----
== Device Tree ==
* Sent out the full support of mx51 platform dt clock for review
* Sent out esdhc-imx dt support for review
== Misc ==
* Tested linaro-media-create on mx51evk board, found and reported issues
of udisks dependency, card/reader compatibility, and proxy support
* Helped Richard reproduce and figure out the root cause of SD/MMC CRC
error regression
--
Regards,
Shawn
== Aneesh V <aneeshv> ==
=== Highlights ===
== U-Boot Cache Maintenance ==
* Sent out the v2 series
== U-Boot Thumb2 ==
* Fixed issue with weakly linked functions and Thumb2
* This issue came out when I enabled Thumb after applying
cache maintenance patches.
== Device Tree ==
* Adding support for clkdev based clock lookup for Samsung platforms.
Existing clock lookup code depends on device id in platform device and
this causes clock lookup (clk_get) to fail when booting with device
tree.
== Misc ==
* Was on leave from 1st March to 14th March.
== m-y ==
=== Highlights ===
* Patch set for DMA support in USB for U8500 is ready and is in
internal review.
* Work on bug # 709245 not started yet.
=== Plans ===
* Push DMA patch set out as soon as possible. It depends on the
outcome of internal review which is expected tomorrow. There may still
be a chance to get them in before merge window opens.
* Would like to investigate bug # 709245 but keeping it at lower priority.
Thanks,
--
Mian Yousaf Kaukab
== Jason Liu <Jasnliu> ==
=== Highlights ===
====DT====
* MX51 basic DT support: V4(use Linaro copyright and sign off )send
out hope that it's ready for Grant can get merge it.
* Investigate to add new device support with MX51 babbage board such
as I2C, GPIO, MMC, etc.
====Kernel configuration ====
* NONE
====Misc====
* MX53 LOCO board support, patch set get merged to u-boot-imx next branch:
* http://git.denx.de/?p=u-boot/u-boot-imx.git;a=shortlog;h=refs/heads/next
* Some Linaro bug fix and analysis
=== Plans ===
* DT support for mx51 babbage board and to add more device support
===Issues===
* NONE
== RCU priority boosting ==
* No progress this week due to travel and meetings
== Processes ==
* More Linaro TSC License processing
== Misc ==
* RCU patches for 2.6.39 merge window accepted into -tip
* Travel to Bangalore for upcoming TSC meeting (and lots of LTC meetings)
* Named program committee chair for Linux Plumbers Conference
== John Stultz <jstultz_vm> ==
=== Highlights ===
* Released first pass demo code of the kconfig fragments work, got some
decent feedback. Although opinion seems to be that upstream acceptance
is needed first (reasonably so), but that is likely to cause this
solution to the config work to be deferred into the next release.
* Got a panda board, and started work on bringing it up with the Linaro
Android kernel the android_omap4_defconfig.
* Published up a Linaro-Android 2.6.38 based tree:
http://git.linaro.org/gitweb?p=people/jstultz/android.git;a=summary
* My android talk got accepted at ELC.
* Got my RTC cleanups pending for 2.6.39 merged into -tip
=== Plans ===
* Sitting on a beach in Hawaii. Out of town most of next week. Should be
back on Friday
* Need to get the panda framebuffer working in the android kernel and
then publish the android_omap4_defconfig.
=== Issues ===
* May need some help prioritizing upstream push of kconfig changes vs
immediate need to help unify the current linaro board configs.
== Dave Martin <dmart> ==
=== Activity ===
==== hardware-n-kernel-standard-architecture ====
* Reposted gas adr instruction fixup workaround patch for
comment, with minor modifications as suggested by Nicolas
Pitre.
* Discussions around enabling kprobes for Thumb-2.
* Getting started on NEON/VFP registers in coredumps.
* Omap Thumb-2 patches now queued by Kevin Hilman for 2.6.39.
(git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-
omap-pm.git for_2.6.39/pm-misc)
* Thumb-2 kernel building is now enabled for OMAP, after
adding -fno-optimize-sibling-calls as a workaround for the
module loading issue encountered last week.
* Received a Genesi Efika smartbook which I will use as a
target when working on imx51 Thumb-2 support when their
2.6.35 merge becomes available: should be a useful target,
since while the linaro imx51 kernel seems to be in a good
condition with regard to Thumb-2 compatibilty, it doesn't
have a full set of drivers or full power management support
yet -- which is where Thumb-2 issues are likely to arise.
==== miscellaneous ====
* Set up an mx51evk board in the linaro validation lab. The
linaro-m release is not mature enough and is not fully
usable, due a lack of network support etc, so upgrading to a
more recent linaro snapshots kernel was needed.
=== Plans ===
* Post an RFC proposal for adding the NEON/VFP state in
coredumps.
* Try and reflash U-Boot on the validation lab u8500 boards.
* Set up the remaining Freescale boards in validation lab.
* Write up the output from the Freescale i.MX BSP review
discussion, and post for comment.
=== Issues ===
* (none)
=== Absences ===
* Mon 2011-03-14 -- Fri 2011-03-16
== Device Tree ==
* Review and test mx51 dt patch v2 from Jason
* Sent out the preview version of patch set 'dynamically adding clk per dt nodes'
== Misc ==
* Test l-m-c and report issues
--
Regards,
Shawn
Out of town Monday, then out sick most of Thursday and Friday, so not a
whole lot got done.
== Posix Alarm Timers ==
* CLOCK_BOOTTIME patches were merged into -tip by tglx for 2.6.39
* LWN Article on alarm timers was published:
https://lwn.net/Articles/429925/
* Got some good discussion in the comments going.
== Config Work ==
* Created First pass Kconfig fragments for imx51, vexpress and omap3, as
well as a distro Kconfig.
* Working to minimize the difference between the kconfig fragments and
the current Linaro config files.
== Linaro Android Kernel ==
* Synced with Jesse about shipping a Panda board to me for testing with
the Android kernel. Should be on its way.
== Linaro Misc ==
* Attended linaro technical resources kick-off meeting.
== m-y ==
=== Highlights ===
* USB works out of the box in PIO mode on U8500 since v2.6.38-rc3
* Work on DMA support is in progress.
=== Plans ===
* Continue testing/debugging DMA for USB on U8500
* Investigate bug # 709245
Thanks,
--
Mian Yousaf Kaukab
== Kernel development ==
* (hopefully) last round of BKL removal patches
* bug hunting: macvtap, omap-serial, lo
* code review: SPEAr13xx PCIe, slack timers
== Flash devices ==
* Helped out a few flashbench users
* Measured various USB flash device
* Started discussions with a PHD student who wants to
write a new flash file system