You might want to try diff-ing the relevant parts of the customized Android 2.1 against the official version of 2.1 and then applying something similar to those changes to the official 2.2
Of course this kind of approach doesn't work if there's been a change in an underlying mechanism between the versions. When that happens, your really have to understand how it works in detail. On Nov 30, 1:02 am, l l <[email protected]> wrote: > Hi, > I'm porting Android2.2 to S5PC100. > The kernel can't find partitons of nand flash. > I have the source code of Android2.1 that can run on S5PC100. > The kernel of Android2.1 called function of add_mtd_blktrans_dev() > related to nand flash, > but Android2.2 didn't. > Source code of Android 2.2 were downloaded from Google. Android 2.1 was > not. > > Nand flash chip is Samsung K9F2G08, 256M Bytes. > > ERROR information: > > VFS: Cannot open root device "mtdblock3" or unknown-block(2,0) > Please append a correct "root=" boot option; here are the available > partitions: > Kernel panic - not syncing: VFS: DIWEI2 Unable to mount root fs on > unknown-block(2,0) > [<c002ea88>] (unwind_backtrace+0x0/0xd0) from [<c02f8074>] > (panic+0x3c/0x10c) > [<c02f8074>] (panic+0x3c/0x10c) from [<c0009024>] > (mount_block_root+0x1d4/0x21c) > [<c0009024>] (mount_block_root+0x1d4/0x21c) from [<c00092c0>] > (prepare_namespace+0x164/0x1b8) > [<c00092c0>] (prepare_namespace+0x164/0x1b8) from [<c00085b4>] > (kernel_init+0xd8/0x10c) > [<c00085b4>] (kernel_init+0xd8/0x10c) from [<c0029f1c>] > (kernel_thread_exit+0x0/0x8) > > Thanks. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
