== Saugata Das sdas ==
=== Activity Summary ===
* Context ID patch internal review ongoing
* Reviewed packed command implementation
* Reviewed power OFF notify implementation
* Reviewed UFS driver implementation
* Brought up Samsung MMC-4.5 JIG on 8500 board
(Restriction: Only works in one bit mode due to the limitation imposed
by the micro-SD/SD bridge I am using. It does not stop me from
validation of features)
=== Plans ===
* Porting of SBC command support on mmci.c
* Validation of context ID, tag and packed command
* Submission of context ID patch
=== Issues ===
* Due to personal unavoidable reasons, I will return from Connect on 8th Feb
(I'm aware that there is a thread on linaro-dev discussing this exact
topic; this is a request for specific information, so I decided to start
a new thread)
Hello,
As has been pointed out elsewhere, it is very difficult to find
the exact git tree that corresponds to a kernel release. Currently the
problem I am having is that the 11.11 linaro kernel release
(linux-linaro-lt-omap_3.1.0-1402.5~oneiric1) works well on my new board,
but later kernels do not. While I can download the kernel tarball for
3.1.0-1402.5 from launchpad, I would much prefer to use the git tree
that it was produced from. Can anybody tell me exactly which git tree
was used to create that kernel, and which tag/branch I should be looking at?
Thanks,
--
Chris Lalancette
== Completed Work Items ==.
- Had to familiarize myself with Android internals and build process,
i.e. set up build environment, actually build a working Android image
from scratch (through quite a bit of hardships, heh). But now I'm
actually able to customize Android from the kernel down to the
userland. :-) Surely I played a bit with all this new stuff.
That might a good question whether I should actually mess with the
userland, but I think that familiarizing w/ Android internals is a
good thing even for a Linux kernel guy, especially as I'm going to
work on Android-related projects.
And this is all was to start preparing changes for ActivityManager
(i.e. add support for memory notifications).
- Started looking into interactive cpufreq governor. I forward-ported
it onto latest kernels, and again played a bit with it. The bad news
is that the governor depends on idle notifiers (notifiers, again :-)
And the notifiers are got a somewhat cool welcome by some ARM folks.
( http://lkml.org/lkml/2011/6/27/391 )
So, might be a good idea to reiterate the notifiers and cpufreq stuff
soon. But need to spend a bit more time on the code, so that I would
feel confident what exactly I'm going to defend.
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
The Linaro Kernel Working Group (KWG) is excited to announce the
availability our January 2012 development snapshot:
linux-linaro-3.2-2021.01-0
As the word "snapshot" implies, these are meant as development kernels
and have not been fully validated. You should expect issues and to help
us deliver a better kernel in the future, please file bugs in Launchpad at
https://bugs.launchpad.net/linux-linaro.
This is our first kernel release run by Andrey Konovalov and I want to
thank him for getting up and running in short time period and getting
this release out the door. Andrey will be creating a 3.3 tracking branch
soon and we can then start merging code from the other WGs and LTs to
provide a common baseline for the 2012.02 release.
The source tarball is available at:
http://launchpad.net/linux-linaro/3.2/3.2-2012.01/+download/linux-linaro-3.…
The kernel sources can also be accessed using git at:
git://git.linaro.org/people/ynk/linux-linaro-tracking.git
tag: linux-linaro-3.2-2012.01-0
This kernel includes the following changes from the 2011.11 kernel:
- Update to 3.2.1 stable kernel
- Various patches from 3.3-rc1 and other trees:
- Restart code cleanup (Russell King)
- Config fragment support (John Stultz)
- Pinctrl updates (Dong Aishang, Rajendra Nayak, Linus Walleij)
- Thermal cpu cooling branch from PMWG (Amit Kacchap, Jaecheol Lee)
- LPAE support (Catalin Marinas)
- MULTI_IRQ_HANDLER support (Marc Zyngier)
- ioremap() consolidation (Nicolas Pitre)
A full change log against the 3.2.1 release is available at:
http://launchpad.net/linux-linaro/3.2/3.2-2012.01/+download/CHANGELOG-linux…
High Priority Known Issues:
- None at this time
Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-dev
Questions? https://ask.linaro.org/
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Caught up on most of pre-holiday emails
* Worked up updating and cleaning up KWG blueprints for 12.01 work
* Connect session planning
* Lots of meeting catching up with folks and planning for 2012.
=== Plans ===
* Release 12.01 kernel
* 12.02 planning
* Work on kernel wiki page updates
* Finish up connect session registration
* Cleanup remaining unfinished KWG roadmap cards
* 1-on-1's, sub-team meetings
=== Travel/Time Off ===
* Connect + ELC 02/04-02/20
 (Taking the Train from Portland  -> Oakland on 02/03 afternoon.
Taking days between
 Connect and ELC as semi-time off, will still be responding to
emails but will mostly
 be exploring around the bay area. Taking train back on 12/19 evening, back
 to work Monday 12/20 afternoon).
* Discussion to generalize the maintenance process of kernel branches
> for the periodic Linaro releases. This still needs documenting in the
> wiki.
>
> * Merged a set of patches put together by Anand Gadiyar to add display
> support to the PandaBoard.
>
> * Merged the following additional patches:
>
> * d983450 cpufreq: Add documentation for sampling_down_factor
> * 054fcd5 ARM: S5P: Fix end address in memory resource information for UART devices
> * bf47520 ARM: make SWP emulation explicit on !CPU_USE_DOMAINS
> * 459967a ARM: fixup SMP alternatives in modules
> * 7144fbc ARM: 6654/1: perf/oprofile: fix off-by-one in stack check
> * 067dfdf ARM: 6659/1: Thumb-2: Make CONFIG_OABI_COMPAT depend on !CONFIG_THUMB2_KERNEL
> * cc0f308 ARM: 6656/1: hw_breakpoint: avoid UNPREDICTABLE behaviour when reading DBGDSCR
> * 40ef21c ARM: 6657/1: hw_breakpoint: fix ptrace breakpoint advertising on unsupported arch
> * 9e97118 ARM: ptrace: remove single-step emulation code
>
== Upstream oriented activities ==
* Review of Arnd Bergmann's flash card article for LWN.
* Incorporation of feedback to the patch adding Thumb2 support to the
P2V branch.
* Another look at the Thumb-2 compatibility fixes for OMAP from Dave
Martin.
* Review of a patch series adding support for SDHCI v3.00.
* Posted patches:
* Rework of the kernel decompressor code to improve efficiency
* Removal of the 4x expansion presumption while decompressing the kernel
* kprobes insn decoding fix
* Ignore mdesc->boot_params if out of range
* Fold lookup_machine_type() into setup_machine()
== Linaro kernel activities ==
* Looked at some bugs:
* Bug 660811
* Bug 720055
* Merged 2.6.37.1 into linaro-2.6.37
* Merged Dave Martin's Thumb2 compatibility patches for OMAP.
* Merged core ARM ffixes from RMK.
* Merged OMAP fixes from Tony Lindgren.
* Opened up the linaro-2.6.38 branch.
Nicolas
=== Highlights ===
* Input evdev timestamp patch was merged in maintainer's tree and queued
for 3.4
* merge_config.sh script that handles config fragments was merged into
3.3!
* Got my Linaro Connect flight/hotel booked.
* Spent most of the time working on range-tree implementation for the
fadvise volatile code. Managed to get insert/delete/lookup working &
also added splay-tree style self-balancing. Think I've knocked out the
obvious bugs, so now just have lots of testing to do. Also pinged akpm
on his thoughts, but didn't get much insight there, other then he wants
to be able to use it for posix file locking. Not 100% sure it will easy
to generically abstract it out.
* Ran email meeting for android kernel subteam
* Synced w/ Deepak
* Very brief review of Dmitry Antipov's usleep_range patch.
=== Plans ===
* Likely more IBM internal assistance on customer issue
* More testing of range-tree implementatoin in userland
* Integration of range-tree idea into kernel space and fadvise work
* Review posix file locking code and determine if range-trees can be
used there.
* Maybe send out alarmtimer work for staging? This has been on my plans
for way too long!
=== Issues ===
* I've been requested to help with an internal customer issue. This has
taken a little bit of time this week, but will likely spill into the
weekend and next week as well.
== Linus Walleij linusw ==
=== Highlights ===
* Posted a second iteration of the pin states patch,
which tied configuration to the driver, so the driver
would declare a number of configration states to
be activated by name. I start to think this approach
may be bad, so:
* Prepared a second alternative to pin configuration,
instead of driver-declared states, we provide a set
of named states in the platform data, maybe we will
tie this into the device as well so devices can request
pin states. Need to read feedback and iterate this
patch set.
* Rebasing my development trees to v3.3-rc1
* Reviewed different patches here and there. Sent
some sporadic U300 and Integrator patches.
* Helped our ALSA SoC guy play audio on the
mainline kernel - it works! So now patches for
the AB8500 ALSA SoC driver are in the works.
=== Plans ===
* Harvest and send patches upstream for -rc1 which is
usually pretty busy. pinctrl and ux500 alike.
* dummy pinmuxes akin to dummy regulators, we need
to see if this is a good idea or not.
* Prepare conference presentation for the
Embedded Linux Conference.
* Drive generalization of Nomadik GPIO
by using the pinctrl framework.
drivers/gpio/gpio-nomadik.c
* Test the PL08x patches on the Ericsson Research
PB11MPCore and submit platform data for using
pl08x DMA on that platform.
* Look into other Ux500 stuff in need of mainlining...
like
- Ux500 clocks
- the HWMON stuff.
=== Issues ===
* Ux500 mainlining having second priority.
Thanks,
Linus Walleij
Hi -
Andrey has made a nice new branch "linux-linaro-tracking" with some
"nexty" goodies in it
http://git.linaro.org/gitweb?p=people/ynk/linux-linaro-tracking.git;a=short…
I rebased tilt-tracking on top of it at v3.2 basis at the moment.
Quite early in boot, it blows a new BUG() in the code around
iotable_init(), I added some debug and see it's blowing up when trying
to define io memory in omap_barriers_init(). A bunch of earlier
machine-defined iotable_inits go OK.
[ 0.000000] iotable_init: adding addr=DA000000 size=02000000
phys_addr=9A000000
[ 0.000000] iotable_init: adding addr=F8000000 size=00100000
phys_addr=44000000
[ 0.000000] iotable_init: adding addr=FC000000 size=00400000
phys_addr=4A000000
[ 0.000000] iotable_init: adding addr=F9000000 size=00100000
phys_addr=50000000
[ 0.000000] iotable_init: adding addr=FD100000 size=00100000
phys_addr=4C000000
[ 0.000000] iotable_init: adding addr=FD200000 size=00100000
phys_addr=4D000000
[ 0.000000] iotable_init: adding addr=FD300000 size=00100000
phys_addr=4E000000
[ 0.000000] iotable_init: adding addr=FA000000 size=00400000
phys_addr=48000000
[ 0.000000] iotable_init: adding addr=FE800000 size=00800000
phys_addr=54000000
...
[ 0.538024] omap_barriers_init: calling iotable_init
[ 0.543243] iotable_init: adding addr=FE600000 size=00100000
phys_addr=AF600000
[ 0.550872] ------------[ cut here ]------------
[ 0.555725] Kernel BUG at c087c74c [verbose debug info unavailable]
[ 0.562255] Internal error: Oops - undefined instruction: 0 [#1]
PREEMPT SMP
[ 0.569610] Modules linked in:
[ 0.572845] CPU: 1 Tainted: G W
(3.2.0-panda_tracking-topic-syslink-k3u+ #6)
[ 0.581451] PC is at vm_area_add_early+0x20/0x84
[ 0.586303] LR is at iotable_init+0xa8/0xbc
[ 0.590698] pc : [<c087c74c>] lr : [<c086cd48>] psr: 20000113
[ 0.590698] sp : ef78ff54 ip : ef78fe10 fp : 00000000
[ 0.602691] r10: c086cca0 r9 : 00000000 r8 : 40000001
[ 0.608154] r7 : ef7ffee0 r6 : ef78ff90 r5 : ef7ffec0 r4 : 00000001
[ 0.614959] r3 : 00000001 r2 : 00000000 r1 : 00000001 r0 : ef7ffec0
[ 0.621765] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM
Segment kernel
[ 0.629394] Control: 10c5387d Table: 8000404a DAC: 00000015
[ 0.635406] Process swapper/0 (pid: 1, stack limit = 0xef78e2f8)
[ 0.641662] Stack: (0xef78ff54 to 0xef790000)
[ 0.646240] ff40:
00000001 00000000 af600000
[ 0.654754] ff60: c09299e0 ef78e000 00000000 00000000 c0870f8c
c0871070 c08d7f9c c08a7bf8
[ 0.663269] ff80: fe600000 000af600 00100000 0000000e c08a7bfc
c0008870 0000009f c009f590
[ 0.671783] ffa0: 0000009f c0870f8c c0014640 00393531 00000000
c0150000 00000000 c08e5604
[ 0.680297] ffc0: 0000019a c08a7bfc c08a842c c0014640 00000013
00000000 00000000 00000000
[ 0.688812] ffe0: 00000000 c08668bc 00000000 00000000 c0866830
c0014640 55555555 45515555
[ 0.697326] [<c087c74c>] (vm_area_add_early+0x20/0x84) from
[<00000000>] ( (null))
[ 0.705322] Code: 059f3068 01a0c003 05933000 0a000010 (e7f001f2)
[ 0.711700] ---[ end trace 1b75b31a2719ed1d ]---
[ 0.716552] Kernel panic - not syncing: Attempted to kill init!
[ 0.722747] CPU0: stopping
[ 0.725646] [<c001a930>] (unwind_backtrace+0x0/0xf8) from
[<c0018cf8>] (handle_IPI+0x114/0x140)
[ 0.734710] [<c0018cf8>] (handle_IPI+0x114/0x140) from [<c00086c0>]
(gic_handle_irq+0x88/0xac)
[ 0.743682] [<c00086c0>] (gic_handle_irq+0x88/0xac) from [<c05fa0c0>]
(__irq_svc+0x40/0x70)
[ 0.752380] Exception stack(0xc08adf70 to 0xc08adfb8)
[ 0.757659] df60: ffffffed
00000000 c08adfb8 00000000
[ 0.766174] df80: c08ac000 c0929aa8 c0603f50 c08c9bd8 c08c9d98
412fc09a 00000000 00000000
[ 0.774688] dfa0: 00000000 c08adfb8 c00146bc c00146c0 60000013 ffffffff
[ 0.781616] [<c05fa0c0>] (__irq_svc+0x40/0x70) from [<c00146c0>]
(default_idle+0x24/0x28)
[ 0.790130] [<c00146c0>] (default_idle+0x24/0x28) from [<c001493c>]
(cpu_idle+0xfc/0x11c)
[ 0.798645] [<c001493c>] (cpu_idle+0xfc/0x11c) from [<c08667e0>]
(start_kernel+0x260/0x2b0)
[ 0.807342] [<c08667e0>] (start_kernel+0x260/0x2b0) from [<80008044>]
(0x80008044)
You can see what's going on in omap_barriers_init() here:
http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=blob;f…
Does anyone have an idea why pulling in the new stuff in Andrey's tree
would provoke this problem? There's a lot of stuff around device tree
but I now rebuild the dtb every kernel build, so it shouldn't be that
what's in there is out of date.
There's also stuff from rmk-devel-stable.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
