[00:13] <TaoSk8r> Greets all.. Im trying to setup the ARM repo if possible on my chrubuntu installation, is this possible? Im using the 12.04 kubuntu
[02:01] <TaoSk8r_> wow i guess this is a lurk mode channel
[02:01] <TaoSk8r_> nobody talks here, oh well
[02:02] <TaoSk8r_> have a good one, nobody who is listening.
[09:41] <hvn2> hi, I have a question about the boot process...does the u-boot.bin play an active role in the boot or not ?
[09:45] <infinity> hvn2: It's effectively your firmware and bootloader all rolled into one, so yes.
[09:49] <hvn2> infinity: so only having a new uImage, uInitrd and boot.scr doesn't boot the system
[09:49] <infinity> hvn2: That depends on the system.  But one like a Panda, for instance, has no PROM with u-boot written to it, so the only one it has is the one you give it on the SD card.
[09:50] <infinity> Some other boards do have a burned-in u-boot, and don't need you to provide a spare.
[09:52] <hvn2> infinity: I'm trying to boot a custom patched kernel. dpkg does create the file I mentioned, but not the u-boot.bin. After reboot, the process hangs on the boot of the new kernel. Hence the question.
[09:52] <hvn2> typo: ..files I mentioned..
[09:52] <infinity> hvn2: Well, the u-boot you already had should work.  You don't need a new one for each kernel.
[09:53] <infinity> If you deleted your old u-boot, that wouldn't work so well. :P
[09:54] <hvn2> infinity: should it work if the u-boot.bin is for a different kernel than uImage, uInitrd  and the /boot contents ?
[09:54] <infinity> hvn2: u-boot isn't "for a kernel".
[09:54] <infinity> hvn2: Like I said, it's effectively your firmware and bootloader.
[09:55] <infinity> hvn2: You don't replace your BIOS and GRUB on every kernel update on x86.  Same general idea.
[09:55] <hvn2> infinity: ok. I understand. Then I have to look further into why it won't boot.
[10:00] <hvn2> infinity: you compare it to GRUB....after installing a new kernel on x86, the new kernel is usually added to GRUB. Does that go for u-boot as well ?
[10:02] <infinity> hvn2: Grub updates its config file, that's all.  Usually not needed with a u-boot setup if it just follows the symlinks.  But look at your boot.scr to see what it's doing.
[10:03]  * infinity needs to get some sleep.
[10:03] <hvn2> infinity: ok, ty
[10:08] <suihkulokki> I guess A53 is quite rare breed.. in-order 64bit cpu :)
[10:10] <suihkulokki> hmm echan
[11:00] <hvn2> Question: I'm about to cross-compile a custom kernel, but not sure which method to use. https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile at 6 says to build uImage only, while other sources say to create a deb package containing uImage, uInitrd and vmlinuz. Which is best ?
[11:01] <hvn2> Running Ubuntu Precise
[12:49] <hvn2> Hi, question: trying to build a custom kernel for beagleboard following https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile FAQ 6, I end up with a hanging system with last message "Uncompressing Linux... done, booting the kernel. ". The boot info shows it boots the correct uImage. But why could it hang?
[12:50] <ogra> did you set the right console= option ?
[13:03] <hvn2> ogra: I'm using a 3.5.7 vanilla kernel, so low-level debug uart is no option. I tried console= earlier but without any result.
[13:15] <hrw> why so old?
[13:21] <hvn2> hrw: because of a patch I intend to use which is adapter for 3.5.7 and 3.8.13. So I could use the later one as well, but my main question is why it doesn't boot. It boots with 3.2.0, so why not 3.5.7 ?
[14:13] <hvn2> ok, I have tried https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile FAQ 6 with 2 different kernels: 3.5.7 and 2.6.33 (because of UART) and the board won't boot. So I'm rather clueless by now.
[14:16] <ogra> how do you know it desnt boot if you dont even get the kernel messages
[14:16] <ogra> fix that first
[14:17] <ogra> "Uncompressing Linux... done, booting the kernel." is only the kernel starting ... if it oopses or doesnt find iits initrd or doesnt find its rootfs it prints stuff after that to the default console
[14:17] <ogra> (whatever console is defined in your config)
[14:50] <hvn2> ogra: yes, I'm going to compare working stuff with custom....see what that gives
[14:50] <hvn2> already did, but will get it working....
[18:14] <davidkrauser> Hello everybody
[18:14] <davidkrauser> Does anyone in here have any experience building for armv5 with the gcc-arm-linux-gnueabi package in Ubuntu 12.04? I can get it to work with the package in 13.10, but not with the package in 12.04.
[18:15] <davidkrauser> Seems that all of the files in /usr/arm-linux-gnueabi/ are targeting armv7-a in 12.04, and armv5t in 13.10
[18:18] <davidkrauser> Also seems that in 12.04, everything is built with -mfloat-abi=softfp, and everything in 13.10 is built with -mfloat-abi=soft
[18:25] <davidkrauser> I used `readelf -A FILE` to inspect those files. Not sure if there's a better way.
[18:37] <davidkrauser> brb