linaro-kernel September 2013

linaro-kernel@lists.linaro.org

106 participants
319 discussions

[PATCH v2 0/4] perf: parse the dwarf backtrace info from .debug_frame section

by Jean Pihet

On ARM the debug info is not present in the .eh_frame sections but in .debug_frame instead, in dwarf format. This patch set uses libunwind to load and parse the dwarf debug info from the .debug_frame section if no .eh_frame_hdr section is found; also it sets the hooks in the perf_regs and libunwind code for ARMv7. Dependencies: . if present, libunwind >= 1.1 is needed to prevent a segfault when parsing the dwarf info, . libunwind needs to be configured with --enable-debug-frame to prevent a linkage error. Note: --enable-debug-frame is automatically selected on ARM). The generated perf has been tested on ARMv7 (OMAP4, Marvell Armada XP) and x86_64, using the following commands: perf record -g [dwarf] -- <binary> perf report --sort symbol --call-graph --stdio Jean Pihet (2): perf tools: Check libunwind for availability of dwarf parsing feature perf: parse the .debug_frame section in case .eh_frame is not present Will Deacon (2): ARM: perf: add support for perf registers API ARM: perf: wire up perf_regs and unwind support for ARM arch/arm/Kconfig | 2 + arch/arm/include/uapi/asm/Kbuild | 1 + arch/arm/include/uapi/asm/perf_regs.h | 23 +++++++++++ arch/arm/kernel/Makefile | 1 + arch/arm/kernel/perf_regs.c | 30 ++++++++++++++ tools/perf/arch/arm/Makefile | 3 ++ tools/perf/arch/arm/include/perf_regs.h | 54 +++++++++++++++++++++++++ tools/perf/arch/arm/util/unwind.c | 48 ++++++++++++++++++++++ tools/perf/config/Makefile | 7 +++- tools/perf/config/feature-tests.mak | 11 ++++- tools/perf/util/unwind.c | 71 +++++++++++++++++++++++++-------- 11 files changed, 232 insertions(+), 19 deletions(-) create mode 100644 arch/arm/include/uapi/asm/perf_regs.h create mode 100644 arch/arm/kernel/perf_regs.c create mode 100644 tools/perf/arch/arm/include/perf_regs.h create mode 100644 tools/perf/arch/arm/util/unwind.c -- 1.7.11.7

11 years, 4 months

[PATCH 0/4] driver core: Introduce initcall_driver() to eliminate boilerplate code

by Hanjun Guo

Lots of device drivers especially for platform/I2C/SPI bus devices, they want to be initialized earlier than other devices, so the driver use initcall such as subsys_initcall for the device initialization. But for those drivers, lots of them just do nothing special in xxx_initcall/module_exit, and produce lots of boilerplate. This patch set introduces a helper macro initcall_driver() to eliminate lots of boilerplate just like module_driver() did, and use it for platform/I2C/SPI bus devices. I use following command under the lastest kernel source code: $grep -r -E "*_initcall" drivers/ | cut -d":" -f1 |xargs grep -E "return platform_driver_register|return i2c_add_driver|return spi_register_driver" | cut -d":" -f1 | xargs grep "module_exit" | wc -l and get 205 hits, so if we use helper macro initcall_driver(), we can reduce thousands lines of code. Hanjun Guo (4): driver core: introduce helper macro initcall_driver() platform device: introduce helper macro initcall_platform_driver() i2c: introduce helper macro initcall_i2c_driver() spi: introduce helper macro initcall_spi_driver() include/linux/device.h | 27 +++++++++++++++++++++++++++ include/linux/i2c.h | 11 +++++++++++ include/linux/platform_device.h | 11 +++++++++++ include/linux/spi/spi.h | 11 +++++++++++ 4 files changed, 60 insertions(+) -- 1.7.9.5

11 years, 4 months

[PATCH] KVM: ARM: arch_timer: Initialize cntvoff at vcpu_init

by Christoffer Dall

