I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed
1. Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with
hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz
and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on
2. Cloned linux-linaro-2.6.37. Changed to source directory
3. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
4. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
5. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
6. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
7. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
8. cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on.
I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create
uInitrd? If so, then how to create it for ARM?
v3 is rebased on top of the latest serial runtime
patches and boot tested with/without DT on OMAP4
SDP and OMAP4 Panda boards.
Patches can be found here..
I also had to pull in a fix for DT testing (already in linux-omap
master) which was missing as the serial runtime branch
was based on an older master commit.
Changes in v3:
-1- Rebased on latest serial runtime patches
-2- Minor typr fixes
Changes in v2:
-1- Got rid of binding to define which uart is console
-2- Added checks to default clock speed to 48Mhz
-3- Added compatible for each OMAP family
-4- Used of_alias_get_id to populate port.line
 git://gitorious.org/runtime_3-0/runtime_3-0.git for_3_3/lo_rc4_uartruntime
Rajendra Nayak (4):
omap-serial: Get rid of all pdev->id usage
omap-serial: Use default clock speed (48Mhz) if not specified
omap-serial: Add minimal device tree support
ARM: omap: pass minimal SoC/board data for UART from dt
.../devicetree/bindings/serial/omap_serial.txt | 10 +++
arch/arm/boot/dts/omap3.dtsi | 31 ++++++++
arch/arm/boot/dts/omap4.dtsi | 28 +++++++
arch/arm/mach-omap2/board-generic.c | 1 -
drivers/tty/serial/omap-serial.c | 80 +++++++++++++++----
5 files changed, 132 insertions(+), 18 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial/omap_serial.txt
For the 12.01 cycle the Linaro Platforms team is pleased to announce
the availability of the new linarotv-xbmc based image. This combines
the xbmc media server project with linaro's leb to result in a "works
out of the box" arm based media server image.
It can be found at http://snapshots.linaro.org/oneiric/linaro-o-linarotv-xbmc/
Currently the best experience can be found on Panda/Panda ES however
boards with hardware video acceleration enabled should work well. We
welcome feedback and suggestions on the image. Support is on a as
"best can" basis. Bugs if found should be written against
linaro-ubuntu in lauchpad.
"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
Following patchset is required to add framebuffer support on Origen.
The patches are based on following commit on Kukjin's for-next branch.
a188e1e "Merge branch 'next-samsung-devel' into for-next"
Tushar Behera (3):
ARM: EXYNOS: Increase DMA pool allocator size for framebuffer
- Required to allocate the framebuffer successfully
ARM: EXYNOS: Add clkdev lookup entry for lcd clock
- Required for framebuffer operation
ARM: EXYNOS: Invert VCLK polarity for framebuffer on Origen board
- Required to remove glitch in LCD display
arch/arm/mach-exynos/clock.c | 14 +++++++++-----
arch/arm/mach-exynos/cpu.c | 7 +++++++
arch/arm/mach-exynos/mach-origen.c | 3 ++-
3 files changed, 18 insertions(+), 6 deletions(-)
From: "Ying-Chun Liu (PaulLiu)" <paul.liu(a)linaro.org>
This is the Anatop regulator used by Freescale i.MX6 SoC.
Please take a look and give me some comments.
Ying-Chun Liu (PaulLiu) (1):
Regulator: Add Anatop regulator driver
drivers/regulator/Kconfig | 7 +
drivers/regulator/Makefile | 1 +
drivers/regulator/anatop-regulator.c | 236 ++++++++++++++++++++++++++++
include/linux/regulator/anatop-regulator.h | 82 ++++++++++
4 files changed, 326 insertions(+), 0 deletions(-)
create mode 100644 drivers/regulator/anatop-regulator.c
create mode 100644 include/linux/regulator/anatop-regulator.h
I have an interesting observation that I thought might be interesting
to the tool-chain team.
I was trying to build u-boot in Thumb2 for OMAP4. Everything was fine
until I added some patches recently. One of these patches introduced an
API (let's say foo()) that has a weakly linked alias(let's say
__foo()) and a strongly linked implementation(the real foo()) in an
Although I give -mthumb and -mthumb-interwork for all the files,
apparently GCC generates ARM code for assembly files. In the final
image foobar() calls foo() using a BL. Since foobar() is in Thumb and
foo() in ARM, it ends up crashing. Looks like foobar() assumed foo()
to be Thumb because __foo() is Thumb.
Also I see that 'objdump -S' aborts when it tries to parse foo().
I could workaround this problem by having foo() also in a C file that
in turn calls into the assembly file.
I tried Linaro GCC 4.5.2 and Codesourcery Lite GCC 4.4.1. Both seem to
have the issue.
Isn't this an issue with GCC or am I missing something?