Hi all,
To support the new Linaro roadmap process, the Infrastructure team has
added new reports to status.linaro.org.
You can find the status for the current quarter here and drill down
into the cards targeted for Q4.
http://status.linaro.org/11.11/roadmap-2011Q4.html
There's of course work left to do, for instance there's a big backlog
of status graphs and some layout tweaks to handle. Not to mention
finding a good time to switch the status.linaro.org index page over to
the roadmap.
Still we believe that this will already be useful for everyone to keep
an eye on the roadmap and how your work supports the long term goals.
Direct any questions you may have about the tech details to
Infrastructure and your TL can help you with connecting your
blueprints to the roadmap cards. The Linaro Roadmap wiki page is also
a good read:
https://wiki.linaro.org/Process/Roadmap
Thanks,
Mattias
Hi Linus, Tony,
This RFC series adds pinmux support for OMAP using
the pinctrl framework. Though it adds a pinmux-omap.c
driver file, it currently only supports OMAP4 and also
has very few function/pin-groups defined.
I have also retained the existing muxing done from
board files using the OMAP-mux framework since this
series does not handle configuring pull up/downs for
pins, and only looks at pin-muxing.
These are still early patches, but I wanted to get
some feedback on if I am heading in the right direction.
Hence sharing these in the current form.
regards,
Rajendra
Rajendra Nayak (3):
pinctrl: add a driver for the OMAP pinmux
ARM: omap4: Add omap4 pinmux devices for core and wkup
ARM: omap4: Add pinmux map in SDP and PANDA board files
arch/arm/mach-omap2/board-4430sdp.c | 10 +
arch/arm/mach-omap2/board-omap4panda.c | 11 +
arch/arm/mach-omap2/devices.c | 43 ++
drivers/pinctrl/Kconfig | 7 +
drivers/pinctrl/Makefile | 1 +
drivers/pinctrl/pinmux-omap.c | 735 ++++++++++++++++++++++++++++++++
6 files changed, 807 insertions(+), 0 deletions(-)
create mode 100644 drivers/pinctrl/pinmux-omap.c
Hi, All
ICS has changed its default shell to mksh.
and the source of mksh is under ${AOSP}/external/mksh.
In ICS, mksh use /system/etc/mkshrc as the default profile if we log into
android with adb shell or on the serial console.
so if we want to export some environment variable like(PS1), we can change
this file.
and we can change the default profile file path by changing MKSHRC_PATH
in Android.mk.
if we don't log in, like just run "adb shell cmd", then the mkshrc will not
be used.
It says that mksh is *mostly* bourne shell compatible and is also POSIX sh
compatible,
but I'm not familiar with mksh, so if you are interested in it, you can go
to the homepage get more information.
this is the home page https://www.mirbsd.org/mksh.htm.
Thanks,
Yongqin Liu
Hello.
Here is the weekly status report from the Android Platform Team.
Key Points for wider discussion
===============================
* Android 2.3.7 Platform Release 11.11 complete and tested on all boards.
* Android 4.0 ICS up and running on Snowball.
Team Highlights
===============================
* ARM vexpress is now in android-build.
* The Kernel configuration is now available on android-build Build details
page.
* A prototype of the kernel rebuild script exits.
* Progress on ICS for iMX53 and Origen
* The gator daemon for DS-5 running on all but the Origen builds.
* ath6k Origen WiFi firmware has been integrated in Origen builds.
* USB 2.0 Ethernet adapter works on Origen board.
* Progress on MediaFrameworkTest integration.
Bugs fixed
===============================
878979, 886058, 889843, 889847, 891753, 892881, 884409, 842451, 877859,
891684, 884931
Miscellaneous
===============================
* New Team member Kejun Zhou from ST-Ericsson China.
* Both fgiff (Dec. 16) and cyang (Dec. 9) are Leaving Linaro due to
ST-Ericsson basingstoke site closing.
Issues
===============================
* Time lost due to the build system becoming corrupted (#891753).
Blueprints
===============================
https://launchpad.net/linaro-android/+milestone/11.11
Hi -
Thanks to the work of Angus and Tushar a second Landing Team has
established a tracking tree, for Samsung Origen. They're using the same
lt-tools management scripts I use to handle the various trees in TI
Landing Team.
As I mentioned in the talk I gave at Connect about lt-tools, the fact
that we're both tracking near Linus HEAD allows us to casually combine
the trees for the first time if we can arrange for our basis to be
relatively close.
Today with the help of Angus and Tushar I gave that a try and -->
http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=shortl…
this single tree builds current Landing Team tracking for both Panda
(omap4_defconfig) and Origen (origen_defconfig), we confirmed the
results work as expected. Its common basis is Linus HEAD from yesterday.
Actually, the two trees did not tread on each others' toes at all, the
rebase proceeded with zero conflicts. Angus mentioned that there are
still some topics to come on his side; maybe they can create conflicts
in the future. Panda tracking got battered by upstream stuff post-3.1
we're still working to clear but it's still workable for this test
purpose anyway since it includes all the code footprint.
So we should be able to make ongoing combined tracking releases, and if
that continues to work smoothly it will naturally lead to a combined 3.2
release tree. Since we'll both be using the same
linaro-androidization-tracking on these trees to create Android kernels,
a single unified Android kernel should be possible to generate
automatically from the unified vanilla one and I'll look at starting
that after Panda tracking is in better shape.
-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