Initialize the cntvoff at vcpu_init time, not before running the VCPUs at the first time because that will overwrite any potentially restored values from user space. Signed-off-by: Christoffer Dall <christoffer.dall(a)linaro.org> --- virt/kvm/arm/arch_timer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c index 8168437..2f6b5fe 100644 --- a/virt/kvm/arm/arch_timer.c +++ b/virt/kvm/arm/arch_timer.c @@ -181,6 +181,7 @@ void kvm_timer_vcpu_init(struct kvm_vcpu *vcpu) INIT_WORK(&timer->expired, kvm_timer_inject_irq_work); hrtimer_init(&timer->timer, CLOCK_MONOTONIC, HRTIMER_MODE_ABS); timer->timer.function = kvm_timer_expire; + vcpu->kvm->arch.timer.cntvoff = kvm_phys_timer_read(); } static void kvm_timer_init_interrupt(void *info) @@ -282,7 +283,6 @@ void kvm_timer_vcpu_terminate(struct kvm_vcpu *vcpu) int kvm_timer_init(struct kvm *kvm) { if (timecounter && wqueue) { - kvm->arch.timer.cntvoff = kvm_phys_timer_read(); kvm->arch.timer.enabled = 1; } -- 1.7.10.4

11 years, 4 months

next/master boot: 26 pass, 3 fail (next-20130927)

by Kevin Hilman build bot

Automated DT boot report for various ARM defconfigs. Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo'). Tree/Branch: next/master Git describe: next-20130927 Commit: a0cf1abc25 Add linux-next specific files for 20130927 Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: arm-multi_v7_defconfig armada-370-mirabox: FAIL: arm-mvebu_defconfig sama5d35ek: FAIL: arm-sama5_defconfig Full Report =========== arm-tegra_defconfig ------------------- tegra30-beaver PASS: 0 min 17.9 sec arm-omap2plus_defconfig ----------------------- am335x-boneblack PASS: 0 min 30.0 sec omap3-beagle-xm PASS: 0 min 49.8 sec am335x-bone PASS: 0 min 26.3 sec omap3-tobi,3530overo PASS: 0 min 42.3 sec omap4-panda PASS: 1 min 2.6 sec omap4-panda-es PASS: 1 min 10.4 sec omap3-tobi,3730storm PASS: 0 min 41.2 sec omap3-beagle PASS: 0 min 52.5 sec arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.5 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.3 sec imx6q-wandboard PASS: 0 min 15.1 sec arm-multi_v7_defconfig ---------------------- tegra30-beaver PASS: 0 min 15.1 sec am335x-boneblack PASS: 0 min 34.6 sec omap3-beagle-xm PASS: 0 min 51.8 sec armada-370-mirabox FAIL: 0 min 30.6 sec omap4-panda PASS: 1 min 1.2 sec omap4-panda-es PASS: 1 min 11.4 sec sun4i-a10-cubieboard PASS: 0 min 11.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec omap3-tobi,3530overo PASS: 0 min 40.7 sec am335x-bone PASS: 0 min 33.4 sec imx6q-wandboard PASS: 0 min 15.7 sec omap3-tobi,3730storm PASS: 0 min 39.7 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.6 sec omap3-beagle PASS: 0 min 53.5 sec arm-exynos_defconfig -------------------- exynos5250-arndale PASS: 0 min 30.1 sec arm-mvebu_defconfig ------------------- armada-370-mirabox FAIL: 0 min 30.6 sec arm-sama5_defconfig ------------------- sama5d35ek FAIL: 0 min 13.8 sec Console logs for failures ========================= arm-multi_v7_defconfig ---------------------- armada-370-mirabox: FAIL: last 24 lines of boot log: ---------------------------------------------------- Connected to mirabox console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset Command(mirabox console)> hardreset (user:jenkins) Reboot mirabox Reboot: mirabox ; ip9258 1 1 : off, sleep, on ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 30.59 seconds. # PYBOOT: Result: FAIL arm-mvebu_defconfig ------------------- armada-370-mirabox: FAIL: last 24 lines of boot log: ---------------------------------------------------- Connected to mirabox console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset cu: write: Input/output error Connected. cu: waitpid: No child processes Command(mirabox console)> hardreset (user:jenkins) Reboot mirabox Connected. Disconnected. Reboot: mirabox ; ip9258 1 1 : off, sleep, on ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 30.59 seconds. # PYBOOT: Result: FAIL arm-sama5_defconfig ------------------- sama5d35ek: FAIL: last 24 lines of boot log: -------------------------------------------- Process swapper (pid: 1, stack limit = 0xdf854238) Stack: (0xdf855eb8 to 0xdf856000) 5ea0: 00000000 00000000 5ec0: c0538618 c0529a34 c0260628 c051dc20 df854000 c0508484 00000000 c051dc50 5ee0: 00000000 c052f2c8 00000006 c0529a34 c0564b80 c0008780 df83e1c0 c00cbc20 5f00: c056ca4c df83e1c0 c03caf00 00000010 c0564b80 c04e46d0 00000000 00000001 5f20: c098d215 c03df988 0000007d c002fd60 c0564b80 c04e46d0 c04a6dd0 c04e3f00 5f40: 00000006 00000006 00000000 c052f2c8 00000006 c0529a34 c0564b80 0000007d 5f60: c0529a40 c0508484 00000000 c0508ad0 00000006 00000006 c0508484 fff7cfb7 5f80: b4dff7fc c4edfdeb 00000000 c03c01e8 00000000 00000000 00000000 00000000 5fa0: 00000000 c03c01f0 00000000 c000e2d8 00000000 00000000 00000000 00000000 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 eaeecabe f7a1c7bd [<c025d5b4>] (ohci_init_driver+0xa8/0x100) from [<c051dc50>] (ohci_at91_init+0x30/0x84) [<c051dc50>] (ohci_at91_init+0x30/0x84) from [<c0008780>] (do_one_initcall+0xec/0x148) [<c0008780>] (do_one_initcall+0xec/0x148) from [<c0508ad0>] (kernel_init_freeable+0xe8/0x1b0) [<c0508ad0>] (kernel_init_freeable+0xe8/0x1b0) from [<c03c01f0>] (kernel_init+0x8/0xe4) [<c03c01f0>] (kernel_init+0x8/0xe4) from [<c000e2d8>] (ret_from_fork+0x14/0x3c) Code: e5840048 e584104c e5842050 e5843054 (e5953000) ---[ end trace 2ce01bf77138c668 ]--- Kernel panic -~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: Kernel panic # PYBOOT: Time: 13.85 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

[PATCH v4 0/4] Target CPU=Host implementation for KVM ARM/ARM64

by Anup Patel

It will be very useful for user space (QEMU/KVMTOOL) if it has a method of querying VCPU target type matching to underlying Host. We can use such querying mechanism and implement machine models in user space where VCPU target type is always same-as/similar-to underlying Host (i.e. Target CPU=Host). This patch series implements KVM_ARM_PREFERRED_TARGET vm ioclt for querying VCPU target type matching underlying host. Using this new ioctl we can implement VCPU target CPU=Host in user space. Also, it is not mandatory to call KVM_ARM_PREFERRED_TARGET vm ioctl and the old method of trying all possible target types using the KVM_ARM_VCPU_INIT ioctl to initialize VCPU works fine. V4: - Fixed files exchanged between patches - For now return zeroed features in struct kvm_vcpu_init instance V3: - Return -ENODEV if no preferred target available for host - Make KVM_ARM_PREFERRED_TARGET ioctl as vm ioctl V2: - Renamed the ioclt to KVM_ARM_PREFERRED_TARGET - Return struct kvm_vcpu_init instace instead of just target type V1: - Initial patch-set with ioctl named as KVM_ARM_SUITABLE_TARGET Anup Patel (4): ARM: KVM: Implement kvm_vcpu_preferred_target() function ARM64: KVM: Implement kvm_vcpu_preferred_target() function ARM/ARM64: KVM: Implement KVM_ARM_PREFERRED_TARGET ioctl KVM: Add documentation for KVM_ARM_PREFERRED_TARGET ioctl Documentation/virtual/kvm/api.txt | 27 +++++++++++++++++++++++---- arch/arm/include/asm/kvm_host.h | 1 + arch/arm/kvm/arm.c | 13 +++++++++++++ arch/arm/kvm/guest.c | 20 ++++++++++++++++++++ arch/arm64/include/asm/kvm_host.h | 1 + arch/arm64/kvm/guest.c | 20 ++++++++++++++++++++ include/uapi/linux/kvm.h | 1 + 7 files changed, 79 insertions(+), 4 deletions(-) -- 1.7.9.5

11 years, 4 months

[PATCH 00/10] Convert to module_platform_driver() in video driver

by Hanjun Guo

This patch set just did one simple thing: convert to module_platform_driver() in video driver to simplify the code. Hanjun Guo (10): Video / hecubafb: Use module_platform_driver() to simplify code Video / bfin-t350mcqb-fb: Use module_platform_driver() to simplify code Video / metronomefb: Use module_platform_driver() to simplify code Video / jz4740_fb: Use module_platform_driver() to simplify code Video / da8xx-fb: Use module_platform_driver() to simplify code Video / cobalt_lcdfb: Use module_platform_driver() to simplify code Video / broadsheetfb: Use module_platform_driver() to simplify code Video / bf54x-lq043fb: Use module_platform_driver() to simplify code Video / au1200fb: Use module_platform_driver() to simplify code Video / au1100fb: Use module_platform_driver() to simplify code drivers/video/au1100fb.c | 14 +------------- drivers/video/au1200fb.c | 16 +--------------- drivers/video/bf54x-lq043fb.c | 14 +------------- drivers/video/bfin-t350mcqb-fb.c | 14 +------------- drivers/video/broadsheetfb.c | 14 +------------- drivers/video/cobalt_lcdfb.c | 14 +------------- drivers/video/da8xx-fb.c | 14 +------------- drivers/video/hecubafb.c | 14 +------------- drivers/video/jz4740_fb.c | 13 +------------ drivers/video/metronomefb.c | 14 +------------- 10 files changed, 10 insertions(+), 131 deletions(-) -- 1.7.9.5

11 years, 4 months

linus/master boot: 29 pass, 0 fail (v3.12-rc3)

by Kevin Hilman build bot

Automated DT boot report for various ARM defconfigs. Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo'). Tree/Branch: linus/master Git describe: v3.12-rc3 Commit: 15c03dd485 Linux 3.12-rc3 Full Report =========== arm-tegra_defconfig ------------------- tegra30-beaver PASS: 0 min 17.9 sec arm-omap2plus_defconfig ----------------------- am335x-boneblack PASS: 0 min 30.3 sec omap3-beagle-xm PASS: 0 min 52.5 sec am335x-bone PASS: 0 min 26.3 sec omap3-tobi,3530overo PASS: 0 min 42.4 sec omap4-panda PASS: 1 min 7.4 sec omap4-panda-es PASS: 1 min 10.3 sec omap3-tobi,3730storm PASS: 0 min 41.4 sec omap3-beagle PASS: 1 min 1.5 sec arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.4 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.2 sec imx6q-wandboard PASS: 0 min 15.0 sec arm-multi_v7_defconfig ---------------------- tegra30-beaver PASS: 0 min 15.0 sec am335x-boneblack PASS: 0 min 34.6 sec omap3-beagle-xm PASS: 0 min 48.0 sec armada-370-mirabox PASS: 0 min 19.5 sec omap4-panda PASS: 1 min 0.9 sec omap4-panda-es PASS: 1 min 9.7 sec sun4i-a10-cubieboard PASS: 0 min 11.6 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.4 sec omap3-tobi,3530overo PASS: 0 min 40.8 sec am335x-bone PASS: 0 min 33.4 sec imx6q-wandboard PASS: 0 min 15.7 sec omap3-tobi,3730storm PASS: 0 min 39.8 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.6 sec omap3-beagle PASS: 1 min 2.4 sec arm-exynos_defconfig -------------------- exynos5250-arndale PASS: 0 min 30.0 sec arm-mvebu_defconfig ------------------- armada-370-mirabox PASS: 0 min 19.3 sec arm-sama5_defconfig ------------------- sama5d35ek PASS: 0 min 18.6 sec

11 years, 4 months

linus/master boot: 27 pass, 2 fail (v3.12-rc2-193-gcac6653)

by Kevin Hilman build bot

Automated DT boot report for various ARM defconfigs. Boot test simply checks if kernel can boot to initramfs with busybox and run some basic commands (e.g. 'cat /proc/cpuinfo'). Tree/Branch: linus/master Git describe: v3.12-rc2-193-gcac6653 Commit: cac6653529 Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Failed boot tests (console logs at the end) =========================================== tegra30-beaver: FAIL: arm-tegra_defconfig tegra30-beaver: FAIL: arm-multi_v7_defconfig Full Report =========== arm-tegra_defconfig ------------------- tegra30-beaver FAIL: 0 min 46.3 sec arm-omap2plus_defconfig ----------------------- am335x-boneblack PASS: 0 min 29.8 sec omap3-beagle-xm PASS: 0 min 51.9 sec am335x-bone PASS: 0 min 31.3 sec omap3-tobi,3530overo PASS: 0 min 42.3 sec omap4-panda PASS: 1 min 10.0 sec omap4-panda-es PASS: 1 min 14.3 sec omap3-tobi,3730storm PASS: 0 min 41.2 sec omap3-beagle PASS: 1 min 2.0 sec arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.4 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.4 sec imx6q-wandboard PASS: 0 min 15.1 sec arm-multi_v7_defconfig ---------------------- tegra30-beaver FAIL: 2 min 13.2 sec am335x-boneblack PASS: 0 min 39.6 sec omap3-beagle-xm PASS: 0 min 52.0 sec armada-370-mirabox PASS: 0 min 19.4 sec omap4-panda PASS: 1 min 1.4 sec omap4-panda-es PASS: 1 min 8.2 sec sun4i-a10-cubieboard PASS: 0 min 14.6 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec omap3-tobi,3530overo PASS: 0 min 41.0 sec am335x-bone PASS: 0 min 33.4 sec imx6q-wandboard PASS: 0 min 15.7 sec omap3-tobi,3730storm PASS: 0 min 39.9 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.6 sec omap3-beagle PASS: 1 min 5.6 sec arm-exynos_defconfig -------------------- exynos5250-arndale PASS: 0 min 29.9 sec arm-mvebu_defconfig ------------------- armada-370-mirabox PASS: 0 min 19.3 sec arm-sama5_defconfig ------------------- sama5d35ek PASS: 0 min 18.4 sec Console logs for failures ========================= arm-tegra_defconfig ------------------- tegra30-beaver: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 3.644436] tegra-ehci 7d008000.usb: irq 129, io mem 0x7d008000 [ 3.663503] tegra-ehci 7d008000.usb: USB 2.0 started, EHCI 1.00 [ 3.670014] hub 1-0:1.0: USB hub found [ 3.673794] hub 1-0:1.0: 1 port detected [ 3.678542] tegra_rtc 7000e000.rtc: setting system clock to 1970-01-01 00:00:12 UTC (12) [ 3.686878] ALSA device list: [ 3.689836] #0: NVIDIA Tegra Beaver [ 3.693839] Freeing unused kernel memory: 232K (c0742000 - c077c000) Starting logging: OK Initializing random number generator... done. Starting network... /bin/sh: can't access tty; job control turned off / # cat /proc/cmdline cat /proc/cmdline console=ttyS0,115200n8 debug earlyprintk / # uname -r uname -r 3.12.0-rc2-00193-gcac6653 / # [ 3.993551] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 4.485511] asix 1-1:1.0 eth1: register 'asix' at usb-7d008000.usb-1, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:55:d1:b9 ~$off # PYBOOT: Exception: ERROR: Timeout waiting for command: uname -r. # PYBOOT: Time: 46.29 seconds. # PYBOOT: Result: FAIL arm-multi_v7_defconfig ---------------------- tegra30-beaver: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 1.524125] platform 1.regulator: Driver reg-fixed-voltage requests probe deferral [ 1.532193] platform 2.regulator: Driver reg-fixed-voltage requests probe deferral /bin/sh: can't access tty; job control tu[ 1.540086] platform 6.regulator: Driver reg-fixed-voltage requests probe deferral rned off / # [ 1.551208] sys_3v3_pexs: 3300 mV [ 1.555574] reg-fixed-voltage 7.regulator: Failed to find supply vin [ 1.561967] reg-fixed-voltage 7.regulator: Failed to register regulator: -517 [ 1.569122] platform 7.regulator: Driver reg-fixed-voltage requests probe deferral [ 1.576929] tegra-hdmi 54280000.hdmi: failed to get VDD regulator [ 1.583013] platform 54280000.hdmi: Driver tegra-hdmi requests probe deferral [ 1.703066] usb 1-1: new high-speed USB device number 2 using tegra-ehci [ 1.871639] platform 1.regulator: Driver reg-fixed-voltage requests probe deferral [ 1.879387] platform 2.regulator: Driver reg-fixed-voltage requests probe deferral [ 1.887094] platform 6.regulator: Driver reg-fixed-voltage requests probe deferral [ 1.894852] sys_3v3_pexs: 3300 mV [ 1.898264] reg-fixed-voltage 7.regulator: Failed to find supply vin [ 1.904661] reg-fixed-voltage 7.regulator: Failed to register regulator: -517 [ 1.911783] platform 7.regulator: Driver reg-fixed-voltage requests probe deferral [ 1.919549] tegra-hdmi 54280000.hdmi: failed to get VDD regulator [ 1.925646] platform 54280000.hdmi: Driver tegra-hdmi requests probe deferral ~$off # PYBOOT: Exception: userspace: ERROR: Never found root shell # PYBOOT: Time: 133.20 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

