This patchset add support for Samsung's SMDK5250 board based on
EXYNOS5250 based SoC. It also adds support for MMC SPL booting.
The porting is done by Samsung engineers at HQ in System LSI Team.
I am contributing in upstreaming the code for the board.
Based upon discussions following patches are dropped in this version:
Exynos: Add CONFIG_EXYNOS4 Macro to EXYNOS4 based boards
Exynos: Clock.c: Replace exynos4 prefix with exynos
SMDK5250: enable device tree support is squashed with
EXYNOS: Add SMDK5250 board support
Chander Kashyap (4):
Exynos: Clock.c: Use CONFIG_SYS_CLK_FREQ macro
ARM: EXYNOS: Add support for Exynos5 based SoCs
EXYNOS: Add SMDK5250 board support
EXYNOS: SMDK5250: Add MMC SPL support
MAINTAINERS | 1 +
arch/arm/cpu/armv7/exynos/clock.c | 215 +++++++++-
arch/arm/include/asm/arch-exynos/clock.h | 326 ++++++++++++++
arch/arm/include/asm/arch-exynos/cpu.h | 35 ++-
arch/arm/include/asm/arch-exynos/gpio.h | 101 ++++-
board/samsung/smdk5250/Makefile | 64 +++
board/samsung/smdk5250/lowlevel_init.S | 528 ++++++++++++++++++++++
board/samsung/smdk5250/mem_setup.S | 600 +++++++++++++++++++++++++
board/samsung/smdk5250/mmc_boot.c | 58 +++
board/samsung/smdk5250/smdk5250.c | 125 +++++
board/samsung/smdk5250/smdk5250_setup.h | 589 ++++++++++++++++++++++++
board/samsung/smdk5250/tools/mkexynos_image.c | 117 +++++
boards.cfg | 1 +
include/configs/s5pc210_universal.h | 1 +
include/configs/smdk5250.h | 188 ++++++++
15 files changed, 2931 insertions(+), 18 deletions(-)
create mode 100644 board/samsung/smdk5250/Makefile
create mode 100644 board/samsung/smdk5250/lowlevel_init.S
create mode 100644 board/samsung/smdk5250/mem_setup.S
create mode 100644 board/samsung/smdk5250/mmc_boot.c
create mode 100644 board/samsung/smdk5250/smdk5250.c
create mode 100644 board/samsung/smdk5250/smdk5250_setup.h
create mode 100644 board/samsung/smdk5250/tools/mkexynos_image.c
create mode 100644 include/configs/smdk5250.h
--
1.7.5.4
This information is also available here:
https://wiki.linaro.org/Platform/Android/Status/2012-01-12
Key Points for wider discussion
===============================
* Ethernet Communication Manager is integrated in ICS
* Snowball USB OTG greatly improved. Supports High Speed powered hubs.
Team Highlights
===============================
* Linaro Android is now based on AOSP version 4.0.3.
* The first 12.01 release has been cut.
* Wifi is enabled on tracking-panda builds
* Progress on Wifi for Snowball.
* Good progress on OMX IL for ICS on Origen.
* Improvements in binutils. Now at version 2.22.51.0.1
* Improvements in documentation on the wiki. e.g.
[[https://wiki.linaro.org/Platform/Android/BuildSource | Building
Android Platform Code]]
Bugs fixed
===============================
* 908956 ICS: Panda: 1080p launcher screen positioning uses 720p origin
* 912720 staging-panda build 179 fails to bootup
* 878973 Builds can not be compiled with the original AOSP GCC 4.4 toolchain
* 890346 Sound doesn't work on panda on ICS
* 900508 GLMark2 not available on ICS
* 913945 powertop not available on ICS
* 894502 No Ethernet Communication Manager on ICS
* 908956 ICS: Panda: 1080p launcher screen positioning uses 720p origin
* 912229 ffmpeg 0.9.1 is released, linaro-android has 0.9.0
* 867527 All binaries and libraries are mapped rwx on both text and data
* 892837 staging-panda and tracking-panda do not come up with the
right resolution
Miscellaneous
===============================
Issues
===============================
Blueprints
===============================
https://launchpad.net/linaro-android/+milestone/12.01
Hi All,
I had some thoughts and a suggestion this morning about the monthly
release cycle that I'd like to share. Perhaps I'll get booed off the
stage, perhaps not. I'm sure it can be improved on.
There is a great deal of stress around what blueprints fit into what
monthly release boundary. For deliveries like the LEB that combine the
fruits of our Linaro labors this makes great sense.
Outside of the process for LEB creation and release, I'd like to
suggest it's less than efficient and creates a bit of stress as we
have the monthly rush to make the release dates. PMs and TLs
continually have to be watching for what will and what won't be making
dates that fit with the LEB. This passes on the stress to the
engineering team, causes some late night hack-a-thons which in turn I
believe caused us to rush software what was less than ready to be
included in a LEB. I'm sure we all have examples we could point to.
To address this I'd like to suggest the following.
The production of the LEB and related builds should continue to be on
a monthly release cycle.
However outside of that process, for the WGs and such, we should go to
a process based on continuous integration.
As work groups, landing teams and so on, we commit to the LEB process
that we have some set of blueprints IN QUEUE, meaning they are being
worked on right now. When they go complete if they are LEB bound, they
are delivered to the staging overlay. Items in the staging overlay are
candidates for promotion to the overlay. When an item in the staging
overlay is judged as being ready (bugs are at least triaged and deemed
to not be blocking) it is promoted into the overlay from which daily
builds are made and the monthly release is made.
Packages in the staging overlay are the subject of functional test.IE
Does it work? Packages in the overlay are the subject of integration
test. IE Does it break the system?
Work Groups, Landing Teams will also commit to having a priority list
of blueprints and bugs that are being addressed or will be addressed.
This keeps the release process and management team aware of what is
coming and when. The # of completed work items per week (or other
counts) can also help the management team measure forward momentum and
progress.
In some respects it's subtle process tweek. But I feel shifting part
of linaro to a continuous integration / ship when ready model makes
sense. In the work groups we are more connected upstream as we stay
tune with upstream release boundaries but still want to showcase
results in the monthly LEBs. Likewise focus on the LEB continues
with higher quality software. It does shift the goal of creating great
software by date X, to creating great software and ship when it's
ready.
Perhaps this would be a good discussion for 1Q12LC.
--
Regards,
Tom
"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian
Multimedia Tech Lead | Linaro.org │ Open source software for ARM SoCs
w) tom.gall att linaro.org
w) tom_gall att vnet.ibm.com
h) tom_gall att mac.com
Hi All,
You’ll be pleased to see we've now created the e-mail alias for Linaro
Connect Q1.12. You can mail connect-q1.12(a)linaro.org for general
announcements, and we will also use this alias to advise you of important
issues related to and during the event.
Everyone who has registered for Linaro Connect Q1.12 is now on this alias.
If you’re attending and have not yet registered, please do so asap by
clicking this link.
‧ Register for Linaro Connect Q1.12
<http://connect.linaro.org/register-connect/> [1]
You’ll also be able to subscribe to sessions at Linaro Connect Q1.12 you are
interested in, apply for visas and share travel information with others (may
be helpful for sharing taxi rides etc).
In addition, please book your accommodation for Linaro Connect Q1.12 before
rooms at the hotel run out. As many of you will be staying on for ELC and
ABS, we've now updated the accommodation booking link to reflect booking
dates from 5th through to 18th February.
‧ Book accommodation for Linaro Connect Q1.12
<http://www.sofitel.com/sofitel/lien_externe.svlt?goto=spec_rate_hotel&sub=I
SP&code_hotel=0922&code_chaine=SOF&RA1=lin0502212&RA2=&ragp=0&libelle_tarif=
1&showEco=0&jour_depart=05&mois_depart=02&annee_depart=2012&jour_arrivee=05&
mois_arrivee=02&annee_arrivee=2012&nb_nuit=13,> [2]
You will see once you've clicked 'recalculate' it states breakfast is not
included. This is INCORRECT – breakfast is included for all delegates. You
do not need to add any additional breakfast to your room booking.
Finally, you can see the developing schedule and other information on the
Linaro Connect Q1.12 website here:
‧ Linaro Connect Q1.12 website
<http://connect.linaro.org/events/event/lcq1-12/> [3]
[1] http://connect.linaro.org/register-connect/
[2]
http://www.sofitel.com/sofitel/lien_externe.svlt?goto=spec_rate_hotel&sub=IS
P&code_hotel=0922&code_chaine=SOF&RA1=lin0502212&RA2=&ragp=0&libelle_tarif=1
&showEco=0&jour_depart=05&mois_depart=02&annee_depart=2012&jour_arrivee=05&m
ois_arrivee=02&annee_arrivee=2012&nb_nuit=13,
[3] http://connect.linaro.org/events/event/lcq1-12/
Regards,
--
Arwen Donaghey
Executive Assistant
T: +44 1223 45 00 22 | M: +44 7791 279 521
Lockton House | Clarendon Road | Cambridge | CB2 8FH
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/#!/linaroorg> | Blog
<http://www.linaro.org/linaro-blog/>
This patchset add support for Samsung's SMDK5250 board based on
EXYNOS5250 based SoC. It also adds support for MMC SPL booting.
The porting is done by Samsung engineers at HQ in System LSI Team.
I am contributing in upstreaming the code for the board.
Based upon discussions following patches are dropped in this version:
Exynos: Add CONFIG_EXYNOS4 Macro to EXYNOS4 based boards
Exynos: Clock.c: Replace exynos4 prefix with exynos
SMDK5250: enable device tree support is squashed with
EXYNOS: Add SMDK5250 board support
Chander Kashyap (4):
Exynos: Clock.c: Use CONFIG_SYS_CLK_FREQ macro
ARM: EXYNOS: Add support for Exynos5 based SoCs
EXYNOS: Add SMDK5250 board support
EXYNOS: SMDK5250: Add MMC SPL support
MAINTAINERS | 1 +
arch/arm/cpu/armv7/exynos/clock.c | 215 +++++++++-
arch/arm/include/asm/arch-exynos/clock.h | 326 ++++++++++++++
arch/arm/include/asm/arch-exynos/cpu.h | 53 ++-
arch/arm/include/asm/arch-exynos/gpio.h | 32 ++
board/samsung/smdk5250/Makefile | 64 +++
board/samsung/smdk5250/lowlevel_init.S | 528 ++++++++++++++++++++++
board/samsung/smdk5250/mem_setup.S | 600 +++++++++++++++++++++++++
board/samsung/smdk5250/mmc_boot.c | 58 +++
board/samsung/smdk5250/smdk5250.c | 125 +++++
board/samsung/smdk5250/smdk5250_setup.h | 589 ++++++++++++++++++++++++
board/samsung/smdk5250/tools/mkexynos_image.c | 117 +++++
boards.cfg | 1 +
include/configs/s5pc210_universal.h | 1 +
include/configs/smdk5250.h | 188 ++++++++
15 files changed, 2878 insertions(+), 20 deletions(-)
create mode 100644 board/samsung/smdk5250/Makefile
create mode 100644 board/samsung/smdk5250/lowlevel_init.S
create mode 100644 board/samsung/smdk5250/mem_setup.S
create mode 100644 board/samsung/smdk5250/mmc_boot.c
create mode 100644 board/samsung/smdk5250/smdk5250.c
create mode 100644 board/samsung/smdk5250/smdk5250_setup.h
create mode 100644 board/samsung/smdk5250/tools/mkexynos_image.c
create mode 100644 include/configs/smdk5250.h
--
1.7.5.4
Power Management Item:
=====================
One of the roadmap cards the PMWG is working on is the thermal management card.
http://status.linaro.org/card/PMWG2011-THERMAL-MANAGEMENT.html
One of the acceptance criteria for this item is:
Thermal management should be validated on an Android image; a
suggestion is to run the system on the highest OPP, and use that to
trigger the thermal transition.
Per Amit D., This topic has been discussed with Samsung landing team,
they will pick these patches for hwpack and android release.
I want to make sure this happens and the patches make it to an Android
image that we can test with on Samsung platform.
Android Agenda Items
===================
1. Single kernel?
2. Benchmarks-to-toolchain-group work
3. Developer tools
4. MM help with Video Conferencing
5. GFX help GLMark2
6. PM on all Android targets
7. How else can Android help you?
Notes:
---------
* Single Kernel status unknown.
* Valgrind +2
* MM help with video conferencing?
* How can Android better help you
* MM? Panda Audio enablement, Vishal question, what’s the plan for
the rest, AI for Zach to send plan.
* GFX? Wiki pages are helpful. Some kind of dev guide. PoC list for
Android issues.
* Toolchain: Valgrind, auto-benchmarks, PoC lists, getting going
* PM: Power Tutor, stalled out, Zach to pick back up , Amit can you,
once CPU idle, pick i up support
* KWG: ???
Dev Platform Agenda Items:
=======================
1. Deliverables that might affect Ubuntu
2. How to make sure PM is properly integrated at the Ubuntu targets
3. MM and work needed to improve XBMC and Ubuntu TV (qtmobility)
4. GFX planning for 12.01 and work with Unity 3D
5. Anything missing at the Dev Platform (images, tools) that might be
interesting for other WGs?
Notes:
---------
* Michael is fine with the current sysroot produced by Marcin, and
plan to keep validating it by hand once they are available. Maybe a
discussion should happen at Connect to see if this can be automate.
* Please send Ubuntu input to Ricardo.
* Still not sure if Ubuntu is properly using power management (as the
LT is maintaining the tree and config set), Amit will take a look and
see if anything is missing.
* Point to MM working group, XBMC and Ubuntu TV, can the MM WG help?
Ravi is. Kan Hu - XBMC still need a person for Ubuntu TV.
* Mark and Alexandros is working on Unity-3D upstreaming. Fighting
against time. They are the correct PoC for Unity-3D upstreaming for
this month and through Connect.
* Ricardo, are there any other tools that people need in Ubuntu?
Jesse, images are fairly good.
Validation Agenda Items:
====================
1. There was some recent discussion with mmwg about audio e2e testing,
and whether we should be testing this over hdmi for boards that
default to hdmi, or whether all boards should start with a test to
simply cover the jack loopback.
2. Kernel WG testsuite progress?
Notes:
---------
* End-to-end audio test. Need to handle HDMI audio test. Audio
loop-back over jack is one test case and HDMI audio loop-back is a
seperate test. Need HDMI test in the next 3-4 months.
* Need to get audio test into LAVA.
* Tom to work on Android and other higher level tests
Housekeeping:
===========
The quality of voice really sucks. Any suggestions for a public
platform, or should we move back to #linaro-meeting?
- Mumble seems to work better, as you can see where the noise is
coming and mute the person (but people generally have issues with
mumble).
- Google Hangout? Would probably work fine too (it’s the only good
thing of google+ ;-)
There are quite a few conflicts with this time slot, we need to
reschedule. I (dzin) will try to find a more appropriate time slot.
Apologies and please bear with me.
==============
= Action Items: =
==============
Amit will send out CONFIG options to check and a test we can run by
hand for http://status.linaro.org/card/PMWG2011-THERMAL-MANAGEMENT.html.
Ideally this would be part of the pm test case available at LAVA.
Besides config enablement, would be good to check with LTs if they are
including the needed patches and so on.
Zach to spin up a thread about feeding raw data to the toolchain
grouphttp://status.linaro.org/card/PMWG2011-THERMAL-MANAGEMENT.html
Zach to send an email to KWG.
Ricardo to spin up a BP for remaining XBMC and Ubuntu TV work (2
different BPs to target 2 people)
Zach to meet with Benjamin.
Tony to talk to Alexandros about GLMark2 integration work, Zach to get
a thread going.
David to send out a summary to linaro-dev and linaro-android.
--
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs
Hi,
Just tried a linaro nano distrib for beagleboards. I used the dd tool to
copy bit per bit the system to the sdcard but I now have a 500 Mb system
on a 8 Gb sd card. First thing to do is to resize the rootfs partition.
I'd like to know if it's possible to merge those 2 steps into one?
