* Ivaylo Dimitrov <ivo.g.dimitrov.75@xxxxxxxxx> [160203 08:51]: > - flashed maemo rootfs > > sudo flasher-3.5 -f -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin > --flash-only=rootfs -R > > - booted to maemo and powered the device off > > sudo flasher-3.5 -k zImage -l -b"init=/sbin/preinit ubi.mtd=rootfs > root=ubi0:rootfs rootfstype=ubifs rootflags=bulk_read,no_chk_data_crc rw > mtdoops.mtddev=log omapfb_vram=7M omapfb.mode=lcd:848x480-16 > nokia-modem.pm=0" This seems to fix things here for legacy booting and booting the maemo zImage after dts image. Care to give it a try? Basically onenand after reset is in wrong state, have not looked up the bits yet. Will post a better patch when I get a chance over next few days. Regards, Tony 8< ----------- --- a/arch/arm/mach-omap2/gpmc-onenand.c +++ b/arch/arm/mach-omap2/gpmc-onenand.c @@ -104,6 +104,7 @@ static void set_onenand_cfg(void __iomem *onenand_base) u32 reg; reg = readw(onenand_base + ONENAND_REG_SYS_CFG1); + reg = 0x06c0; reg &= ~((0x7 << ONENAND_SYS_CFG1_BRL_SHIFT) | (0x7 << 9)); reg |= (latency << ONENAND_SYS_CFG1_BRL_SHIFT) | ONENAND_SYS_CFG1_BL_16; @@ -289,6 +290,7 @@ static int omap2_onenand_setup_async(void __iomem *onenand_base) } } + onenand_async.sync_write = true; omap2_onenand_calc_async_timings(&t); ret = gpmc_cs_program_settings(gpmc_onenand_data->cs, &onenand_async); -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
