Linux 2.6-10.rc3 8xx - Only 3 characters are printed well i n __ init start_kernel() upon kernel booting - why ?

[Povolotsky, Alexander]

Hi Hans,

Unfortunately I am not using u-boot.
I am using "custom" bootloader (modified pSOS bootloader),
 for which I do not have the source (and on top of - even if I would
have the source for this bootloader - JTAG is not available to me to 
reflash new version of the bootloader).

Is there any way to control (change) this in the kernel source itself ?

Thanks,
Best Regards,
Alex

-----Original Message-----
From: Hans Schillstrom [mailto:hans.schillstrom at pwav.com]
Sent: Monday, January 17, 2005 2:10 AM
To: Povolotsky, Alexander
Subject: Re: Linux 2.6-10.rc3 8xx - Only 3 characters are printed well
in __ init start_kernel() upon kernel booting - why ?

Hi,
If you are using u-boot,
have you checked the env. varialbe "clocks_in_mhz" ?
if that one is set it turn out like that.

Regards
/Hans

On Sun, 2005-01-16 at 20:54, Povolotsky, Alexander wrote:
> > Per kind advise I have got, I have added baud rate to the command line
(I
> > did not have it there before):
> > 
> > CONFIG_CMDLINE="console=ttyCPM0,115200 panic=3 root=/dev/ram"
> > 
> > 	However, my real current problem (just 3 characters get printed
> > correctly during the kernel boot) did not go away.
> > 
> > 	Is there a way to check if the baud rate specified in the .config's
> > commandline is indeed in effect for the kernel booting ?
> > 
> > 	Any other reasons/explanation for my "3 character" problem ?
> > 
> > 	 -----Original Message-----
> > 	From: 	Povolotsky, Alexander  
> > 	Sent:	Sunday, January 16, 2005 5:59 AM
> > 	To:	'linuxppc-dev at ozlabs.org'
> > 	Subject:	Linux 2.6-10.rc3  8xx kernel booting - how to set
> > baud rate for the serial driver ?
> > 
> > 	Hi,
> > 	... 
> > 	     
> > 	My bootloader uses 115200 baud rate for the serial output during
> > boot strapping.
> > 
> > 	I have:
> > 	CONFIG_SERIAL_CPM_CONSOLE
> > 	in my .config 
> > 	... 
> > I could see some output during the kernel boot -
> > I noticed that (only 3) characters (see below) from the linux_banner are
> > printed
> > in __init start_kernel() upon booting . Then a lot of garbage is
outputted
> > and eventually kernel hangs ...
> > 
> > after gunzip
> > done.
> > Now booting the kernel
> >
LinÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÀ8ÀÿÿÿÿÿÿÿÿÀXÀÿÿÿÿÿÿÿÿÀxÀÿÿÿÿÿÿÿÿÀ~ÀÿÿÿÿÿÿÿÿÀ¸Àÿÿÿÿÿÿÿ
> > ÿÀØÀÿÿ
> > <more garbage>
> > <hangs>
> > 
> > to prove it I added printk("ALEX\n"); in __init start_kernel() prior to
> > printk(linux_banner);
> > 
> > ... 
> > lock_kernel();
> > page_address_init();
> > printk("ALEX\n");
> > printk(linux_banner);
> > setup_arch(&command_line);
> > setup_per_cpu_areas();
> > ...
> > 
> > after gunzip
> > done.
> > Now booting the kernel
> >
ALEÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÀ8ÀÿÿÿÿÿÿÿÿÀXÀÿÿÿÿÿÿÿÿÀxÀÿÿÿÿÿÿÿÿÀ~ÀÿÿÿÿÿÿÿÿÀ¸Àÿÿÿÿÿÿÿ
> > ÿÀØÀÿÿ
> > <more garbage>
> > <hangs>
> > 
> > Why would first 3 characters come out right ?
> > Any ideas ?
> > Thanks,
> > 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>