How To Compile Your Own Kernels, Modules, Tinboot (NAND boot), and More for Beginners

[ndno]

I'm finally setup up Ubuntu under Vmware; for the Froyo system.ext2, rootfs, and initrd, how do you grab the sources? Will it be something like this?

git clone git://gitorious.org/xdandroid-froyo/froyo-rootfs.git
git clone git://gitorious.org/xdandroid-froyo/initramfs.git

[natemcnutty]

Originally Posted by ndno

I'm finally setup up Ubuntu under Vmware; for the Froyo system.ext2, rootfs, and initrd, how do you grab the sources? Will it be something like this?

For building the system, it is much more complicated and something that I have not set up in my environment. You compile a lot with Java and such.

For rootfs and initrd, it's pretty much what you said, but the gits are the wrong addresses. Haret is the only one using rootfs now as we changed it for NAND. Here are the two gits you want to clone:

git clone git://gitorious.org/xdandroid-eclair/eclair-rootfs.git
git clone git://gitorious.org/xdandroid-eclair/initramfs.git

Note: They are restructuring the XDAndroid stuff to get rid of legacy names like eclair and all that.

[ndno]

Originally Posted by natemcnutty

For building the system, it is much more complicated and something that I have not set up in my environment. You compile a lot with Java and such.

For rootfs and initrd, it's pretty much what you said, but the gits are the wrong addresses. Haret is the only one using rootfs now as we changed it for NAND. Here are the two gits you want to clone:

git clone git://gitorious.org/xdandroid-eclair/eclair-rootfs.git
git clone git://gitorious.org/xdandroid-eclair/initramfs.git

Note: They are restructuring the XDAndroid stuff to get rid of legacy names like eclair and all that.

Thanks. I see they have the instructions to build the Froyo system.ext2 posted on the XDAndroid site. I'll follow your instructions to build the rootfs and initrd. Planning to play around and build the full package (include kernel/modules) to run with haret.exe. For my work, I have worked with OMAP A8 processor and have some experience playing around with the x-loader and u-boot on the NAND. Trying to learn a little about how the Android system is set up. For my work, I have the Mistral OMAP3530 board so I'm going to eventually try to get Froyo to run on it using this kit from TI: http://processors.wiki.ti.com/index....2_ReleaseNotes

[natemcnutty]

Guys, I wanted to let you all know that this post is now out-dated for NAND, and I'm just waiting for things to finalize a little more before I update it. We officially have no rootfs anymore, and everything is done through init.rc or combined into the system/data store. I'll explain this a little better when I do update the first post.

I also have a huge update to do on the first post of the NAND testing thread as well. This will get first priority, and then I'll head over here and get this one updated as well.

[arrrghhh]

Originally Posted by natemcnutty

Guys, I wanted to let you all know that this post is now out-dated for NAND, and I'm just waiting for things to finalize a little more before I update it. We officially have no rootfs anymore, and everything is done through init.rc or combined into the system/data store. I'll explain this a little better when I do update the first post.

I also have a huge update to do on the first post of the NAND testing thread as well. This will get first priority, and then I'll head over here and get this one updated as well.

Looking forward to it, thanks for keeping these threads up-to-date!

[tiad8]

hi, nate

I know you are very busy. i apologise for that.

I have an important question.

data.img

1- when android is creating the data.img, you think is possible to let initrd.gz know, to add the data.img to an ext2 partition with 300mb. i want to keep the data.img in a ext2 partition by it self.

1- fat32 for all android stuff
2- ext2 for data.img only

thanks

[manekineko]

Originally Posted by tiad8

hi, nate

I know you are very busy. i apologise for that.

I have an important question.

data.img

1- when android is creating the data.img, you think is possible to let initrd.gz know, to add the data.img to an ext2 partition with 300mb. i want to keep the data.img in a ext2 partition by it self.

1- fat32 for all android stuff
2- ext2 for data.img only

thanks

Can actually already be done, I just did this yesterday. The init script is setup so that if you have 3 partitions, first is fat32 for SD card stuff and Haret, second is ext2 for system, and third is ext2 for data, it will automatically use it.

Order is set by the init file. In the current stock init file in the rootfs, there is an error, and the system partition is set as 3, and the data partition is set as 4, with nothing set to 2. You can create the partitions numbered that way using fdisk in Linux, or you can fix the init script.

My initial experimentation shows that this gets USB/SD card semi-working.

[tiad8]

Originally Posted by manekineko

Can actually already be done, I just did this yesterday. The init script is setup so that if you have 3 partitions, first is fat32 for SD card stuff and Haret, second is ext2 for system, and third is ext2 for data, it will automatically use it.

Order is set by the init file. In the current stock init file in the rootfs, there is an error, and the system partition is set as 3, and the data partition is set as 4, with nothing set to 2. You can create the partitions numbered that way using fdisk in Linux, or you can fix the init script.

My initial experimentation shows that this gets USB/SD card semi-working.

thank you

[tiad8]

Originally Posted by manekineko

Can actually already be done, I just did this yesterday. The init script is setup so that if you have 3 partitions, first is fat32 for SD card stuff and Haret, second is ext2 for system, and third is ext2 for data, it will automatically use it.

Order is set by the init file. In the current stock init file in the rootfs, there is an error, and the system partition is set as 3, and the data partition is set as 4, with nothing set to 2. You can create the partitions numbered that way using fdisk in Linux, or you can fix the init script.

My initial experimentation shows that this gets USB/SD card semi-working.

Test 1
I was able to add more mb to my data.img (500), when creating new data.img.

Test 2
I created a fat32(android stuff) and ext2 partition (data.img). But when creating the new data.img. the data.img is in the sd card not in the ext2.

I will play more with this tomorrow. But everything is working according plan.

Thanks


FROYO X RED, BLAZN 2.2.2, GINGERBREAD 2,3,2, SENSE FROYO 2.2/SPRINT TOUCH PRO 2/RHOD400

[natemcnutty]

Originally Posted by tiad8

Test 1
I was able to add more mb to my data.img (500), when creating new data.img.

Test 2
I created a fat32(android stuff) and ext2 partition (data.img). But when creating the new data.img. the data.img is in the sd card not in the ext2.

I will play more with this tomorrow. But everything is working according plan.

Thanks


FROYO X RED, BLAZN 2.2.2, GINGERBREAD 2,3,2, SENSE FROYO 2.2/SPRINT TOUCH PRO 2/RHOD400

I think you are getting the terms mixed up. You can partition the SD card to have ext2 partitions which the init script is set up to recognize. If it finds the right partition layout, it will natively write to the sd card rather than creating a data.img.

If you don't partition the sd card and just leave it formatted as FAT32, the data.img by default is in ext2 as you can see from the code: init - eclair-rootfs in XDANDROID Eclair - Gitorious

If you want it to actually say data.ext2, you can just change the extension and update the if statement to check for data.ext2 instead of data.img, but it won't affect performance or change the way it works.

Thanks for bringing this thread back up too. I almost forgot to get it updated! Maybe I'll have some free time tomorrow when I get home from work