Calendar Week 45: Here is test result summary for Linaro ubuntu image on
following boards:
1) ARM Versatile Express A9;
2) Samsung Origen;
3) TI Panda Board 4430;
4) TI Panda Board 4460.
Synopsis: No change on feature status for vexpress A9 and Panda 4460. For
Samsung Origen, Unity 3D and hardware acceleration need to be double
checked next week; Audio works on Panda 4430.
1. vexpress A9 + ubuntu (Column AG):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV…
Features' status is exactly same as previous week. Device Tree and video
playback are still unavailable.
2. Origen + ubuntu (Column AB):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEowN…
Unity 3D and hardware acceleration feature will be double checked in next
week. WiFi, Bluetooth, HDMI and Video Playback are still unavailable.
3. Panda 4430 + ubuntu (Column AD):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Audio works. Dead lock error still exists in boot log, and the issues still
exist in power management and Bluetooth. All other features remain the same
status.
4. Panda 4460 + ubuntu (Column AC):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Exactly same status as previous test result. Audio input is unavailable and
dead lock error exists in boot log, although no significant effect to
system.
For the previous week (Calendar week 43) summary, please refer to
attachment.
Thank you.
Best Regards
Botao Sun
Dear Yamil,
Thank you so much for your interest in Linaro. I am forwarding your
question to our DevPlatform team Tech Lead, Ricardo Salveti and I am also
CC'ing our Linaro Dev mailing list.
Ricardo and those on the mailing listing list, thank you in advance for any
assistance that you can give Yamil.
Yamil other helpful resources should you have future questions are our
mailing lists and IRC channels:
http://www.linaro.org/engineering/mailing-listshttp://www.linaro.org/engineering/getting-started/discuss#tab2
You can also find other helpful support and discussion channels on the
Linaro Website at:
http://www.linaro.org/engineering/getting-started/discuss
Again thank you for your interest in Linaro and I hope you find these
resources helpful.
Please feel free to let me know if there is anything else I can assist you
with in regards to Linaro Technical Resources or Getting Started in the
Linaro Community.
All the best,
Amber Graner
On 9 November 2012 13:48, Linaro Content Management System <
linaro(a)freshleafmedia.co.uk> wrote:
> **
> Linaro Website Form Submission - *Contact Form*
> A user has submitted the following information on the Linaro website:
>
> Name Yamil Garcia Email ygarcia(a)imagikcorp.com Message I'm using a
> i.MX6Q Sabre Lite Board running a kernel and rootfs from
> linaro-12.09(Ubuntu-12.04) release. I would like to cross compile Qt
> applications for this board, could you guys give me a hint on this? I've
> been trying without successs. Thanks for your support. Form Url
> http://www.linaro.org/contact
>
> This enquiry was received via the *Contact Form* on the website:
> http://www.linaro.org/contact
>
> Thank you,
>
> Linaro
>
--
Amber Graner
User Experience and Community Specialist
Linaro.org <http://www.linaro.org/>* **│ *Open source software for ARM SoCs*
***
Follow *Linaro: *Facebook <http://www.facebook.com/pages/Linaro> |
Twitter<http://twitter.com/#%21/linaroorg>
| Blog <http://www.linaro.org/linaro-blog/>
*+1.828.582.9469* cell
*+1.828.395.1049* office
irc: akgraner
amber.graner(a)linaro.org (email and Google chat)
Hi Geert,
On Fri, Nov 02, 2012, Geert Schuring wrote:
> Could you tell me if you have any plans to enable Ubuntu on the Raspberry Pi
> (ARMv6) ?
Short answer: an Ubuntu ARMv6 port for the Raspberry Pi isn't a Linaro
target, but we're taking patches and we're interested in some bugs! :-)
There are two main reasons for that:
- Linaro doesn't have the capacity to do large scale distro ports, this
is usually mainly the job of distros, and we're sometimes giving a
hand
- Linaro is all about the future of ARM, so the focus is mainly on ARMv7
and ARMv8 at this point
That said, there is hope! First, a bunch of Linaro folks have a
Raspberry Pi and play with it; second, I believe Ubuntu's armel port is
being re-targeted to ARMv5, so Ubuntu armel binaries should eventually
run on the Pi.
Linaro does directly care about toolchain regressions you might
encounter on ARMv5/ARMv6 (or even on x86), so please do report us any
toolchain regressions caused by Linaro patches.
Cheers,
--
Loïc Minier
From: "hongbo.zhang" <hongbo.zhang(a)linaro.com>
Hi all,
This patch set is to upstream ST-Ericsson thermal driver and fix some bugs
of thermal layer at the same time.
All of these patches are based on v3.7-rc1.
[PATCH 1/5] Thermal: do bind operation after thermal zone or cooling
device register returns.
In the previous bind function, cdev->get_max_state(cdev, &max_state) is called
before the registration function finishes, but at this moment, the parameter
cdev at thermal driver layer isn't ready--it will get ready only after its
registration, so the the get_max_state callback cannot tell the max_state
according to the cdev input.
This problem can be fixed by separating the bind operation out of registration
and doing it when registration completely finished.
There is no such problem with the current exynos thermal driver because it
regsters cooling device before thermal zone device. As a generic thermal layer
any sequence should be supported, thermal zone first or cooling device first,
this will be also helpful to add/remove cooling device dynamically.
[PATCH 2/5] Thermal: add indent for code alignment.
[PATCH 3/5] Thermal: fix empty list checking method.
[PATCH 4/5] Thermal: make sure cpufreq cooling register after
cpufreq driver
Bug fix for generic cpufreq cooling layer as described in the commit logs.
[PATCH 5/5] Thermal: Add ST-Ericsson db8500 thermal dirver.
This patch is to add ST-Ericsson into the latest kervel version.
hongbo.zhang (5):
Thermal: do bind operation after thermal zone or cooling device
register returns.
Thermal: add indent for code alignment.
Thermal: fix empty list checking method.
Thermal: make sure cpufreq cooling register after cpufreq driver
Thermal: Add ST-Ericsson db8500 thermal dirver.
arch/arm/boot/dts/dbx5x0.dtsi | 11 +
arch/arm/configs/u8500_defconfig | 4 +
arch/arm/mach-ux500/board-mop500.c | 73 ++++
drivers/thermal/Kconfig | 20 ++
drivers/thermal/Makefile | 2 +
drivers/thermal/cpu_cooling.c | 19 +-
drivers/thermal/db8500_cpufreq_cooling.c | 118 +++++++
drivers/thermal/db8500_thermal.c | 507 +++++++++++++++++++++++++++
drivers/thermal/thermal_sys.c | 86 +++--
include/linux/platform_data/db8500_thermal.h | 39 +++
10 files changed, 847 insertions(+), 32 deletions(-)
create mode 100644 drivers/thermal/db8500_cpufreq_cooling.c
create mode 100644 drivers/thermal/db8500_thermal.c
create mode 100644 include/linux/platform_data/db8500_thermal.h
--
1.7.11.3
On Thu, Nov 8, 2012 at 2:07 PM, Viresh Kumar <viresh.kumar(a)linaro.org> wrote:
> Hi guys,
>
> Sorry if i am on the wrong list :(
Probably a linaro-dev question.
> I found it hard to log on to ask.linaro.org to see if i can answer some queries.
> Or even to ask some queries.
You should be able to use your launchpad id. e.g. for me the openid
url is launchpad.net/~amitk
> I would love to have a mail + mailing-list interface for it. Please point me to
> one if available.
ask.linaro.org is a stackoverflow Q&A interface. There is no mailing
list interface to stackoverflow.
The discussion about having different cpus on the system with
different latencies bring us to a first attemp by adding a
pointer in the cpuidle_device to the states array.
But as Rafael suggested, it would make more sense to create a
driver per cpu [1].
This patch adds support for multiple cpuidle drivers.
It creates a per cpu cpuidle driver pointer.
In order to not break the different drivers, the function cpuidle_register_driver
assign for each cpu, the driver.
The multiple driver support is optional and if it is not set, the cpuide driver
core code remains the same (except some code reorganisation).
I did the following tests compiled, booted, tested without/with CONFIG_CPU_IDLE,
with/without CONFIG_CPU_IDLE_MULTIPLE_DRIVERS.
Tested on Core2 Duo T9500 with acpi_idle [and intel_idle]
Tested on ARM Dual Cortex-A9 U8500 (aka Snowball)
V1 tested on Tegra3 and Vexpress TC2
[1] http://www.spinics.net/lists/linux-acpi/msg37921.html
Changelog:
V2:
* fixed sysfs output : /sys/devices/system/cpu/cpu[0-9]/driver/name
* fixed ifdefs in driver.c
* fixed register_driver function loop when unregistering
* removed WARN under spinlock
* fixed changelog for patch [2/4]
* changed cpuidle_get_cpu_driver function parameter
* removed cpuidle_for_each_driver function
* replaced smp_processor_id() by get_cpu/put_cpu
V3:
* refreshed patchset
Daniel Lezcano (4):
cpuidle: move driver's refcount to cpuidle
cpuidle: move driver checking within the lock section
cpuidle: prepare the driver core to be multi drivers aware
cpuidle: support multiple drivers
drivers/cpuidle/Kconfig | 9 ++
drivers/cpuidle/cpuidle.c | 36 +++++---
drivers/cpuidle/cpuidle.h | 4 +-
drivers/cpuidle/driver.c | 209 ++++++++++++++++++++++++++++++++++++++------
drivers/cpuidle/sysfs.c | 174 ++++++++++++++++++++++++++++++++++++--
include/linux/cpuidle.h | 8 ++-
6 files changed, 388 insertions(+), 52 deletions(-)
--
1.7.5.4
From: "hongbo.zhang" <hongbo.zhang(a)linaro.com>
V3->V4 Changes:
1. In previous patch set V3 "Fix thermal bugs and Upstream ST-Ericsson thermal
driver", there were 5 patches in total, since the first 3 for fixing thermal
layer bugs have been accepted by the maintainer, I'd like to send out the
updated last 2 only this time, for upstreaming ST-Ericsson thermal driver.
2. In patch "Thermal: Add ST-Ericsson DB8500 thermal driver"
- typo in commit message: diver -> driver;
- add more explanation of device tree properties are optional or required.
- in function db8500_thermal_match_cdev: remove cdev_name, use
trip_points->cdev_name[i] directly instead;
- in function db8500_cdev_bind: move cdev->ops->get_max_state(cdev,
&max_state) out of for loop to call it only once;
- in function db8500_thermal_parse_dt: update checking strlen(tmp_str) >=
THERMAL_NAME_LENGTH
- add Reviewed-by: Viresh Kumar <viresh.kumar(a)linaro.org>
- add Reviewed-by: Francesco Lavra <francescolavra.fl(a)gmail.com>
3. In patch "Thermal: Add ST-Ericsson DB8500 thermal properties and platform
data"
- add Reviewed-by: Viresh Kumar <viresh.kumar(a)linaro.org>
hongbo.zhang (2):
Thermal: Add ST-Ericsson DB8500 thermal driver.
Thermal: Add ST-Ericsson DB8500 thermal properties and platform data.
.../devicetree/bindings/thermal/db8500-thermal.txt | 44 ++
arch/arm/boot/dts/dbx5x0.dtsi | 14 +
arch/arm/boot/dts/snowball.dts | 31 ++
arch/arm/configs/u8500_defconfig | 2 +
arch/arm/mach-ux500/board-mop500.c | 64 +++
drivers/thermal/Kconfig | 20 +
drivers/thermal/Makefile | 2 +
drivers/thermal/db8500_cpufreq_cooling.c | 108 +++++
drivers/thermal/db8500_thermal.c | 530 +++++++++++++++++++++
include/linux/platform_data/db8500_thermal.h | 38 ++
10 files changed, 853 insertions(+)
create mode 100644 Documentation/devicetree/bindings/thermal/db8500-thermal.txt
create mode 100644 drivers/thermal/db8500_cpufreq_cooling.c
create mode 100644 drivers/thermal/db8500_thermal.c
create mode 100644 include/linux/platform_data/db8500_thermal.h
--
1.7.11.3
Hi Ingo/Peter,
I am trying to understand the complex scheduler code and just found
something incorrect (maybe i am not reading it well):
File: kernel/sched/fair.c
static void
prio_changed_fair(struct rq *rq, struct task_struct *p, int oldprio)
{
if (!p->se.on_rq)
return;
/*
* Reschedule if we are currently running on this runqueue and
* our priority decreased, or if we are not currently running on
* this runqueue and our priority is higher than the current's
*/
if (rq->curr == p) {
if (p->prio > oldprio)
resched_task(rq->curr);
} else
check_preempt_curr(rq, p, 0);
}
Comment says that we must mark the task to be rescheduled, if we
are currently running and our priority has decreased. But in code we
are checking (p->prio > oldprio). i.e. reschedule if we were currently
running and our priority increased.
Sorry if i am wrong :(
--
viresh
