=== heathkid|2 is now known as heathkid === heathkid|2 is now known as heathkid === chrisccoulson_ is now known as chrisccoulson [09:33] Hi there [09:33] Is anyone around so I can ask a couple of questions about porting to armhf? [09:33] I'm trying to get started with porting ubuntu to a tablet === doko__ is now known as doko [09:52] hello? [10:11] ask away [10:11] blackthund3r: ^ [10:30] wookey: o.O hi [10:30] Okay [10:30] Basically I'm working on a tegra port of ubuntu [10:30] and was wondering how I really start collating everything [10:31] I have downloaded the linux4tegra kit and I've modified rootstock to produce an armhf package but I'm not really sure what the best way of testing all this is [10:31] also how I would add certain patches to the kernel for specific device support [10:44] rootstock makes images not packages. Are you building a package for armhf or trying to build whole images? [10:45] whole images [10:45] and eventually a kernel too [10:46] I'm attempting to get 12.04 booting on the Acer Iconia A500 [10:46] blackthund3r: you can use the ac100 image for starting [10:46] but you will need a working kernel [10:46] hmm ok. Is that a better option than starting from scratch? [10:46] depends on your caps [10:47] Sure. I believe there is a 2.6 chromeos kernel for this device but I'm trying to get as new a source tree compiled as possible [10:47] caps? [10:47] capabilities [10:47] ok sure [10:47] ac100 uses a 3.1 kernel (from nvidia) [10:47] I'm new to kernel dev and this sort of thing although I'm very experienced with linux [10:47] that makes sense. I've just checked that code out via git [10:48] I believe the stuff I need to add in is here: https://github.com/iconia-dev [10:48] how do I add that then tell make to use that config? [10:50] what kernel is this based on? [10:50] Not sure. I believe they're patches for stock linux [10:51] (in the github link) [10:51] I'm working with the 3.1 kernel for nvidia [10:51] *from [10:51] it is preconfigured (I believe) for the ventana test board. I need to add those patches so it will work on the tablet [10:52] (and then work on adding in drivers once I see what is actually supported OOTB) [10:52] sounds like a plan [10:53] so how do I add those patches in? [10:53] there is a vendor section with proprietary folder, [10:54] I haven't seen any patches in the repo at all [10:54] and a device tree [10:54] https://github.com/iconia-dev/android_device_acer_a500 and https://github.com/iconia-dev/android_vendor_acer_a500 [10:56] also (probably a separate question) where is the section in the kernel source for the initramfs? [10:56] these are scripts for some build system, no kernel patches [10:56] The plan is to install linux into /data/linux from within Android and install the kernel to the spare partition. Then chroot to it [10:56] the kernel seems to be available in binary form [10:57] sure does. Should I try booting it to see what will happen? [10:57] I think you can use the android kernel and see how far you come [10:57] I need to bridge it to an initramfs or it won't be useful, unless I can open a serial connection with it to view the output? [10:57] hmm [10:57] I hadn't considered that [10:58] okay so assuming I used that kernel as it is fairly up to date (one dev has a 3.2.x-based kernel) [10:58] how can I chroot to /data/linux? [10:58] is that even possible? Has anybody every tried installing linux to a folder? [10:59] I assume it would go fairly early in the init script [10:59] if /data was mounted by the initramfs, could you then chroot to /data/linux? [10:59] Or would it need to be remounted as /? [11:00] there is no /data on ubuntu [11:00] I could call it anything when mounted though right? [11:00] okay /mnt/data [11:00] ah, you can try to mount an ubuntu fs in android [11:00] and chroot to it [11:01] no I've done that already ;) [11:01] I mean use the kernel to do it and boot up from a chroot [11:01] the data partition is mmcblk0p9 [11:01] the data partition is mmcblk0p8 [11:02] so if mmcblk0p8 was mounted by the ramdisk [11:02] then the linux folder was set as the root [11:02] would this work? [11:03] that would mean Ubuntu could be booted natively whilst keeping that partition [11:03] the data partition is pretty huge [11:03] so it makes sense to install linux there [11:03] and somehow boot it [11:05] you may create your own initrd (from the chroot) [11:05] and pass it to the kernel [11:05] hmm [11:05] also the root partition (via root=...) kernel command line [11:05] can you mount a partition beforehand? [11:05] Wait no that wouldn't work [11:06] okay so if root=magicinitrd [11:06] no, the ubuntu initrd will try to mount root [11:06] then somewhere in that initrd it needs to mount /dev/block/mmcblk0p8 [11:06] the initrd is mounted automaticly by the kernel (if it is there) [11:06] then fuse-mount /mnt/mmcblk0p8 as / [11:06] sure [11:07] so how does linux's initrd then mount the rest of the filesystem? [11:07] /etc/fstab ? [11:07] because it is almost a union of the initrd and the partition [11:07] makes sense [11:08] okay android seems a little different [11:08] yes, userspace is totally different [11:08] the android initrd will use /fstab.t20 to mount all the partition in the own folders [11:08] although (I assume) ubuntu will mount the RootFS as /? [11:09] it should [11:09] but I'm also not an expert [11:09] ok sure. [11:09] So in that case I need to understand roughly how that works [11:10] in order to mount a partition then set a folder rather than a partition as / [11:11] I still don't understand why you want to do this [11:11] in order to boot ubuntu up with it installed in a folder [11:12] currently there is /data/media, /data/Android etc etc [11:12] in android, the partitions are also mounted on folders [11:12] so I want a /data/linux [11:12] which the linux kernel will use as a rootfs [11:12] yes but android doesn't need to mount a new rootfs - the initrd is the complete rootfs as the main system works out of the /system folder [11:12] if fact, the mount point doesn't matter [11:13] why do you want to keep this strange android way of booting? [11:13] so is what I want to do possible? [11:13] why not just mount the root partition and you are finished [11:13] to not have to wipe out all the userdata in order to install ubuntu [11:13] you can also boot from a sdcard [11:14] I guess the a500 has a slot for it [11:14] so install straight to the data partition alongside the rest of the android data? [11:14] yes you can but it's only cool if it works from the internal memory ;) [11:14] more storage that way too - there are some 64GB tabs [11:16] once I have a reliable way of doing this, I want to extend it to making an easy way of patching an existing android ROM to boot from, say, /data/sys2 or /data/sys3 so you can dual boot ROM [11:16] *ROMs [11:16] but that's a later project. For now I want a working ubuntu install [11:17] for tablets like this it'd be really useful to have a full RootFS in a folder [11:17] particularly as the filesystem is ext4 anyway [11:17] it saves repartitioning stuff [11:30] blackthund3r: you can split the "user" partition [11:30] don't know anymore where it was mounted [11:30] split how? [11:30] repartition it? [11:30] yes [11:30] that would cause ROM issues [11:30] it worked fine on the ac100 [11:30] hmm [11:30] this is the anatomy of the a500 [11:30] http://projects.pappkartong.se/a500/ [11:31] actually it might work [11:31] but then you have to dedicate that space [11:31] (which is what I was trying to avoid :P) [11:32] and the whole tablet would still have to be wiped out to do that as I understand [11:32] nvflash isn't the most user-friendly of tools! [11:33] eventually I want this to be available to the public [11:34] brb :) [12:12] thanks for your help marvin24! [12:12] gtg :( [12:16] * lilstevie thinks he is going about that in the most difficult way he can find [12:17] picasso and tf101 are very similar, with a small patch it would boot with the same kernel [12:18] nah, cant be that would break the well estabished arm fragemntation vendors worked on for years ! [12:18] :) [12:19] ogra_, muromec ported 2.6.38 to both the tf101 and picasso, if you compile it with both boards defined in the config it comes down to a few if(is_machine_picasso()) blocks difference [12:20] I have no idea why though :p arm fragmentation is common, and expected [12:23] yeah, evil, the vendors should sue him to break it :) [12:23] s/to break/for breaking/ [12:24] :p [12:25] lol " hey guys there is a rumor about windows 8 coming out for tablets and im so excited for that " <-- got to love forums, that was posted today [12:26] yeah, finally more locked down HW on the market [12:28] yeah [12:28] uefi comes to arm, but not to benefit the platform :( === Quintasan_ is now known as Quintasan === Ursinha` is now known as Ursinha