Ignore the last patch I posted.
I'm not sure this is the right fix for this problem but it seems to
work ;-) Here is what's happening
In drivers/serial/8250.c size_fifo() miscalculates the fifo size of
the 3rd UART. The first 2 UART's calculations are okay. The 3rd's
miscalculation causes the console port to be messed up. When I tried
putting debug code in, the problem would sometimes go away (or come
back) depending on what debug code I put in. So I thought maybe it
was the memory mapping type that was chosen for the UART io memory
range. That's what led to this patch. Try it out and tell me if it
works for you.
I have to wonder if L4_WK_34XX_VIRT needs to be classified as
MT_MEMORY_SO also?
Rick
--- linux-omap-2.6/arch/arm/mach-omap2/io.c.~1~ 2008-10-28 10:10:25.000000000 -0700
+++ linux-omap-2.6/arch/arm/mach-omap2/io.c 2008-11-01 14:58:35.000000000 -0700
@@ -155,7 +155,7 @@ static struct map_desc omap34xx_io_desc[
.virtual = L4_PER_34XX_VIRT,
.pfn = __phys_to_pfn(L4_PER_34XX_PHYS),
.length = L4_PER_34XX_SIZE,
- .type = MT_DEVICE
+ .type = MT_MEMORY_SO /* debug only */
},
{
.virtual = L4_EMU_34XX_VIRT,
--
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
