Hi all.
During Linaro Connect there will be a session [1] about packaging tools
and other components produced by Linaro teams.
Goals:
- Review the current set of components/projects create and maintained by
Linaro
- Identify the ones that are not yet part of Ubuntu and Ubuntu LEB
- Discuss how to make the Linaro changes upstream at the distro-level as
soon they are updated
I want to get Linaro to the point where most of our tools will be
available in Debian and Ubuntu distributions instead of random set of PPAs.
Whom I would like to see there? Everyone who has written any packaged
(or not yet) tool useful for other developers. Nevermind is it host or
target, native or cross tool.
1.
http://summit.linaro.org/lcq2-12/meeting/20859/review-the-missing-packages-…
I did a number of searches and found that in the recent kernels the
twl4030-madc module has been made upstream.
And I found this link:
http://wiki.gumstix.org/index.php?title=ADC_overo_2.6.39%2B
as I followed it, I couldn't find the directories mentioned therein..
The most relevant thing I found in Linaro-Alip/Nano file system was the
/sys/class/i2c-adapter/ folder. Now i'm into the wild and searching for the
file I need, so that I can read the ADC values.
Any help meanwhile....???
---------------------------------
Sudhangathan BS
Ph:(+91) 9731-905-205
---------------------------------
terms: twl4030-madc tps65950 hwmon madc driver sys class i2c-adapter
These couple of patches use the new cpuidle core api to refactor
some part of the code. The first one removes the state count initialization
as it is done from the cpuidle core and the second one use the new
API and removes the ops.
The patchset is based on Lenb's tree on top of Robert Lee cpuidle consolidation
work.
I don't have this board, I was not able to test these patches.
Daniel Lezcano (2):
ARM: DAVINCI: cpuidle - remove useless state count initialization
ARM: DAVINCI: cpuidle - remove ops
arch/arm/mach-davinci/cpuidle.c | 83 +++++++++++++--------------------------
1 files changed, 27 insertions(+), 56 deletions(-)
--
1.7.5.4
These couple of patches use the new cpuidle core api to refactor
some part of the code. The first one declares the states directly
in the driver declaration and the second one use the timekeeping
flag to let the cpuidle core to compute the idle time.
I don't have this board, I was not able to test these patches.
Daniel Lezcano (2):
ARM: s3c64xx: cpuidle - declare the states with the new api
ARM: s3c64xx: cpuidle - use timekeeping wrapper
arch/arm/mach-s3c64xx/cpuidle.c | 45 +++++++++++++--------------------------
1 files changed, 15 insertions(+), 30 deletions(-)
--
1.7.5.4
Recently a patch went in for tidspbridge code, to ioremap
SCM registers and solve a build break[1]. However it has
been pointed out before that this is a layer violation
given that control module should handle its own registers, this
series is an attempt to create APIs for the users of these
registers.
With some adaptations this patch might also make use of it:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg66491.html
Patch: staging: tidspbridge: use scm functions to set boot address and mode,
will be sent separately to staging tree.
Tested on OMAP3 Beagleboard.
[1] http://www.mail-archive.com/devel@linuxdriverproject.org/msg18762.html
Omar Ramirez Luna (3):
OMAP2+: control: new APIs to configure boot address and mode
OMAP: dsp: interface to control module functions
staging: tidspbridge: use scm functions to set boot address and mode
arch/arm/mach-omap2/control.c | 43 ++++++++++++++++++++
arch/arm/mach-omap2/control.h | 2 +
arch/arm/mach-omap2/dsp.c | 4 ++
.../include/mach/ctrl_module_core_44xx.h | 1 +
arch/arm/plat-omap/include/plat/dsp.h | 3 +
drivers/staging/tidspbridge/core/tiomap3430.c | 32 +++-----------
6 files changed, 60 insertions(+), 25 deletions(-)
--
1.7.4.1
Hello All
ARM have released a new version of Developer Studio 5 (DS-5) and we now
have a new version of the Gator component [1] to go with this which
needs updating in all Linaro kernel trees that will be part of the 12.05
release.
For those people maintaining kernel trees here is what this means...
- If your kernels are including the linux-linaro-core-tracking [2]
branch then you will get the new Gator version from this when it is
updated over the next couple of days. You don't need to do anything
except to make sure you are up to date with this branch before the 12.05
release.
- For Ubuntu kernels not including linux-linaro-core-tracking (and not
being released from the common linux-linaro branch) then you should
replace your existing gator topic branch (or add one if it is missing).
This new topic branch can be created by pulling from the ARM Landing
Team's tree [3], we have tree topic branches available for the last
three kernel versions...
tracking-armlt-gator (3.4-rc7)
3.3-armlt-gator-5.10
3.2-armlt-gator-5.10
The code in these branches is identical, they are just rebased onto
different Linux versions to make pulling easier.
- For Android kernels, if your kernel already includes the Gator topic,
then this should be updated as above. If it doesn't already have Gator
then you can add this topic now, or, leave it for the time being. (Some
Android builds are using a separate Gator git repo in their manifest and
this will continue to work for now.)
If anyone has any questions or if anything is unclear, please do
hesitate to contact me.
For those people who have applied Mali driver patches to support
profiling by Gator: you don't need to modify those Mali patches, just
take the new version of Gator, this will still work OK.
Cheers
--
Tixy
[1] Gator is the ARM target device components for ARM's Streamline
Performance Analyzer which is part of their Developer Studio (DS-5).
http://www.arm.com/products/tools/software-tools/ds-5/streamline.php
[2] http://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=shortlog;…
[3] git://git.linaro.org/landing-teams/working/arm/kernel.git