As I commented in http://marc.info/?l=linux-omap&m=121792042504348&w=2 I can't quite see why anything is using "omap_mmc_config" for anything related to hsmmc ... it contains two structs that don't match what the hsmmc driver understands. - Dave > > @@ -83,9 +84,17 @@ static struct omap_uart_config > > omap2_evm_uart_config __initdata = { > > .enabled_uarts = ((1 << 0) | (1 << 1) | (1 << 2)), > > }; > > > > +static struct omap_mmc_config omap2_evm_mmc_config __initdata = { > > + .mmc [0] = { > > + .enabled = 1, > > + .wire4 = 1, > > + }, > > +}; > > + > > static struct omap_board_config_kernel omap2_evm_config[] __initdata = { > > { OMAP_TAG_UART, &omap2_evm_uart_config }, > > { OMAP_TAG_LCD, &omap2_evm_lcd_config }, > > + { OMAP_TAG_MMC, &omap2_evm_mmc_config }, > > }; > > > > static int __init omap2_evm_i2c_init(void) -- 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
