Re: [BUG] PandaBoard hangs before starting init while booting v3.12
* Ben Gamari [131118 07:14]: > I'm having difficulty getting a PandaBoard ES rev. B1 to boot v3.12 and > linux-next (30121118). I'm booting with a brand new u-boot > (c2e5e802ecb7ab668ce9911b210ed68c804b349f). > > In both cases the device appears to hang shortly before one would expect > init to start as seen in the boot output below. I'm booting with the > omap4-panda-es devicetree. As far as I can tell, the machine is > completely dead and will not respond to even sysrq. I have a PandaBoard > A4 which apparently has no trouble with the same kernel image. Do you have the same version of u-boot in both cases? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
Tony Lindgren writes: > * Ben Gamari [131118 07:14]: >> I'm having difficulty getting a PandaBoard ES rev. B1 to boot v3.12 and >> linux-next (30121118). I'm booting with a brand new u-boot >> (c2e5e802ecb7ab668ce9911b210ed68c804b349f). >> >> In both cases the device appears to hang shortly before one would expect >> init to start as seen in the boot output below. I'm booting with the >> omap4-panda-es devicetree. As far as I can tell, the machine is >> completely dead and will not respond to even sysrq. I have a PandaBoard >> A4 which apparently has no trouble with the same kernel image. > > Do you have the same version of u-boot in both cases? > Yes. Cheers, - Ben pgpEaFDgfl713.pgp Description: PGP signature
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
Hi Ben, On Monday 18 November 2013 08:44 PM, Ben Gamari wrote: > I'm having difficulty getting a PandaBoard ES rev. B1 to boot v3.12 and > linux-next (30121118). I'm booting with a brand new u-boot > (c2e5e802ecb7ab668ce9911b210ed68c804b349f). > > In both cases the device appears to hang shortly before one would expect > init to start as seen in the boot output below. I'm booting with the > omap4-panda-es devicetree. As far as I can tell, the machine is > completely dead and will not respond to even sysrq. I have a PandaBoard > A4 which apparently has no trouble with the same kernel image. Which defconfig are you using ? Can you see if CPU_IDLE is enabled in your defconfig? I saw a similar failure on my panda es when CPU_IDLE is enabled. If this is the case for you please apply this[1] patch and give a try. Hope this helps. Let me know if you need more info. [1] https://patchwork.kernel.org/patch/3084521/ Thanks and regards, Lokesh > > The only issues I can see in the output are, > > * pinctrl issues pertaining to wl12xx[1], these shouldn't cause the > machine not to boot > * Various missing vmmc regulators > * hw-breakpoint issues: > * Failed to enable monitor mode on CPU 0 > * CPU 0 failed to disable vector catch > These sound serious and occur near the hang. Perhaps this is the culprit? > > Any help would be greatly appreciated. > > Cheers, > > - Ben > > > [1] http://www.spinics.net/lists/devicetree/msg07983.html > > > reading uEnv-new.txt > 1147 bytes read in 5 ms (223.6 KiB/s) > Importing environment from mmc0 ... > Running uenvcmd ... > reading zImage-new > 3738608 bytes read in 172 ms (20.7 MiB/s) > reading uInitrd-new.img > 3241151 bytes read in 157 ms (19.7 MiB/s) > reading /dtbs-new/omap4-panda-es.dtb > 20188 bytes read in 10 ms (1.9 MiB/s) > Kernel image @ 0x8030 [ 0x00 - 0x390bf0 ] > ## Loading init Ramdisk from Legacy Image at 8160 ... >Image Name: >Image Type: ARM Linux RAMDisk Image (gzip compressed) >Data Size:3241087 Bytes = 3.1 MiB >Load Address: 8160 >Entry Point: 8160 >Verifying Checksum ... OK > ## Flattened Device Tree blob at 815f >Booting using the fdt blob at 0x815f >Loading Ramdisk to 8fce8000, end 847f ... OK >Using Device Tree in place at 815f, end 815f7edb > > Starting kernel ... > > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Initializing cgroup subsys cpuset > [0.00] Initializing cgroup subsys cpu > [0.00] Initializing cgroup subsys cpuacct > [0.00] Linux version 3.12.0-next-20131118 (ben@ben-server) (gcc > version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #11 SMP Mon Nov 18 02:24:43 > EST 2013 > [0.00] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), > cr=10c5387d > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing > instruction cache > [0.00] Machine model: TI OMAP4 PandaBoard > [0.00] bootconsole [earlycon0] enabled > [0.00] Memory policy: Data cache writealloc > [0.00] OMAP4460 ES1.1 > [0.00] PERCPU: Embedded 9 pages/cpu @c13c8000 s13568 r8192 d15104 > u36864 > [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total > pages: 260368 > [0.00] Kernel command line: console=ttyO2,115200n8 earlyprintk > initcall_debug vram=16M omapfb.mode=: omapdss.def_disp= root=/dev/mmcblk0p5 > ro rootfstype=ext4 fixrtc > [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) > [0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 > bytes) > [0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > [0.00] allocated 2097152 bytes of page_cgroup > [0.00] please try 'cgroup_disable=memory' option if you don't want > memory cgroups > [0.00] Memory: 1021188K/1047552K available (7108K kernel code, 620K > rwdata, 2940K rodata, 457K init, 833K bss, 26364K reserved, 269312K highmem) > [0.00] Virtual kernel memory layout: > [0.00] vector : 0x - 0x1000 ( 4 kB) > [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) > [0.00] vmalloc : 0xf000 - 0xff00 ( 240 MB) > [0.00] lowmem : 0xc000 - 0xef80 ( 760 MB) > [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) > [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) > [0.00] .text : 0xc0008000 - 0xc09d845c (10050 kB) > [0.00] .init : 0xc09d9000 - 0xc0a4b500 ( 458 kB) > [0.00] .data : 0xc0a4c000 - 0xc0ae7350 ( 621 kB) > [0.00].bss : 0xc0ae7350 - 0xc0bb79b8 ( 834 kB) > [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 > [0.00] Hierarchical RCU implementation. > [0.00] NR_IRQS:16 nr_irqs:16 16 > [0.00] OMAP clockevent source: timer1 at 32768 Hz > [0.00] sched_clock: 32 bits a
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
Lokesh Vutla writes: > Hi Ben, > On Monday 18 November 2013 08:44 PM, Ben Gamari wrote: >> I'm having difficulty getting a PandaBoard ES rev. B1 to boot v3.12 and >> linux-next (30121118). I'm booting with a brand new u-boot >> (c2e5e802ecb7ab668ce9911b210ed68c804b349f). >> >> In both cases the device appears to hang shortly before one would expect >> init to start as seen in the boot output below. I'm booting with the >> omap4-panda-es devicetree. As far as I can tell, the machine is >> completely dead and will not respond to even sysrq. I have a PandaBoard >> A4 which apparently has no trouble with the same kernel image. > > Which defconfig are you using ? > I derived the config from RobertCNelson's Debian Wheezy image. It did require some modification, however. > Can you see if CPU_IDLE is enabled in your defconfig? > Yes, CPU_IDLE is enabled. > I saw a similar failure on my panda es when CPU_IDLE is enabled. > If this is the case for you please apply this[1] patch and give a try. > Indeed that did the trick. Thanks for the reference! I do however now see periodic messages of the form, [ 42.143005] gic_timer_retrigger: lost localtimer interrupt Any idea what this might be due to? Cheers, - Ben pgpubspGDYvbs.pgp Description: PGP signature
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
Hi, I also try to boot v3.12 on my pandaboard rev A2, but it hangs at "starting kernel". My SD card is originally loaded with a linaro 12.04 ubuntu-developer image. I have tried with v3.7 and v3.8 uImage and both of them work normally, but v3.12 hangs. Is there any trick I missed? Do I need to use the new u-boot as used by Ben? And here is a separate problem with building u-boot. I cloned the upstream u-boot repository. The latest commit is c2e5e802ecb7ab668ce9911b210ed68c804b349f. Then I did: make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap4_panda_config make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j8 cp MLO u-boot.img /media/boot/ But when turn on my pandaboard, there is NO output from the serial console. I didn't change the other file in the boot partition. They are from linaro 12.04 ubuntu-developer image. Any help would be much appreciated! On Mon, Nov 18, 2013 at 9:14 AM, Ben Gamari wrote: > I'm having difficulty getting a PandaBoard ES rev. B1 to boot v3.12 and > linux-next (30121118). I'm booting with a brand new u-boot > (c2e5e802ecb7ab668ce9911b210ed68c804b349f). > > In both cases the device appears to hang shortly before one would expect > init to start as seen in the boot output below. I'm booting with the > omap4-panda-es devicetree. As far as I can tell, the machine is > completely dead and will not respond to even sysrq. I have a PandaBoard > A4 which apparently has no trouble with the same kernel image. > > The only issues I can see in the output are, > > * pinctrl issues pertaining to wl12xx[1], these shouldn't cause the > machine not to boot > * Various missing vmmc regulators > * hw-breakpoint issues: > * Failed to enable monitor mode on CPU 0 > * CPU 0 failed to disable vector catch > These sound serious and occur near the hang. Perhaps this is the culprit? > > Any help would be greatly appreciated. > > Cheers, > > - Ben > > > [1] http://www.spinics.net/lists/devicetree/msg07983.html > > > reading uEnv-new.txt > 1147 bytes read in 5 ms (223.6 KiB/s) > Importing environment from mmc0 ... > Running uenvcmd ... > reading zImage-new > 3738608 bytes read in 172 ms (20.7 MiB/s) > reading uInitrd-new.img > 3241151 bytes read in 157 ms (19.7 MiB/s) > reading /dtbs-new/omap4-panda-es.dtb > 20188 bytes read in 10 ms (1.9 MiB/s) > Kernel image @ 0x8030 [ 0x00 - 0x390bf0 ] > ## Loading init Ramdisk from Legacy Image at 8160 ... >Image Name: >Image Type: ARM Linux RAMDisk Image (gzip compressed) >Data Size:3241087 Bytes = 3.1 MiB >Load Address: 8160 >Entry Point: 8160 >Verifying Checksum ... OK > ## Flattened Device Tree blob at 815f >Booting using the fdt blob at 0x815f >Loading Ramdisk to 8fce8000, end 847f ... OK >Using Device Tree in place at 815f, end 815f7edb > > Starting kernel ... > > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Initializing cgroup subsys cpuset > [0.00] Initializing cgroup subsys cpu > [0.00] Initializing cgroup subsys cpuacct > [0.00] Linux version 3.12.0-next-20131118 (ben@ben-server) (gcc > version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #11 SMP Mon Nov 18 02:24:43 > EST 2013 > [0.00] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), > cr=10c5387d > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing > instruction cache > [0.00] Machine model: TI OMAP4 PandaBoard > [0.00] bootconsole [earlycon0] enabled > [0.00] Memory policy: Data cache writealloc > [0.00] OMAP4460 ES1.1 > [0.00] PERCPU: Embedded 9 pages/cpu @c13c8000 s13568 r8192 d15104 > u36864 > [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total > pages: 260368 > [0.00] Kernel command line: console=ttyO2,115200n8 earlyprintk > initcall_debug vram=16M omapfb.mode=: omapdss.def_disp= root=/dev/mmcblk0p5 > ro rootfstype=ext4 fixrtc > [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) > [0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 > bytes) > [0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > [0.00] allocated 2097152 bytes of page_cgroup > [0.00] please try 'cgroup_disable=memory' option if you don't want > memory cgroups > [0.00] Memory: 1021188K/1047552K available (7108K kernel code, 620K > rwdata, 2940K rodata, 457K init, 833K bss, 26364K reserved, 269312K highmem) > [0.00] Virtual kernel memory layout: > [0.00] vector : 0x - 0x1000 ( 4 kB) > [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) > [0.00] vmalloc : 0xf000 - 0xff00 ( 240 MB) > [0.00] lowmem : 0xc000 - 0xef80 ( 760 MB) > [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) > [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) > [0.00] .text : 0xc0008000 - 0xc09
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
Chao Xu writes: > Hi, > > I also try to boot v3.12 on my pandaboard rev A2, but it hangs at > "starting kernel". My SD card is originally loaded with a linaro 12.04 > ubuntu-developer image. I have tried with v3.7 and v3.8 uImage and > both of them work normally, but v3.12 hangs. Is there any trick I > missed? Do I need to use the new u-boot as used by Ben? > I've written up some of my experiences bringing up 3.12 on the PandaBoard here[1]. You may find it helpful. Regardless, I would definitely try upgrading u-boot. > And here is a separate problem with building u-boot. I cloned the > upstream u-boot repository. The latest commit is > c2e5e802ecb7ab668ce9911b210ed68c804b349f. Then I did: > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap4_panda_config > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j8 > cp MLO u-boot.img /media/boot/ > But when turn on my pandaboard, there is NO output from the serial > console. I didn't change the other file in the boot partition. They > are from linaro 12.04 ubuntu-developer image. > I would check that you have earlyprintk enabled (both in the kernel configuration as well as on the kernel command line). Moreover, ensure that the correct serial devices is selected for low-level debug output (in the kernel configuration). Cheers, - Ben [1] http://bgamari.github.io/posts/2013-11-17-running-modern-kernel-on-pandaboard.html pgpXEq97V9CLv.pgp Description: PGP signature
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
* Ben Gamari [131119 19:07]: > Chao Xu writes: > > > Hi, > > > > I also try to boot v3.12 on my pandaboard rev A2, but it hangs at > > "starting kernel". My SD card is originally loaded with a linaro 12.04 > > ubuntu-developer image. I have tried with v3.7 and v3.8 uImage and > > both of them work normally, but v3.12 hangs. Is there any trick I > > missed? Do I need to use the new u-boot as used by Ben? > > > I've written up some of my experiences bringing up 3.12 on the > PandaBoard here[1]. You may find it helpful. Regardless, I would > definitely try upgrading u-boot. Nice investigative blogging :) Care to also update it with the other issues remaining on pandaboard? Sounds like we're pretty close to having things working nicely with mainline kernel on it, so let's just fix those issues ASAP. I'm aware of at least two issues: 1. The WLAN not working after a soft reset, or if the interface is reset with ifconfig down. This could be a typo somewhere in the .dts file for the WLAN regulator or something like that. 2. Suspend and resume does not wake-up from serial console and spews a bunch of warnings. The wake-up issue can be fixed with the new the new interrupts-extended property to use the wake IRQs, I'll try to update my patches for that today. > > And here is a separate problem with building u-boot. I cloned the > > upstream u-boot repository. The latest commit is > > c2e5e802ecb7ab668ce9911b210ed68c804b349f. Then I did: > > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap4_panda_config > > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j8 > > cp MLO u-boot.img /media/boot/ > > But when turn on my pandaboard, there is NO output from the serial > > console. I didn't change the other file in the boot partition. They > > are from linaro 12.04 ubuntu-developer image. > > > I would check that you have earlyprintk enabled (both in the kernel > configuration as well as on the kernel command line). Moreover, ensure > that the correct serial devices is selected for low-level debug output > (in the kernel configuration). I wonder if we also have some dependency to some earlier versions of u-boot as u-boot now only muxes the essential pins? Regards, Tony > [1] > http://bgamari.github.io/posts/2013-11-17-running-modern-kernel-on-pandaboard.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
Tony Lindgren writes: > * Ben Gamari [131119 19:07]: >> Chao Xu writes: >> >> > Hi, >> > >> > I also try to boot v3.12 on my pandaboard rev A2, but it hangs at >> > "starting kernel". My SD card is originally loaded with a linaro 12.04 >> > ubuntu-developer image. I have tried with v3.7 and v3.8 uImage and >> > both of them work normally, but v3.12 hangs. Is there any trick I >> > missed? Do I need to use the new u-boot as used by Ben? >> > >> I've written up some of my experiences bringing up 3.12 on the >> PandaBoard here[1]. You may find it helpful. Regardless, I would >> definitely try upgrading u-boot. > > Nice investigative blogging :) > Thanks! > Care to also update it with the other issues remaining on pandaboard? > Sure. > Sounds like we're pretty close to having things working nicely with > mainline kernel on it, so let's just fix those issues ASAP. > > I'm aware of at least two issues: > > 1. The WLAN not working after a soft reset, or if the interface is > reset with ifconfig down. This could be a typo somewhere in the > .dts file for the WLAN regulator or something like that. > Yes, although frankly I've more or less given up on the wl12xx. This is really a matter for linux-wireless@ but for some reason I find that it is terribly unreliable. It stay associated without a problem but for some reason I encounter extremely long (>2 seconds) dropouts where no traffic can get in or out. Nothing is logged so I really have no idea how to go about debugging this. Ultimately Ethernet is fine for my purposes anyways. > 2. Suspend and resume does not wake-up from serial console and spews >a bunch of warnings. The wake-up issue can be fixed with the new >the new interrupts-extended property to use the wake IRQs, I'll >try to update my patches for that today. > Thankfully this is for a build-bot so this should be a problem for me. I'll mention these in the write-up. >> > And here is a separate problem with building u-boot. I cloned the >> > upstream u-boot repository. The latest commit is >> > c2e5e802ecb7ab668ce9911b210ed68c804b349f. Then I did: >> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap4_panda_config >> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j8 >> > cp MLO u-boot.img /media/boot/ >> > But when turn on my pandaboard, there is NO output from the serial >> > console. I didn't change the other file in the boot partition. They >> > are from linaro 12.04 ubuntu-developer image. >> > >> I would check that you have earlyprintk enabled (both in the kernel >> configuration as well as on the kernel command line). Moreover, ensure >> that the correct serial devices is selected for low-level debug output >> (in the kernel configuration). > > I wonder if we also have some dependency to some earlier versions of > u-boot as u-boot now only muxes the essential pins? > I haven't been very careful in characterizing the behavior of various u-boot versions (although I've tried several) so I'm afraid I can't say. Thanks again for your help. Cheers, - Ben pgpd9LIe1qEX3.pgp Description: PGP signature
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
"I wonder if we also have some dependency to some earlier versions of u-boot as u-boot now only muxes the essential pins?" This is exactly the problem in my case. I added "#define CONFIG_SYS_ENABLE_PADS_ALL" in u-boot/include/configs/omap4_common.h and now there is output. I guess the reason that the u-boot worked out-of-box for Ben but not for me is that I missed some configurations in v3.12 kernel. I image there is a config options that tells the kernel to take care of the non-essential pins that used to be the responsibility of u-boot. Could you confirm my hypothesis? And if so, could you kindly suggest what's the name of the config option? Thank you! On Wed, Nov 20, 2013 at 12:35 PM, Tony Lindgren wrote: > * Ben Gamari [131119 19:07]: >> Chao Xu writes: >> >> > Hi, >> > >> > I also try to boot v3.12 on my pandaboard rev A2, but it hangs at >> > "starting kernel". My SD card is originally loaded with a linaro 12.04 >> > ubuntu-developer image. I have tried with v3.7 and v3.8 uImage and >> > both of them work normally, but v3.12 hangs. Is there any trick I >> > missed? Do I need to use the new u-boot as used by Ben? >> > >> I've written up some of my experiences bringing up 3.12 on the >> PandaBoard here[1]. You may find it helpful. Regardless, I would >> definitely try upgrading u-boot. > > Nice investigative blogging :) > > Care to also update it with the other issues remaining on pandaboard? > Sounds like we're pretty close to having things working nicely with > mainline kernel on it, so let's just fix those issues ASAP. > > I'm aware of at least two issues: > > 1. The WLAN not working after a soft reset, or if the interface is > reset with ifconfig down. This could be a typo somewhere in the > .dts file for the WLAN regulator or something like that. > > 2. Suspend and resume does not wake-up from serial console and spews >a bunch of warnings. The wake-up issue can be fixed with the new >the new interrupts-extended property to use the wake IRQs, I'll >try to update my patches for that today. > >> > And here is a separate problem with building u-boot. I cloned the >> > upstream u-boot repository. The latest commit is >> > c2e5e802ecb7ab668ce9911b210ed68c804b349f. Then I did: >> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap4_panda_config >> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j8 >> > cp MLO u-boot.img /media/boot/ >> > But when turn on my pandaboard, there is NO output from the serial >> > console. I didn't change the other file in the boot partition. They >> > are from linaro 12.04 ubuntu-developer image. >> > >> I would check that you have earlyprintk enabled (both in the kernel >> configuration as well as on the kernel command line). Moreover, ensure >> that the correct serial devices is selected for low-level debug output >> (in the kernel configuration). > > I wonder if we also have some dependency to some earlier versions of > u-boot as u-boot now only muxes the essential pins? > > Regards, > > Tony > > >> [1] >> http://bgamari.github.io/posts/2013-11-17-running-modern-kernel-on-pandaboard.html > > -- Regards, Chao Xu -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
* Chao Xu [131122 19:28]: > "I wonder if we also have some dependency to some earlier versions of > u-boot as u-boot now only muxes the essential pins?" > This is exactly the problem in my case. I added "#define > CONFIG_SYS_ENABLE_PADS_ALL" in u-boot/include/configs/omap4_common.h > and now there is output. > > I guess the reason that the u-boot worked out-of-box for Ben but not > for me is that I missed some configurations in v3.12 kernel. I image > there is a config options that tells the kernel to take care of the > non-essential pins that used to be the responsibility of u-boot. Could > you confirm my hypothesis? And if so, could you kindly suggest what's > the name of the config option? That would be CONFIG_PINCTRL_SINGLE=y for device tree based omaps. But if we have the configuration missing for some driver in the board specific .dts file, that won't help naturally. We do have PINCTRL_SINGLE enabled in omap2plus_defconfig. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
Thanks, Tony. I checked my .config and this option is enabled. FYI, I raised this issue in u-boot mailing-list, too. It seems to be a bug in u-boot and only happens to certain version of pandaboard. The name of the thread is "No single character output after update to latest u-boot on pandaboard" On Tue, Nov 26, 2013 at 12:20 PM, Tony Lindgren wrote: > * Chao Xu [131122 19:28]: >> "I wonder if we also have some dependency to some earlier versions of >> u-boot as u-boot now only muxes the essential pins?" >> This is exactly the problem in my case. I added "#define >> CONFIG_SYS_ENABLE_PADS_ALL" in u-boot/include/configs/omap4_common.h >> and now there is output. >> >> I guess the reason that the u-boot worked out-of-box for Ben but not >> for me is that I missed some configurations in v3.12 kernel. I image >> there is a config options that tells the kernel to take care of the >> non-essential pins that used to be the responsibility of u-boot. Could >> you confirm my hypothesis? And if so, could you kindly suggest what's >> the name of the config option? > > That would be CONFIG_PINCTRL_SINGLE=y for device tree based omaps. > But if we have the configuration missing for some driver in the > board specific .dts file, that won't help naturally. We do have > PINCTRL_SINGLE enabled in omap2plus_defconfig. > > Regards, > > Tony -- Regards, Chao Xu -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] PandaBoard hangs before starting init while booting v3.12
* Chao Xu [131126 12:00]: > Thanks, Tony. I checked my .config and this option is enabled. FYI, I > raised this issue in u-boot mailing-list, too. It seems to be a bug in > u-boot and only happens to certain version of pandaboard. The name of > the thread is "No single character output after update to latest > u-boot on pandaboard" OK thanks for the info. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
