On Friday 20 March 2009, Narnakaje, Snehaprabha wrote: > Dave, > > Does it bring up the need to support legacy layout > in the git, for existing devices? > > What is your opinion on supporting the legacy layout > on git, for existing dm355 devices?
I think the deciding factor is that GIT has never really supported the DM355 NAND in a usable mode, so in a sense it doesn't matter. If I can get a clean switchover, I'll be happy ... and for me, switchover doesn't need to preserve any data on the flash whatsoever. Recall that chips shipped with the EVM have used two non-mainline data formats on those NAND chips: the page layout (infix OOB), and YAFFS. Even if there were a legacy option for the former, the latter would still need dealing with. I'd like to see a 2009-x version of U-Boot, with eventual kernel-from-MMC support, and NAND hosting a big UBIFS volume holding a Debian ARMEL release. IMO that would be a good base "community" config. > Basically some of davinci-nand 4-bit APIs need to be > rewritten to support the legacy layout. Then the > question is how are we going to let the user choose > between legacy vs. standard layouts - kconfig? I'm > not sure, if we can check this at run-time. That would imply a new u-boot that knows how to use both formats. I wouldn't encourage that. - Dave > > Thanks > Sneha _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
