Hello,
We were using kernel 2.6.35 for omap4 (blazeboard), and tiler memory is
tested using tiler-userspace tests (tiler_tests, memmgr_ptest and
utils_test). Few tests were successfully executed.
We need to test tiler on kernel-3.4, We ran tiler-userspace (branch
memmgr_2.0) tests.
It got failed with error: "TilerMgr_Open: No such file or directory".
Can I get some pointers/links for tiler-userspace, tests?
Thanks and Regards
Manju
== Highlights ==
* Finished versioned tracing, version tag is now written into the PRZ
signature. The idea didn't cause any objections, so I guess it
should be OK for merge. There is a minor (cosmetic) comment from
Steven, which I'll fix and resend the series on Monday;
* Finished most of the work on FIQ debugger. There is some positive
feedback from Colin Cross, although the bad news is that the FIQs are
"broken" on the new HW because of the hypervisor, so the debugger is
useless on newest ARM SOCs.
Although, it's still useful for ARMv6 SOCs, and for ARMv7 HV issue
might be fixed in the future, plus part of the patches are
useful for non-ARM as well (i.e. any arch that might want to invoke
the debugger from an NMI);
== Plans ==
* Make KDB console [optionally] async, and resend the FIQ/KDB patches,
ask for merge;
* Yet again resend pstore patches that didn't make it into -next;
* Return to vmevents or pick another task?
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
=== Highlights ===
* Watched a number of Google IO talks. Most interested in the the
systrace tool. From initial research, it seems Jelly Bean is actually
going to be based on an updated 3.0 kernel (same as ICS), meaning the
3.4 based kernels (including the merged wakelocks and other upstreamed
features) won't likely be used until the Oct phone release. This may
cause some pain for Linaro as changes in the 3.4 based kernel require
some new userland improvements, which likely won't be available till
after Oct.
* Sent out updated volatile range v5 iteration. Still not much feedback.
After some private discussion w/ Dave Hansen I'm looking into
implementing something closer to Minchan's suggestion of a separate LRU
for volatile pages. Got it sort of half working right now, and hope to
sort things out soon.
* LinusW reviewed the ETM patches. Had a number of suggestions for
changes, including increased documentation. I'll be looking at trying to
address those concerns, and resubmitting soon.
* Finished newsletter update
* Sent out weekly android-usptreaming email.
=== Plans ===
* Debug current LRU_VOLATILE work and hopefully get a early rough draft
sent to lkml
* Spend some time learning more about ETM functionality and try to make
use of it so I can have some context with which to write documentation
* Ping Google devs (likely at Google IO this week) about the mmc
wakelock changes
=== Issues ===
GAH! HOW DID IT GET TO BE JULY ALREADY!?
==== Activity Summary ====
* Completed DT binding on btemp and fuel guage driver with documentation
- Obtained review comments from lee jones
* Got the battery interface ready for Snowball V11 board
- Board is booting with external battery power
- Currently using "Sonyericsson BST41" Battery type for testing
* Observed kernel crash at gpadc call with battery interface on first
iteration of testing
==== Plan ====
* Work on review comments
* Complete the testing and bug fix of btemp and "fuel guage" driver
using battery interface
==== Issues ====
2012-07-05 : I will be on leave
