[BusyBox] Serial console on kernel 2.6.9

[Brian T]

I use a customer embedded unit, and a few months back I was working on 
getting 2.6 working also.  I didn't have problems with S0 as the console, 
but my bootloader is 9600.  That probably doesn't matter though.  Here are 
the options I used.  Not sure if it will be any help, but worth a try.

#
# Character devices
#
# CONFIG_VT is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=12
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_MULTIPORT=y
# CONFIG_SERIAL_8250_RSA is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_UNIX98_PTYS is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

-Brian


>
> I am running Linux Kernel 2.6.9 and Busybox on a WRAP 2C board -
> Ethernet, Serial, and no VGA.
>
> I have configured bootloader (tried grub and lilo) to use serial
> console at WRAP's default baud rate (38400), and passed
> console=ttyS0,38400 on the kernel command line.
>
>
> Everything works on the serial port fine up until the Kernel's serial
> driver loads (just after the line Serial: 8250/16550 driver
> $Revision: 1.90 $ 8 ports, IRQ sharing enabled) and then it starts
> spitting out junk. It is like the baud rate, serial paramaters get
> changed).
>
>
> Then once busybox's init loads, serial sorts itself out and displays
> properly again.
>
>
> I have tried changing lots of Kernel Parameters (enabling virtual
> terminals, shared IRQs, serial drivers etc) with no change. It isn't
> too big a problem, just a bit annoying, and don't understand why.
>
>