On Sunday 02 November 2008, Rick Bronson wrote: > > Is that what you saw too? > > Yep, that's what I saw, but only if I had DEBUG_LL=y. Without that > I had nothing except "Uncompressing Linux........". I don't have DEBUG_LL=y ... if you had some kind of network link configured over USB, could you SSH in? (I can.) > I guess we don't see this problem on the other 2 ports since they > are mapped MT_MEMORY_SO and not MT_DEVICE (L4_34XX_PHYS). Hmm, inconsistency is to be avoided. :) I wonder what the root cause is ... is the driver missing various barriers needed to make MT_DEVICE work? Or is the MT_DEVICE incorrect in the first place? "git whatchanged" didn't show any recent changes that seemed (on a quick glance) to affect I/O at that level. Maybe it was one of the other TTY changes interacting here. - Dave -- 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
