[uClinux-dev] Odd boot message

Georges Menie g.menie at wanadoo.fr
Thu Mar 20 16:30:10 EST 2003

On Thu, 2003-03-20 at 16:33, Stuart MacDonald wrote:
> From: "Bernard Leach" <leachbj at bouncycastle.org>
> > > Jivin Stuart MacDonald lays it down ...
> > > > In arch/m68knommu/kernel/setup.c:setup_arch() is the line:
> > > >
> > > > printk("\x0F\r\n\nuClinux/" CPU "\n");
> [snip quoted]
> > The 0xf is an ASCII shift-in which should ensure the terminal is in
> > ASCII mode.  The extra \r\n's are normally used to ensure the following
> > text starts on the start of the terminal line.
> In that case, I'll just #ifdef it for my platform.
> Note: I couldn't locate where in the kernel's printk chain the
> escaped (backslashed) characters are processed. Anyone have a pointer?
> printk is in linux/kernel/printk.c and it calls vsnprintf from
> linux/lib/vsprintf.c. vsnprintf takes care of regular % style formats,
> but appears to leave \ style formats alone, leading me to suspect that
> the compiler handles them.

I think most of the platform don't need this ASCII shift-in, and if some
needs it, it could be set from the crt0... it's not even the very first
char displayed when booting.

I like Stuart's first proposal:

printk("uClinux/" CPU "\n");


More information about the uClinux-dev mailing list