Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed
following:
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
my BB.
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
EARLY_PRINTK)
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
INSTALL_MOD_PATH=/media/rootfs
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?
Regards,
Avik
Hi Nicolas,
Attached patch set has support for MPU DVFS (cpufreq) on OMAP4 and
these are rebased against latest .38 linaro kernel.
omap cpufreq driver changes are already posted to lo
(https://patchwork.kernel.org/patch/589081/) and OMAP4 DVFS layer
changes will be upstreamed once Basic DVFS framework is accepted.
Kindly let me know if you can merge these patches for .38 linaro kernel.
Regards
Vishwa
Hi,
If I mess up the u-boot in my efikamx smart book how can I install a new one?
I tried booting with an SD-card image from
http://www.powerdeveloper.org/asset/by-id/116. I guess this only works
if I have a working u-boot in place.
I don't have the serial/JTAG connector. Is this what I need in order to recover?
Thanks,
Per
Hi all,
Per Nicolas' request, I've compiled a list of all patchsets needed to
get functional display on the Pandaboard. There are 35 patches in all,
over 6 series, plus one patch for the board file to enable the DVI
support.
I've set up two branches (against v2.6.38-rc4, and against the head of
linux-linaro-2.6.37 as of today) to make it easy for people to extract
and test these.
They are available in my git tree here:
git://dev.omapzoom.org/pub/scm/anand/linux-omap-usb.git
in the display-patches-for-v2.6.38-rc4 and
display-patches-for-linaro-37 branches respectively.
I've updated the bug report for this issue (Bug #707038) with links to
the component series, as well as the link to my tree above.
(I'll make sure these two branches stick around - at least as a
reference - until the patches make it upstream).
@Nicolas,
None of these have been queued up by the respective maintainers yet,
so they aren't in linux-next as of today. However I believe there are
no outstanding review comments for these.
I can send a pull request for these if it's okay with you. Let me know
if you need them based off any particular tag/commit/branch.
- Anand
Hi,
I am trying to prepare an MMC card to boot up Panda with Linaro daily
build image.
I downloaded linaro-image-tools from:
https://launchpad.net/linaro-image-tools
I installed all dependencies mentioned in the README and tried to run
linaro-media-create like below:
sudo ./linaro-media-create --rootfs ext3 --mmc /dev/sdb1 --binary
/home/a0393566local/linaro/headless/linaro-natty-headless-
tar-20110206-0.tar.gz --hwpack /home/a0393566local/linaro/hwpack
/hwpack_linaro-panda_20110206-0_armel_supported.tar.gz --dev panda
However, it crashes immediately with the following dump:
http://pastebin.com/SV78dP8L
Any idea what could be going wrong?
Thanks,
Aneesh
This patchset adds FSL mx51 device tree support. This
is based on
git://git.secretlab.ca/git/linux-2.6 devicetree/test
This patch has been tested on MX51 babbage board and can
boot up succesfully to linux console with DT enabled.
Jason Liu (3):
arm/dt: add basic mx51 device tree support
arm/dt: add very basic dts file for babbage board
serial/imx: parse from device tree support
arch/arm/boot/dts/babbage.dts | 117 +++++++++++++++++++++++++++++++
arch/arm/mach-mx5/Kconfig | 6 ++
arch/arm/mach-mx5/Makefile | 1 +
arch/arm/mach-mx5/board-dt.c | 64 +++++++++++++++++
arch/arm/mach-mx5/clock-mx51-mx53.c | 45 ++++++++++++-
arch/arm/plat-mxc/include/mach/common.h | 1 +
drivers/tty/serial/imx.c | 81 +++++++++++++++++++---
7 files changed, 304 insertions(+), 11 deletions(-)
create mode 100644 arch/arm/boot/dts/babbage.dts
create mode 100644 arch/arm/mach-mx5/board-dt.c
mode change 100644 => 100755 drivers/tty/serial/imx.c
Hi,
I have started to use the new cpuidle tracepoint and created a plugin
for pytimechart.
I'm not sure if it's the right way to add this cpuidle trace format
update but it's the less intrusive one.
I also have a plugin for new cpu_hotplug trace points but i'm waiting
for trace approval before sending it
Vincent
Subject: [PATCH 1/1] cpuidle: new plugin
new tracepoints are available for cpuidle
Signed-off-by: Vincent Guittot <vincent.guittot(a)linaro.org>
---
timechart/plugins/cpuidle.py | 35 +++++++++++++++++++++++++++++++++++
1 files changed, 35 insertions(+), 0 deletions(-)
create mode 100644 timechart/plugins/cpuidle.py
diff --git a/timechart/plugins/cpuidle.py b/timechart/plugins/cpuidle.py
new file mode 100644
index 0000000..32dce91
--- /dev/null
+++ b/timechart/plugins/cpuidle.py
@@ -0,0 +1,35 @@
+from timechart.plugin import *
+from timechart import colors
+from timechart.model import tcProcess, c_state_table
+
+class cpu_idle(plugin):
+ additional_colors = """
+"""
+ additional_ftrace_parsers = [
+ ('cpu_idle', 'state=%d cpu_id=%d', 'state', 'cpuid'),
+ ]
+
+ additional_process_types = {
+ }
+
+ @staticmethod
+ def do_event_cpu_idle(self,event):
+ self.ensure_cpu_allocated(event.cpuid)
+ tc = self.tmp_c_states[event.cpuid]
+ if event.state != 4294967295 :
+ if len(tc['start_ts'])>len(tc['end_ts']):
+ tc['end_ts'].append(event.timestamp)
+ self.missed_power_end +=1
+ if self.missed_power_end < 10:
+ print "warning: missed cpu_idle end"
+ if self.missed_power_end == 10:
+ print "warning: missed cpu_idle end: wont warn anymore!"
+ tc['start_ts'].append(event.timestamp)
+ tc['types'].append(colors.get_color_id(c_state_table[int(event.state)]))
+ tc['linenumbers'].append(event.linenumber)
+ else :
+ if len(tc['start_ts'])>len(tc['end_ts']):
+ tc['end_ts'].append(event.timestamp)
+
+plugin_register(cpu_idle)
+
--
1.7.1
Hi,
Just tested the imx51 Thumb-2 kernel on efikamx here -- it boots fine,
but we only went as far as the initramfs.
Is anyone currently relying on CONFIG_LATENCYTOP? If so, we should
investigate what the incompatibility is...
Cheers
---Dave
On Wed, Feb 23, 2011 at 6:11 PM, Dave Martin <dave.martin(a)linaro.org> wrote:
> Hi there,
>
> Talking with Loic just now, we thought it could be worth turning on
> Thumb-2 in the main omap kernel package after all, since we've at
> least seen it work on a few different boards now. It feels ready for
> wider testing.
>
> Is it possible for you to move to a newer snapshot of the 2.6.38
> linaro tree, or will that be problematic at this stage?
>
>
> Since the imx51 kernel at least seems to build and boot in Thumb, it
> could be worth enabling a separate build in a PPA, but it's may not
> mature enough for everyone to use as the main kernel just yet. If you
> want to try this, you need CONFIG_ARM_UNWIND=y, CONFIG_LATENCYTOP=n
> and CONFIG_THUMB2_KERNEL=y
>
> Cheers
> ---Dave
>
Hi All,
In Multimedia WG we have been posed with a question regarding best way
to expose low level API for camera.so this a questions mainly about pros and
cons of v4l2 and omx over each other.So to involve a wider community to
discuss this topic I am floating this mail on linaro-dev.Please share your
view/experiences.Also please involve any body else in this mail who can
provide valuable inputs on this.
Thanks
Sachin
