== Per Forlin <perfor> ==
=== Highlights ===
* Prepare blueprints for LDS
* K7.3 Non-Blocking Request in MMC
* K7.4 eMMC Background Maintenance
* K7.6 SDIO Single Function Support
* K7.10 DMA Engine on ARM
* K7.11 USB gadget mass storage
* Submit patch to optimize SDIO for single IRQ
* Submit patch v3 of nonblocking mmc with some minor fixes.
=== Plans ===
* Attending LDS
== Paul E. McKenney <paulmck> ==
=== Highlights ==
* Pre-Budapest specification work
* Submitted two smaller RCU-related patchsets to LKML.
* Submitted git pull request to Ingo Molnar for TREE_RCU priority boosting.
* Cheng Xu is working towards a fix to the related scheduler bug.
=== Highlights ===
* Had jury duty on weds, so was mostly out for that day.
* Met Deepak for 1:1 lunch meeting
* Lots of community bugs/issues coming out of the woodwork!
* Worked on debugging a boot-time delay seemingly caused by earlier
TSC refinement patch.
* Worked on time() bug found on P7 hardware
* Did a full audit of the rtc drivers to resolve issues with bad
initialization that was uncovered by my RTC infrastructure fixes
* Discussed methods for reducing xtime_lock contention
* Wrote up spec for Kconfig work
* Got two Alarmtimer fixes merged into -tip, worked with Thomas to
resolve some other minor alarmtimer issues.
=== Plans ===
* Spend time reviewing the pm_stay_awake/pm_relax code
* Try to adapt Arve's earlier RTC suggestions into the tree.
* Try to implement printk task_comm %P value
* Get Android Trivial branches cpufreq and cgroup sent out.
=== Issues ===
* Crazy number of community bugs taking lots of my time right now.
Hoping this calms down soon.
Hi all,
I am going through the Linaro kernel bug backlog to wrap my head
around the status of what that the kernel and landing team has been
working on. I made some simple notes for myself and want some input
from folks who've been involved longer to understand what should be
closed, what should remain open, and what should be re-prioritized
based on deliverables as we start up the 11.11 cycle so please speak
up with any thoughts. Some of these bugs have no assignees and since I
still need to figure out what everyone's availability and skill set
is, please speak up if there's a bug you are called to take.
Mounir, I think it'd be good for you and I to sit down towards the end
of LDS next week and do a review of all kernel bugs.
Starting with http://goo.gl/6k7GS - Importance field not set
645663 2.6.35-1006-linaro-omap occasional oops during boot
This was opened in September of last year on a very old kernel,
should be closed?
754247 2.6.38 halts under heavy load
This looks like it should be a medium priority bug and needs to be
reproduced
on a single board with serial console logged running latest Linaro kernel.
754248 Processes do not distribute across cores when running CoreMark
Related to WIP code for TI Panda board, needs re-testing with CPU_FREQ
disabled to validate. Importance should be low as it is a mostly known
issue and possibly needs to just be marked a dup if we already have
a bug tracking the CPU_FREQ development?
776856 uboot won't boot until running 'mmc part 0'
Needs to be tested/reproduced on latest U-Boot by John. I consider this
a low priority bug as developer's can still boot a board by running
'mmc part 0'.
Next, we have http://goo.gl/kfk7L - High and Medium priority bugs.
754254 imx51 randomly truncates serial input at 31 characters
Probably trivial to fix, just needs someone with HW to fix it.
Probably someone
from landing team?
615972 Neon registers missing in core files
In progress, patches merged into Linaro trees and headed upstream.
720055 CONFIG_OMAP2_DSS_SDI on OMAP4 causes...
Issue is resolved in linux-linaro-omap. Does it need to be pulled
into Nicolas'
tree to close out the linux-linaro component?
754254 imx51 randomly truncates serial input at 31 characters
Needs to be assigned to someone, likely in the Freescale Landing Team?
615974 Interrupted system call handling
Patch is in Linaro tree, needs submitting to RMK's patch system.
660639 twl driver failed to transfer msgs etc
Patch has been submitted upstream by Andy that possibly fixes the issue
but needs to be retested by Tom, original submitter and then likely added
to Linaro kernel tree if not already merged.
709245 panda: USB disk IO slow
Was assigned to Mian, will re-assign to Venkat.
712025 asoc: interface omap-mcbsp-dai hw params failed
Patch sent upstream, needs merging into Linaro kernel.
712175 OMAP Beagle C4: kernel does not reliably find SD card on boot
No update since April 04, probably want to retest on latest kernel.
717677 wifi is not recognized in latest netbook image on IGEP v2
No update since March 21st. Does this need testing on latest kernel?
762026 Problem with SMP IRQ affinity
Known issue, needs an assignee to fix.
768680 Boot does not complete on IGEP with Device Tree
Currently assigned to Grant. Grant, do you have time to dig into this or
should we reassign to someone else with access to HW?
Without device_type property set as memory for the node, the generated
dtb can still work when it gets passed to kernel by u-boot, since
u-boot will fix it up. But kernel will not boot due to that it fails
to parse the memory node, when the dtb is appended to kernel image as
it is.
The patch adds a property device_type="memory" for memory node to fix
the problem.
Signed-off-by: Shawn Guo <shawn.guo(a)linaro.org>
---
It applies on branch devicetree/test.
arch/arm/boot/dts/babbage.dts | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/babbage.dts b/arch/arm/boot/dts/babbage.dts
index 8f9b47c..4805168 100644
--- a/arch/arm/boot/dts/babbage.dts
+++ b/arch/arm/boot/dts/babbage.dts
@@ -21,6 +21,7 @@
interrupt-parent = <&tzic>;
memory {
+ device_type = "memory";
reg = <0x90000000 0x20000000>;
};
--
1.7.4.1
On Mon, Apr 04, 2011 at 10:54:00PM -0600, Grant Likely wrote:
> On Fri, Apr 01, 2011 at 03:49:16PM +0800, Shawn Guo wrote:
> > On Thu, Mar 31, 2011 at 10:09:40AM -0600, Grant Likely wrote:
> > > On Fri, Mar 25, 2011 at 03:13:58PM +0800, Shawn Guo wrote:
> > > > After fec dt support is added, the following compile error will be
> > > > seen when building a pure non-dt kernel.
> > > >
> > > > drivers/net/fec.c: In function ‘fec_probe’:
> > > > drivers/net/fec.c:1383: error: implicit declaration of function ‘of_match_device’
> > > > drivers/net/fec.c:1383: warning: assignment makes pointer from integer without a cast
> > >
> > > Earlier today I suggested fixing this by adding an empty
> > > implementation of of_match_device, but I forgot that an .of_match
> > > pointer has been added to struct device for exactly this purpose. You
> > > can use that instead.
> > >
> > > That change is currently in mainline, but it has not been backported
> > > to the Linaro 2.6.38 tree (yet).
> > >
> > This simply is a fix to commit 54898b86fa9813313b3eb981c44610ff483b0067
> > "net/fec: add device tree matching support", which only sits on branch
> > devicetree/test-2.6.38 right now. However, .of_match is not available
> > on that tree yet. So I can not do anything until ether this patch
> > shows on devicetree/test or .of_match is back ported on
> > devicetree/test-2.6.38. Or you can simply ignore this patch since I
> > just want let you know such a compile error.
>
> Okay, of_match is in my devicetree/test branch now since I've rebased
> to 2.6.38-rc1. I'll happily take a fixup patch from you now. :-)
>
Sorry, Grant. I overlooked this reply, and noticed it when re-visiting
the thread today. I just sent an updated patch. Please take a look.
--
Regards,
Shawn
Andy Green has worked on a set of patches adding many features to OMAP4
such as HDMI audio/video, FM receiver, etc. Before I merge that into
the Linaro kernel tree I need some assurance that this won't break
existing OMAP3 support, especially video. The branch is available in
the linux-linaro-2.6.38 Git repository on git.linaro.org, in the
"testing" branch.
So please if you have an OMAP3 board and can perform some testing that
would be appreciated.
Nicolas
Hi,
Probably most of you are aware of LTTng since it is already integrated
in Linaro's kernel, in this session I will focus on the new LTTng
patchset which has the following characteristics :
1) The size of the kernel patchset has been shrinked for Linux
distributions by removing all LTTng-specific instrumentation from the tree.
2) The lttng-modules package now implements an ABI based on anonymous
file descriptors (inspired from perf) rather than the full-blown VFS
tree the previous LTTng versions were implementing.
3) lttng-modules now exports trace data and metadata in the CTF (Common
Trace Format).
4) lttng-modules now uses the Generic Ring Buffer Library.
LTTng will probably not enter in the Oneiric Ubuntu kernel, but our
target is to upstream most of our patches before the next LTS.
The purpose of this session is :
- to show the benefit developers and sysadmins have with LTTng
kernel and userspace tracers for debugging and QA;
- to highlight the main differences between the current stable LTTng and
this new patchset and the new tools associated with it;
- to find a way to test LTTng in Oneiric to have something rocking in
the next LTS.
The session will be held in room Jozsef on Wednesday 11th between 12:00
and 13:00, the blueprint associated is here :
https://blueprints.launchpad.net/ubuntu/+spec/other-o-lttng
Thanks,
Julien
Hello all,
I want to introduce myself to the linaro-kernel and linaro-dev lists as I
just started at Linaro today in the role of Kernel Working Group Technical
Lead and will be working closely with all of you on enhancing the ARM Linux
ecosystem. I've been using Linux since 1993 and working with the Linux
kernel for over 10 years for a variety of companies including silicon
vendors, OSVs, and device vendors with a broad variety of experience
including ARM CPU and board bring up, hacking on a variety of device
drivers, maintaining a distro kernel, maintaining a few ARM
sub-architectures, educating HW vendors and new developers about the open
source development model, etc. I've been a bit out of the loop of the open
source community the last 1-2 years and am really excited to be involved
with Linaro working on community-focused technology enablement and
enhancement.
I expect this first week to be mostly focused on reading up on process,
existing deliverables, mailing list archives, etc to wrap my head around
where we are right now and where we're headed with the 11.11 release. I'll
be at LDS and look forward to meeting many of you next week and I want to
encourage anyone who won't be at LDS but has concerns, ideas, questions
related to the kernel WG to drop me an email.
Thanks!
~Deepak
Hello!
A call for hardware needs -- please speak now or hold your peace for
another cycle.
Thanx, Paul
----- Forwarded message from James Westby <james.westby(a)linaro.org> -----
Date: Fri, 29 Apr 2011 18:01:18 -0400
From: James Westby <james.westby(a)linaro.org>
To: techleads(a)linaro.org
Subject: LDS: hardware requirements for next cycle
Hi,
I'm organising a session at LDS to collate and prioritise hardware needs
across Linaro.
https://blueprints.launchpad.net/linaro/+spec/linaro-other-o-hardware-needs
If your team needs some hardware that isn't currently ordered then
either come along to the session, or email me beforehand, and tell me:
* What hardware you need (type, quantity)
* When you need it by
* What you need if for (i.e. what won't be able to happen if you don't
have it)
We'll then be able to use this to come up with a shopping list that we
can request hardware from, and balance priorities if we can't have
everything.
If the request is already on the Hardware wiki page then you don't need
to re-send it.
Also, this isn't to say that if you don't mention it now you can't have
it, but it will be helpful to have a comprehensive snapshot of the
requirements before the session.
Thanks,
James
----- End forwarded message -----
