[okl4-developer] OKL4 2.1: Build Option 'VEBOSE_INIT=1 'doesnot work

[Frank Kaiser]

> -----Original Message-----
> From: Geoffrey Lee [mailto:glee at ok-labs.com]
> Sent: Monday, June 23, 2008 2:02 PM
> To: Frank Kaiser
> Cc: developer at okl4.org
> Subject: Re: [okl4-developer] OKL4 2.1: Build Option 'VEBOSE_INIT=1
'doesnot
> work
> 
> On Mon, Jun 23, 2008 at 10:48:50AM +0200, Frank Kaiser wrote:
> > Hello, Geoffrey
> >
> > Many thanks for your feedback. I am testing OKL4 version 2.1 which I
got
> > from
> >
http://wiki.ok-labs.com/FrontPage?action=AttachFile&do=get&target=okl4_2
> > .1.tar.gz. The ATMEL AT91SAM9263 is built around an ARM926EJ-S core.
> > Since the directory arch/arm/pistachio/cpu/arm926ejs proved to be
empty,
> > I cloned the xscale directory since it comes closest to the core
variant
> > I am using. So far I only had some work to adapt cache.h.
> > Meanwhile I found out that kmem_t::init() and kmem_t::free() (called
by
> > init) are the only methods using TRACE_INIT() before the
initialisation
> > of the console. After commenting them out 'VERBOSE_INIT=1' behaved
as
> > excpected.
> 
> Hi Frank
> 
> Writing to the console is done by the Platform::serial_putc()
> function.  In our platform code we make a check to ensure that
> the serial is always initialized before trying to write
> out to the serial.
> 
> Please take a look at the supported platforms, you should
> see the serial_putc() function being wrapped around an
> if block.
> 
> 	-gl
Hi, Geoffrey

Admitted: for instance the PXA platform shows such a scheme that
serial_putc() checks the validity of a global pointer to the serial
device which is assigned by serial_init(). However, due to the lack of
comments it is not obvious that this is intended to serve as a barrier
against pre-initialised console output.
Anyway, it makes sense to add such a check to my console driver.

Thanks + regards
Frank