* Dave Hylands <dhylands@xxxxxxxxx> [111004 23:41]: > Hi, > > I have an older overo board, which has an OMAP3503 > > U-booot reports: > OMAP3503-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz > > In order to get the 2.6.39 kernel to boot, I had to make 2 modifications: > > In arch/arm/mach-omap2/pm34xx.c, in the omap_sram_idle routine I had > to put an #if 0 around: > > #if 0 > if (omap3_has_io_wakeup() && > (per_next_state < PWRDM_POWER_ON || > core_next_state < PWRDM_POWER_ON)) { > omap2_prm_set_mod_reg_bits(OMAP3430_EN_IO_MASK, > WKUP_MOD, PM_WKEN); > omap3_enable_io_chain(); > } > #endif > > or I would get continuous > > Wake up daisy chain activation failed. > > messages on the console. No idea why this fails.. > I then also had to modify drivers/mmc/card/block.c and initializing > disable_multi to 1 in the mmc_blk_issue_rw_rq function to get rid of > the following messages for every I/O request. > > mmcblk0: retrying using single block read > mmcblk0: retrying using single block read > mmcblk0: retrying using single block read > mmcblk0: retrying using single block read > > (since this revision of the silicon doesn't support multi-block MMC reads). ..but this one is usually a problem muxing the MMC data lines. Are you sure this revision only supports one data line? Tony -- 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