[01:51] <ojn> s/Where/Who/
[03:50] <XaSe> Anyone know if it is possible to replace bootloader on an android handset or to load ubuntu from the preexisting bootloader, or chain it to an acceptable boot mechanism such as grub or lilo?
[03:56] <lilstevie> XaSe, in most cases providing that bootloaders do not signature check the kernel it will be possible to boot ubuntu without needing to change the bootloader
[03:57] <XaSe> S-off or security off on an htc, so kernel signing is no issue.
[03:57] <lilstevie> ok
[03:58] <lilstevie> well you just need an appropriate kernel and initrd\
[03:58] <lilstevie> it isnt that difficult
[04:01] <XaSe> ok. cool so i could write boot.img to /boot... would the initrd be stored there as well?
[04:04] <XaSe> im curious as how to handle the file system since the nand seems to have pre-defined positions?
[04:04] <XaSe> or am i off base?
[04:05] <XaSe> positions>partitions
[04:06] <lilstevie> nand uses MTD
[04:07] <lilstevie> so you may want to boot your rootfs from sd
[04:07] <lilstevie> and the kernel is not all that is at boot
[04:08] <lilstevie> the bootloader HBOOT is a fastboot bootloader
[04:08] <XaSe> An android kernel source with some extra flags set should suffice for buildingb kernel or  should i use say: linaro sources or something else.
[04:09] <lilstevie> this means it needs to be in android bootimg format
[04:09] <XaSe> So i would require fastboot bits then?
[04:09] <lilstevie> which is packed zImage + initrd
[04:09] <lilstevie> as well as a header to define the commandline and a few other details like size
[04:09] <XaSe> So recompiling cyanogenmod into a zImage should be fine?
[04:10] <lilstevie> use the android kernel source with changes to the kernel config, there is no generic arm kernel tree that works on all devices like x86 does
[04:11] <XaSe> So step one is modifying cyanogenmod sources to have necessary bits to work with ubuntu?
[04:13] <lilstevie> Edit the kernel config to allow udev to work (set CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y).
[04:13] <lilstevie> dont do the whole cm tree
[04:13] <lilstevie> that is silly
[04:13] <lilstevie> just the kernel
[04:13] <lilstevie> which device is this for
[05:36] <XaSe> Well of  course the kernel, lilstevie its the htc evo4g
[05:36] <lilstevie> k
[05:37] <XaSe> man this computer is going to make it hard.
[05:40] <XaSe> so you think dding the arm image to the sd card and then removing the boot information there and instead having it reside in /boot on the nand would be the best bet@ lilstevie ?
[05:41] <lilstevie> there is no reason to remove the boot information, it just wont get used
[05:42] <XaSe> ok
[05:43] <XaSe> let me see if i even know how to use git well enough to pull just the kernel
[05:46] <XaSe> I just realized this is the first time ive missed using an iteration of ubuntu on or before release in many ages
[05:48] <XaSe> i'll just dl it  instead. im too dumb for git and so  is  this computer.
[05:52] <XaSe> the latest source i can find so far was last modified two years ago and is 2.6.32 is that  still acceptable for precise pangolin? lilstevie
[06:40] <heathkid> if we can't talk about the Raspberry Pi here... then where?
[06:41] <heathkid> I know at least a few of you have one now...  :)
[13:26] <XaSe> i should copy a config to the kernel directory or the root source directory and rename it config right lilstevie ?
[14:23] <XaSe> lilstevie: Create a kernel maintained /dev tmpfs ? to set those flags you mention?
[14:34] <XaSe> http://pastebin.com/xu92Vc0M anyone know what's wrong because I dont
[14:35] <XaSe> i have a .config file with correct config
[14:35] <XaSe> or do i have to name the file something else?
[14:37] <XaSe> i think im missing target...
[14:38] <XaSe>  and not  sure how to get it to build zimage either.
[15:28] <janrinze> XaSe: the config file is .config ; did you configure the kernel with defconfig?
[15:29] <XaSe> it was my toolchain
[15:29] <janrinze> what was your toolchain??
[15:29] <XaSe> emdebian
[15:29] <janrinze> you mean it was caused by your toolchain?
[15:29] <XaSe> switched to code sourcery, no issues.
[15:29] <janrinze> aha.
[15:30] <janrinze> did you manage to build a zImage?
[15:30] <XaSe> Question EXTRA_AFLAGS=-mfpu=neon < would this flag break anything?
[15:30] <janrinze> yep, Tegra2 has no NEON
[15:30] <XaSe> kernel is building now.
[15:30] <XaSe> im building for msm i believe
[15:31] <janrinze> msm?
[15:31] <XaSe> mach-msm
[15:31] <XaSe> it's a snap dragon chipset
[15:31] <janrinze> oh, S4?
[15:32] <XaSe> I was getting these type of errors without neon flag
[15:32] <XaSe> /home/all/SourceCode/android/HTC/vision-2.6.32-g814e0a1/arch/arm/mach-msm/idle-v7.S:126: Error: selected processor does not support ARM mode `fmxr fpexc,r2'
[15:32] <janrinze> ah, i missed the 'htc' in the dir name :-)
[15:33] <janrinze> XaSe: looks like your toolchain is not with hard-float
[15:33] <janrinze> probably -mhard-float would be better?
[15:34] <janrinze> Do you intend to use armhf?
[15:34] <XaSe> if i run into errors maybe ? i dont know.
[15:34] <XaSe> its an armv7 chip.
[15:34] <XaSe> i am not sure what all of it means to be honest
[15:34] <janrinze> the float-abi can be either NEON or vfp3D16
[15:35] <XaSe> which would you say would be best in your opinion?
[15:35] <janrinze> it is about which co-processor is used for float instructions
[15:36] <XaSe> im aiming to use this as a tablet if that helps
[15:36] <janrinze> XaSe: usually -mhard-float should be sufficient. I have not seen specific usage of NEON in the kernel yet.. but that may be just me ;-)
[15:36] <janrinze> XaSe: you are compiling an Android kernel?
[15:37] <XaSe> no
[15:37] <XaSe> linux to use ubuntu
[15:37] <XaSe> boot from sd
[15:37] <XaSe> im using the android source
[15:38] <janrinze> Ubuntu will not be compiled with NEON, if you use armhf then it will use vfp3D16
[15:39] <XaSe> so i should change this flag
[15:39] <janrinze> did you make your own Ubuntu image or got it from a download?
[15:40] <XaSe> Have not made it  was hoping a prebuilt fs would be sufficient
[15:40] <janrinze> most prebuilt fs are armel, if you are lucky it will be armhf
[15:41] <janrinze> with armel there is no hard-float compiled in with the binaries
[15:41] <XaSe> so extra_flags=-mhard-float instead?
[15:41] <janrinze> or you could get the hard-float version of the compiler instead
[15:42] <XaSe> it just built my kernel...
[15:42] <janrinze> fine :-)
[15:42] <janrinze> probably will be ok, since the assembler instructions are quite specific :-)
[15:43] <XaSe> so now should i just rebuild with -mhard-float instead?
[15:43] <janrinze> you could, i don't think it will really matter
[15:44] <XaSe> But didnt  you just say id need to build ubuntu image a certain way?
[15:44] <janrinze> I have Ubuntu 12.04 armhf and for what it is worth, most things run a bit better
[15:44] <janrinze> XaSe: your kernel will be able to run both
[15:44] <janrinze> having a armel fs would be ok too
[15:45] <XaSe> So now that i've built my kernel wwhats my next step to be able to be up and running fastest
[15:45] <XaSe> ?
[15:45] <janrinze> probably get a armhf Ubuntu image ;-)
[15:45] <janrinze> since 12.04 it is possible to choose armel or armhf
[15:46] <janrinze> armhf will be faster when programs use a lot of floating-point instructions
[15:46] <janrinze> a armel fs cannot be upgraded to armhf due to incompatibilities..
[15:47] <janrinze> I am running Ubuntu 12.04 armhf on a ASUS TF101. works good.
[15:47] <XaSe> So im unsure of what needs to be done next beyond flashing zimage through hboot.
[15:47] <XaSe> lucky
[15:48] <janrinze> just follow the instructions for your platform, must be on a web page somewhere since you already got this far ;-)
[15:49] <XaSe> Ive kind of been winging it with previous knowledge and some info from lilstevie.
[15:49] <janrinze> aha, then perhaps lilstevie can be of more help than me.
[16:01] <XaSe> janrinze: with that neon set do i still need to specify mhard-float to use armhf?
[16:02] <XaSe> or am i good to go with the flag i set
[16:07] <XaSe> I know someone named M. Poirier lol.
[16:09] <janrinze> XaSe: your kernel will probably be fine for either armel or armhf
[16:10] <XaSe> ok well then i will download the armhf core
[16:23] <XaSe> How do I make the bootloader/kernel know that my root is on my sdcard.
[16:38] <XaSe> im only sure about one thing and that's fastboot flash zimage zImage
[17:14] <xase> janrinze: where do i put initrd do you perhaps know?
[17:15] <xase> =/
[17:15] <xase> janrinze: where do i put initrd do you perhaps know?
[17:15] <xase> err woops
[17:15] <xase> i would assume fastboot push initrd /boot ?
[17:15] <xase> i mean i would assume /boot
[17:26] <xase> stupid question, how to make an initrd
[19:48] <xase_> I dont think my kernel is even  doing anything.
[19:49] <xase_> not booting, nothing
[19:50] <mythos> hmm... it's sunday... so most are drunk or worse... be patient, xase_ ;)
[19:50] <mythos> xase_, what is your problem? maybe i can help you
[19:51] <xase_> i have made kernel and initrd for htc evo 4g/supersonic and attempting to use fastboot to boot it but i dont go past splash screen.
[19:52] <mythos> what device do you use?
[19:53] <mythos> htc evo 4g/supersonic <-- is that the name?
[19:54] <xase_> yes
[19:55] <mythos> hmm... i don't have any experience to boot a phone. can you deactivate the splash? does the device use uboot?
[19:56] <xase_> no
[19:56] <xase_> fastboot/hboot
[19:56] <mythos> ok... i have to say, that i can't help you then. sorry ;)
[21:14] <xase_> im giving up on the evo going back to hacking my nook.
[21:52] <trelane> would anyone like to recommend a wireless adapter which is stable on the beaglebone with the -psp kernel series that rcn-ee appears to be responsible for?
[22:28] <mythos> trelane, maybe more luck in #pandaboard
[22:28] <mythos> äh...#beagle