| Message ID | 1369663662-7340-1-git-send-email-sumit.semwal@linaro.org |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Mon, 2013-05-27 at 19:37 +0530, Sumit Semwal wrote: > vexpress64.conf is missing some key CONFIGs about Regulators, > which cause the kernel to complain about mmc voltages, and panic. > > These additional configs seem to help. Which kernel tree, config (android/ubuntu/ubuntu-minimal?), root filesystem (Android/OE?), RTSM and device-tree are you using? I don't doubt that these are probably needed (they are for 32-bit vexpress) but am wondering why we haven't seen this problem before. Thanks
Hi Tixy, On 28 May 2013 16:24, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: > On Mon, 2013-05-27 at 19:37 +0530, Sumit Semwal wrote: >> vexpress64.conf is missing some key CONFIGs about Regulators, >> which cause the kernel to complain about mmc voltages, and panic. >> >> These additional configs seem to help. > > Which kernel tree, config (android/ubuntu/ubuntu-minimal?), root > filesystem (Android/OE?), RTSM and device-tree are you using? I am using linux-linaro branch of linux-linaro-tracking tree: ubuntu-minimal for OE rootfs, RTSM and rtsm_ve-aemv8a.dts. Without these configs, I get mmc errors; I stumbled upon an old bug report where you had suggested. > > I don't doubt that these are probably needed (they are for 32-bit > vexpress) but am wondering why we haven't seen this problem before. > > Thanks > > -- > Tixy > >> Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org> >> --- >> linaro/configs/vexpress64.conf | 5 +++++ >> 1 file changed, 5 insertions(+) >> >> diff --git a/linaro/configs/vexpress64.conf b/linaro/configs/vexpress64.conf >> index 9087e4e..32b638f 100644 >> --- a/linaro/configs/vexpress64.conf >> +++ b/linaro/configs/vexpress64.conf >> @@ -28,3 +28,8 @@ CONFIG_VIRTIO_BLK=y >> CONFIG_VIRTIO_MMIO=y >> CONFIG_REGULATOR=y >> CONFIG_REGULATOR_FIXED_VOLTAGE=y >> +CONFIG_SENSORS_VEXPRESS=y >> +CONFIG_REGULATOR_VEXPRESS=y >> +CONFIG_NEW_LEDS=y >> +CONFIG_LEDS_CLASS=y >> +CONFIG_LEDS_REGULATOR=y > > -- Thanks and regards, Sumit Semwal Graphics Engineer - Graphics working group Linaro.org │ Open source software for ARM SoCs
On Tue, 2013-05-28 at 16:47 +0530, Sumit Semwal wrote: > Hi Tixy, > > On 28 May 2013 16:24, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: > > On Mon, 2013-05-27 at 19:37 +0530, Sumit Semwal wrote: > >> vexpress64.conf is missing some key CONFIGs about Regulators, > >> which cause the kernel to complain about mmc voltages, and panic. > >> > >> These additional configs seem to help. > > > > Which kernel tree, config (android/ubuntu/ubuntu-minimal?), root > > filesystem (Android/OE?), RTSM and device-tree are you using? > I am using linux-linaro branch of linux-linaro-tracking tree: > ubuntu-minimal for OE rootfs, RTSM and rtsm_ve-aemv8a.dts. Without > these configs, I get mmc errors; I stumbled upon an old bug report > where you had suggested. With a kernel built from the current linux-linaro I'm able to boot the 13.04 OE minimal image fine, and I've been booting Juice OK on the AEMv8 models regularly using the same vexpress64.conf. In order to try and understand what's going on can you mail me a full log of your kernel boot? And also tell me the command-line you are using to run the models and also what bootwrapper you are using and the options used to build that? Finally, how old is your model? I have version 0.8 from about 6 months ago, do you have a newer version? It would be interesting to see how our setups differ. I've been using this bootwrapper: https://git.linaro.org/gitweb?p=arm/models/boot-wrapper-aarch64.git;a=commit;h=26b62f586020fd998c6efd43db657eaafeec14da And I use make rules below to build a kernel and run an oe image, build_kernel64_oe: bash -c "pushd ${KERNELDIR} && ARCH=arm64 scripts/kconfig/merge_config.sh linaro/configs/linaro-base.conf linaro/configs/ubuntu-minimal.conf linaro/configs/vexpress64.conf && popd" export PATH=${PATH}:/data/arm64/aarch64-toolchain/gcc-linaro-aarch64-linux-gnu-4.7+bzr115029-20121015+bzr2506_linux/bin && \ make -C ${KERNELDIR} ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j 5 Image modules run_rtsm64_oe_ve: # ssh -L 8224:localhost:8224 -L 18224:localhost:18224 -N flexlm.linaro.org cd /data/arm64/boot-wrapper-aarch64 && \ git zap . && \ git checkout origin/ubuntu && \ ln -sf ${KERNELDIR}/scripts/dtc/dtc && \ ln -sf ${KERNELDIR}/arch/arm64/boot/Image && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/skeleton.dtsi && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-v2m-rs1.dtsi && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-foundation-v8.dts && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-v2p-aarch64.dts && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/foundation-v8.dts && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/rtsm_ve-aemv8a.dts && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/rtsm_ve-motherboard.dtsi && \ ln -sf ${KERNELDIR}/arch/arm64/boot/dts/new.dts && \ export PATH=${PATH}:/data/arm64/aarch64-toolchain/gcc-linaro-aarch64-linux-gnu-4.7+bzr115029-20121015+bzr2506_linux/bin && \ make CROSS_COMPILE=aarch64-linux-gnu- FDT_SRC=vexpress-v2p-aarch64.dts BOOTARGS='"root=/dev/mmcblk0p2 consolelog=9 rw console=ttyAMA0 debug earlyprintk"' export ARMLMD_LICENSE_FILE=8224@127.0.0.1 && \ /data/arm64/RTSM_AEMv8/bin/model_shell64 /data/arm64/RTSM_AEMv8/models/Linux64_GCC-4.1/RTSM_VE_AEMv8A.so \ -a /data/arm64/boot-wrapper-aarch64/linux-system.axf \ -C motherboard.hostbridge.interfaceName=tap0 \ -C motherboard.smsc_91c111.enabled=true \ -C motherboard.smsc_91c111.mac_address=00:02:f7:ef:67:e6 \ -C motherboard.mmc.p_mmc_file=/data/arm64/oe/vexpress64-openembedded_minimal-armv8_20130423-299.img
Thank Jon! I've seen the same issues as Sumit has. I'm on the same version of rtsm model (v8) so we should be the same there. Still will narrow things down. On Tue, May 28, 2013 at 10:36 AM, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: > On Tue, 2013-05-28 at 16:47 +0530, Sumit Semwal wrote: >> Hi Tixy, >> >> On 28 May 2013 16:24, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: >> > On Mon, 2013-05-27 at 19:37 +0530, Sumit Semwal wrote: >> >> vexpress64.conf is missing some key CONFIGs about Regulators, >> >> which cause the kernel to complain about mmc voltages, and panic. >> >> >> >> These additional configs seem to help. >> > >> > Which kernel tree, config (android/ubuntu/ubuntu-minimal?), root >> > filesystem (Android/OE?), RTSM and device-tree are you using? >> I am using linux-linaro branch of linux-linaro-tracking tree: >> ubuntu-minimal for OE rootfs, RTSM and rtsm_ve-aemv8a.dts. Without >> these configs, I get mmc errors; I stumbled upon an old bug report >> where you had suggested. > > With a kernel built from the current linux-linaro I'm able to boot the > 13.04 OE minimal image fine, and I've been booting Juice OK on the AEMv8 > models regularly using the same vexpress64.conf. > > In order to try and understand what's going on can you mail me a full > log of your kernel boot? And also tell me the command-line you are using > to run the models and also what bootwrapper you are using and the > options used to build that? Finally, how old is your model? I have > version 0.8 from about 6 months ago, do you have a newer version? > > It would be interesting to see how our setups differ. I've been using > this bootwrapper: > https://git.linaro.org/gitweb?p=arm/models/boot-wrapper-aarch64.git;a=commit;h=26b62f586020fd998c6efd43db657eaafeec14da > > And I use make rules below to build a kernel and run an oe image, > > build_kernel64_oe: > bash -c "pushd ${KERNELDIR} && ARCH=arm64 scripts/kconfig/merge_config.sh linaro/configs/linaro-base.conf linaro/configs/ubuntu-minimal.conf linaro/configs/vexpress64.conf && popd" > export PATH=${PATH}:/data/arm64/aarch64-toolchain/gcc-linaro-aarch64-linux-gnu-4.7+bzr115029-20121015+bzr2506_linux/bin && \ > make -C ${KERNELDIR} ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j 5 Image modules > > run_rtsm64_oe_ve: > # ssh -L 8224:localhost:8224 -L 18224:localhost:18224 -N flexlm.linaro.org > cd /data/arm64/boot-wrapper-aarch64 && \ > git zap . && \ > git checkout origin/ubuntu && \ > ln -sf ${KERNELDIR}/scripts/dtc/dtc && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/Image && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/skeleton.dtsi && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-v2m-rs1.dtsi && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-foundation-v8.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-v2p-aarch64.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/foundation-v8.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/rtsm_ve-aemv8a.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/rtsm_ve-motherboard.dtsi && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/new.dts && \ > export PATH=${PATH}:/data/arm64/aarch64-toolchain/gcc-linaro-aarch64-linux-gnu-4.7+bzr115029-20121015+bzr2506_linux/bin && \ > make CROSS_COMPILE=aarch64-linux-gnu- FDT_SRC=vexpress-v2p-aarch64.dts BOOTARGS='"root=/dev/mmcblk0p2 consolelog=9 rw console=ttyAMA0 debug earlyprintk"' > > export ARMLMD_LICENSE_FILE=8224@127.0.0.1 && \ > /data/arm64/RTSM_AEMv8/bin/model_shell64 /data/arm64/RTSM_AEMv8/models/Linux64_GCC-4.1/RTSM_VE_AEMv8A.so \ > -a /data/arm64/boot-wrapper-aarch64/linux-system.axf \ > -C motherboard.hostbridge.interfaceName=tap0 \ > -C motherboard.smsc_91c111.enabled=true \ > -C motherboard.smsc_91c111.mac_address=00:02:f7:ef:67:e6 \ > -C motherboard.mmc.p_mmc_file=/data/arm64/oe/vexpress64-openembedded_minimal-armv8_20130423-299.img > > -- > Tixy > > > _______________________________________________ > linaro-kernel mailing list > linaro-kernel@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Tue, 2013-05-28 at 10:46 -0500, Tom Gall wrote: > Thank Jon! > > I've seen the same issues as Sumit has. > > I'm on the same version of rtsm model (v8) so we should be the same > there. Still will narrow things down. Not sure I trust version numbers, the release notes in mine says "0.8 RTSM Release Notes", are we on version 8 of RTSM, or is the ARM Architecture 8 models on there own version system as they are new and the release notes correct in saying version 0.8? So to be sure, shall we compare hashes of the .so file? $md5sum RTSM_AEMv8/models/Linux64_GCC-4.1/RTSM_VE_AEMv8A.so 400e35eb93f0e96dd2da016d2931cbc8
On Tue, May 28, 2013 at 10:59 AM, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: <snip> > So to be sure, shall we compare hashes of the .so file? > > $md5sum RTSM_AEMv8/models/Linux64_GCC-4.1/RTSM_VE_AEMv8A.so > 400e35eb93f0e96dd2da016d2931cbc8 400e35eb93f0e96dd2da016d2931cbc8 RTSM_VE_AEMv8A.so Looks like a match. > -- > Tixy > -- Regards, Tom "Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
Hi Tixy, On 28 May 2013 21:06, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: > On Tue, 2013-05-28 at 16:47 +0530, Sumit Semwal wrote: >> Hi Tixy, >> >> On 28 May 2013 16:24, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: >> > On Mon, 2013-05-27 at 19:37 +0530, Sumit Semwal wrote: >> >> vexpress64.conf is missing some key CONFIGs about Regulators, >> >> which cause the kernel to complain about mmc voltages, and panic. >> >> >> >> These additional configs seem to help. >> > >> > Which kernel tree, config (android/ubuntu/ubuntu-minimal?), root >> > filesystem (Android/OE?), RTSM and device-tree are you using? >> I am using linux-linaro branch of linux-linaro-tracking tree: >> ubuntu-minimal for OE rootfs, RTSM and rtsm_ve-aemv8a.dts. Without >> these configs, I get mmc errors; I stumbled upon an old bug report >> where you had suggested. > > With a kernel built from the current linux-linaro I'm able to boot the > 13.04 OE minimal image fine, and I've been booting Juice OK on the AEMv8 > models regularly using the same vexpress64.conf. > > In order to try and understand what's going on can you mail me a full > log of your kernel boot? And also tell me the command-line you are using > to run the models and also what bootwrapper you are using and the > options used to build that? Finally, how old is your model? I have > version 0.8 from about 6 months ago, do you have a newer version? > > It would be interesting to see how our setups differ. I've been using > this bootwrapper: > https://git.linaro.org/gitweb?p=arm/models/boot-wrapper-aarch64.git;a=commit;h=26b62f586020fd998c6efd43db657eaafeec14da same git, different commit: commit 73ecb28f15a4c92562573efa1a701043b4a826ac: Allow CROSS_COMPILE override on the make command line > > And I use make rules below to build a kernel and run an oe image, > > build_kernel64_oe: > bash -c "pushd ${KERNELDIR} && ARCH=arm64 scripts/kconfig/merge_config.sh linaro/configs/linaro-base.conf linaro/configs/ubuntu-minimal.conf linaro/configs/vexpress64.conf && popd" > export PATH=${PATH}:/data/arm64/aarch64-toolchain/gcc-linaro-aarch64-linux-gnu-4.7+bzr115029-20121015+bzr2506_linux/bin && \ > make -C ${KERNELDIR} ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j 5 Image modules > Essentially the same, except that I don't build modules, just the Image - are there any specific modules that could cause this? > run_rtsm64_oe_ve: > # ssh -L 8224:localhost:8224 -L 18224:localhost:18224 -N flexlm.linaro.org > cd /data/arm64/boot-wrapper-aarch64 && \ > git zap . && \ > git checkout origin/ubuntu && \ > ln -sf ${KERNELDIR}/scripts/dtc/dtc && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/Image && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/skeleton.dtsi && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-v2m-rs1.dtsi && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-foundation-v8.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/vexpress-v2p-aarch64.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/foundation-v8.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/rtsm_ve-aemv8a.dts && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/rtsm_ve-motherboard.dtsi && \ > ln -sf ${KERNELDIR}/arch/arm64/boot/dts/new.dts && \ > export PATH=${PATH}:/data/arm64/aarch64-toolchain/gcc-linaro-aarch64-linux-gnu-4.7+bzr115029-20121015+bzr2506_linux/bin && \ > make CROSS_COMPILE=aarch64-linux-gnu- FDT_SRC=vexpress-v2p-aarch64.dts BOOTARGS='"root=/dev/mmcblk0p2 consolelog=9 rw console=ttyAMA0 debug earlyprintk"' All ln -sf are same, toolchain is gcc-linaro-aarch64-linux-gnu-4.7-2013.04-20130415_linux (aarch64-linux-gnu-gcc (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC 2013.04) 4.7.3 20130328 (prerelease)) Make command is this: (without the FDT_SRC=), so I assume that it could be rtsm_ve-aemv8a.dts rather than vexpress-v2p-aarch64.dts. (diff shows difference only in name and compatible clauses though, but I'm not sure how important it is.) make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/mmcblk0p2 consolelog=9 rw console=ttyAMA0" earlyprintk=pl011,0x1c090000' > > export ARMLMD_LICENSE_FILE=8224@127.0.0.1 && \ > /data/arm64/RTSM_AEMv8/bin/model_shell64 /data/arm64/RTSM_AEMv8/models/Linux64_GCC-4.1/RTSM_VE_AEMv8A.so \ > -a /data/arm64/boot-wrapper-aarch64/linux-system.axf \ > -C motherboard.hostbridge.interfaceName=tap0 \ > -C motherboard.smsc_91c111.enabled=true \ > -C motherboard.smsc_91c111.mac_address=00:02:f7:ef:67:e6 \ > -C motherboard.mmc.p_mmc_file=/data/arm64/oe/vexpress64-openembedded_minimal-armv8_20130423-299.img > $MODEL_PATH/bin/model_shell64 -a ~/code/vexpress/linux-3.x/boot-wrapper-aarch64/linux-system.axf \ -C motherboard.mmc.p_mmc_file=/home/sumit/code/openembedded/jenkins-setup/build/vexpress-gfx/sd.img \ $MODEL_PATH/models/Linux64_GCC-4.1/RTSM_VE_AEMv8A.so \ -C cluster.NUM_CORES=1 -C cluster.cpu0.unpredictable_WPMASKANDBAS=0 \ -C cluster.cpu0.unpredictable_non-contigous_BAS=0 \ -C cluster.cpu1.unpredictable_WPMASKANDBAS=0 \ -C cluster.cpu1.unpredictable_non-contigous_BAS=0 \ -C cluster.cpu2.unpredictable_WPMASKANDBAS=0 \ -C cluster.cpu2.unpredictable_non-contigous_BAS=0 \ -C cluster.cpu3.unpredictable_WPMASKANDBAS=0 \ -C cluster.cpu3.unpredictable_non-contigous_BAS=0 \ -C cluster.take_ccfail_undef=0 \ -C motherboard.hostbridge.userNetworking=true \ -C motherboard.hostbridge.userNetPorts="5556=6565" \ -C motherboard.smsc_91c111.enabled=1 Also, md5sum ~/RTSM_AEMv8_VE/models/Linux64_GCC-4.1/RTSM_VE_AEMv8A.so e335c0919c126acf8d4471c9a22ddf48 The model I am using is: from arm-download-482650.tgz, which contains RTSM_AEMv8_VE_0.8_4702.tgz $MODEL_PATH/bin/model_shell64 -v Fast Models Model Shell 8.0.16 (Dec 7 2012) Copyright 2000-2012 ARM Limited. All Rights Reserved. > -- > Tixy > -- Thanks and regards, Sumit Semwal Graphics Engineer - Graphics working group Linaro.org │ Open source software for ARM SoCs
On Wed, 2013-05-29 at 11:13 +0530, Sumit Semwal wrote: > On 28 May 2013 21:06, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: > > It would be interesting to see how our setups differ. I've been using > > this bootwrapper: > > https://git.linaro.org/gitweb?p=arm/models/boot-wrapper-aarch64.git;a=commit;h=26b62f586020fd998c6efd43db657eaafeec14da > same git, different commit: > commit 73ecb28f15a4c92562573efa1a701043b4a826ac: Allow CROSS_COMPILE > override on the make command line Seems you are using a different git: people/nbhat/boot-wrapper-aarch64.git (that's the problem with the bootwrapper there are so many versions). However, trying that one didn't make any difference for me. It seems we're using nearly identical setups but getting different results. Can you send me a kernel log of the boot-up so I can see what errors you get, and also the axf file you are booting and the .config file from building your kernel (when you get the MMC errors). Best do that in a private mail rather than sending big attachments to the lists. Thanks
On 29 May 2013 12:52, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: > On Wed, 2013-05-29 at 11:13 +0530, Sumit Semwal wrote: >> On 28 May 2013 21:06, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: >> > It would be interesting to see how our setups differ. I've been using >> > this bootwrapper: >> > https://git.linaro.org/gitweb?p=arm/models/boot-wrapper-aarch64.git;a=commit;h=26b62f586020fd998c6efd43db657eaafeec14da >> same git, different commit: >> commit 73ecb28f15a4c92562573efa1a701043b4a826ac: Allow CROSS_COMPILE >> override on the make command line > > Seems you are using a different git: > people/nbhat/boot-wrapper-aarch64.git > (that's the problem with the bootwrapper there are so many versions). > However, trying that one didn't make any difference for me. Well, I think it is different - but from here: git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/boot-wrapper-aarch64.git > > It seems we're using nearly identical setups but getting different > results. Can you send me a kernel log of the boot-up so I can see what > errors you get, and also the axf file you are booting and the .config > file from building your kernel (when you get the MMC errors). Best do > that in a private mail rather than sending big attachments to the lists. > Yes, sure I'll send off the files. > Thanks > > -- > Tixy > > -- Thanks and regards, Sumit Semwal Graphics Engineer - Graphics working group Linaro.org │ Open source software for ARM SoCs
On 29 May 2013 15:03, Sumit Semwal <sumit.semwal@linaro.org> wrote: > On 29 May 2013 12:52, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: >> On Wed, 2013-05-29 at 11:13 +0530, Sumit Semwal wrote: >>> On 28 May 2013 21:06, Jon Medhurst (Tixy) <tixy@linaro.org> wrote: >>> > It would be interesting to see how our setups differ. I've been using >>> > this bootwrapper: >>> > https://git.linaro.org/gitweb?p=arm/models/boot-wrapper-aarch64.git;a=commit;h=26b62f586020fd998c6efd43db657eaafeec14da >>> same git, different commit: >>> commit 73ecb28f15a4c92562573efa1a701043b4a826ac: Allow CROSS_COMPILE >>> override on the make command line >> >> Seems you are using a different git: >> people/nbhat/boot-wrapper-aarch64.git >> (that's the problem with the bootwrapper there are so many versions). >> However, trying that one didn't make any difference for me. > Well, I think it is different - but from here: > git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/boot-wrapper-aarch64.git > >> >> It seems we're using nearly identical setups but getting different >> results. Can you send me a kernel log of the boot-up so I can see what >> errors you get, and also the axf file you are booting and the .config >> file from building your kernel (when you get the MMC errors). Best do >> that in a private mail rather than sending big attachments to the lists. >> > Yes, sure I'll send off the files. Hi Tixy! Well - unfortunately, I can't reproduce this now! :O - I have tried in multiple ways to get this error, but can't! Sorry for the noise; if I stumble upon it again, I will let you know. Also, 1 request: could you please get the https://wiki.linaro.org/HowTo/BuildArm64Kernel wiki page updated to make sure it has the correct instructions? >> Thanks >> >> -- >> Tixy >> >> > > -- -- Thanks and regards, Sumit Semwal Graphics Engineer - Graphics working group Linaro.org │ Open source software for ARM SoCs
On Wed, 2013-05-29 at 15:50 +0530, Sumit Semwal wrote: > Also, 1 request: could you please get the > https://wiki.linaro.org/HowTo/BuildArm64Kernel wiki page updated to > make sure it has the correct instructions? It's a wiki, you could update it yourself ;-) I've not seen that page before, but my default assumption about any wiki page is that they're not owned by anyone, are unmaintained, out of date, and there are multiple copies floating around in different places.
diff --git a/linaro/configs/vexpress64.conf b/linaro/configs/vexpress64.conf index 9087e4e..32b638f 100644 --- a/linaro/configs/vexpress64.conf +++ b/linaro/configs/vexpress64.conf @@ -28,3 +28,8 @@ CONFIG_VIRTIO_BLK=y CONFIG_VIRTIO_MMIO=y CONFIG_REGULATOR=y CONFIG_REGULATOR_FIXED_VOLTAGE=y +CONFIG_SENSORS_VEXPRESS=y +CONFIG_REGULATOR_VEXPRESS=y +CONFIG_NEW_LEDS=y +CONFIG_LEDS_CLASS=y +CONFIG_LEDS_REGULATOR=y
vexpress64.conf is missing some key CONFIGs about Regulators, which cause the kernel to complain about mmc voltages, and panic. These additional configs seem to help. Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org> --- linaro/configs/vexpress64.conf | 5 +++++ 1 file changed, 5 insertions(+)