Re: What happened to the serial console on BeagleBoard with 2.6.28-rc2?

[Tony Lindgren <tony@atomide.com>]

* Rick Bronson <rick@efn.org> [081104 13:08]:
> Hi Tony,
> 
>   I tried your patch to drivers/serial/8250.c and it works fine.  I
> was concerned that I would start seeing:
> 
> omapfb: omapfb blah blah interrupt 0x4000
> 
>   (sorry, can't remember the exact verbage) because I saw them at one
> point during the many reboots I did while working on the serial port
> problem.  But I didn't see any after about 20 reboots.
> 
>   I assume you mean the patch below but why do you want this one if
> your 8250.c patch works?

Well the patch below, and my i2c-omap and 8250 patches should not be
needed any longer, see commit 6ae3983b779ea5ad87515630e9b9205b76f1e916.

Tony


>   Rick
> 
> 
> Signed-off-by: Rick Bronson <rick@efn.org>
> 
> --- 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,
> 
> 
> > Rick, can you please reply with your Signed-off-by for your patch?
> > 
> > Let's push that one, then continue thinking about the so/device
> > issues.
> > 
> > Tony
> >