[PATCH 1/2] ide / au1xxx-ide: Use module_platform_driver() to simplify code

by Hanjun Guo

Convert to module_platform_driver() to simplify code. Signed-off-by: Hanjun Guo <hanjun.guo(a)linaro.org> --- drivers/ide/au1xxx-ide.c | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/drivers/ide/au1xxx-ide.c b/drivers/ide/au1xxx-ide.c index 259786c..bdaf8a5 100644 --- a/drivers/ide/au1xxx-ide.c +++ b/drivers/ide/au1xxx-ide.c @@ -591,19 +591,7 @@ static struct platform_driver au1200_ide_driver = { .probe = au_ide_probe, .remove = au_ide_remove, }; - -static int __init au_ide_init(void) -{ - return platform_driver_register(&au1200_ide_driver); -} - -static void __exit au_ide_exit(void) -{ - platform_driver_unregister(&au1200_ide_driver); -} +module_paltform_driver(au1200_ide_driver); MODULE_LICENSE("GPL"); MODULE_DESCRIPTION("AU1200 IDE driver"); - -module_init(au_ide_init); -module_exit(au_ide_exit); -- 1.7.9.5

11 years, 4 months

Please help! Can't build correct kernel for 13.07 linaro-ubuntu on pandaboard

by Chao Xu

Hi, I tried to build linaro kernel for pandaboard. I have tried everything what I can think of but the kernel still can't boot correctly. Any help will be appreciated. Here is what I did: 1. I flash the 13.07 linaro-ubuntu-pandaboard image into the sd card ( http://releases.linaro.org/13.07/ubuntu/panda). This image works fine. 2. I clone the kernel source code from git:// git.linaro.org/kernel/linux-linaro-stable.git. 3. checkout the lsk 13.07 tag. 4. copy the config file from original image (i.e. /boot/config-3.10.1.0-1-linaro-omap). 5. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- CFLAGS="-O" LOADADDR=0x80008000 uImage The cross compiler on my machine is gcc-4.7-arm-linux-gnueabihf-base 6. From pandaboard, I load the built uImage via scp. The problem I met: 1. In most cases, the kernel can't boot correctly. And the terminal keeps printing "hub 1-1:1.0: hub_port_status failed (err = -71)". 2.Sometime, the kernel can finish booting. But the terminal prints for several times the aforementioned error message after booting. Plus, I don't have any module running, 'lsmod' shows nothing. Please help! Thank you. -- Regards, Chao Xu

11 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel September 2013