<snip> > > You are quite possibly correct, but the level translator I'm using is > "invisible" - it doesn't require the transceiver control signals > offered only on MMC2. So as far as I know, there is no hardware reason > the OMAP MMC3 controller couldn't talk correctly at the electrical > level with the card. This is evidenced by the CMD signal being > correctly level translated (and this is via the same type of level > translator as the data signals are according to the TXS02612 > datasheet), and toggling correctly(-looking) at the card socket (i.e. > between 0 and 3.3V and it's edges synced to the clock signal). The > DAT0-DAT3 signals never do anything though. The MMC3 DAT0-DAT3 lines are muxed with MMC2 DAT4-DAT7. Any chance the padconfs are being overwritten even though you programmed them correctly in the bootloader? - Anand -- 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
