Re: [microblaze-uclinux] Initial console problems

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

I wrote:
> Hi Greg and others,
> 
> Greg Miller wrote:
> 
>> Same issue here. The console is broke. How to fix it??!!
> 
> 
> OK at least I've been able to reproduce the problem at my end.  It seems 
> the issue is limited to xmbserial.c, so, for a quick fix, while I work 
> out what's really going on
> 
> $ cd linux-2.4.x/arch/microblaze/kernel
> $ cvs update -C -D "2005-4-14" xmbserial.c
> 
> then rebuild your kernel as normal.
> 
> I'll continue looking at the stuff that changed in xmbserial.c (support 
> for "console=null" boot param) to see what broke.  If I cannot do this 
> in a reasonable timeframe (e.g. next hour or so) I'll revert CVS to how 
> it was before the change.

OK I'm pretty confident this is fixed.  It turns out I was trying to do 
"too much", the "console=null" handling logic is already built into the 
mainline kernel consle handler.  I essentially re-=implemented this and 
managed to break it completely - sorry for that.

CVS head should be hunky-dory, please test it out and let me know.  I 
tried it using uClinux-auto on both the V2MB1000 and ML401 standard 
designs from my website, seems fine now.

Cheers,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/