Thread: How To Compile Your Own Kernels, Modules, Tinboot (NAND boot), and More for Beginners
View Single Post
  #97 (permalink)  
Old 03-10-2011, 01:18 AM
manekineko's Avatar
manekineko
Regular 'Geeker
Offline
 
Join Date: Jul 2009
Posts: 478
Reputation: 845
manekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: How To Compile Your Own Kernels, Modules, Tinboot (NAND boot), and More for Begin
Quote:
Originally Posted by tiad8 View Post
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.
Reply With Quote