[okl4-developer] OKLinux on x86

[Henning Schild]

On Wed, 12 Nov 2008 21:11:44 +1100
Geoffrey Lee <glee at ok-labs.com> wrote:

> What is the exact command line you used to build OK Linux and OKL4?  
> Have you made any modifications, both source code and any supporting
> infrastructure?

My command line:

> PATH="/opt/nicta/gcc-3.3.4-glibc-2.3.3/i686-unknown-linux-gnu/bin/:$PATH"
> ./tools/build.py machine=ia32_pc99 project=iguana
> toolchain=gnu_ia32_toolchain wombat=true

I did not change anything except the mentioned patch i found on this
list.
http://lists.okl4.org/pipermail/developer/2008-October/001834.html

> On the 2.1 release, the hardware serial device is shared between the
> kernel debugger and a userlevel driver used by OK Linux.  This may be
> causing some issues.  Can you try building a production build by 
> appending enable_debug=False to the build command line, and see if you
> get any output?  The initial dmesg output and the OKL4 banner will
> go missing because the kernel serial driver will be compiled out.

With that it again works in Qemu and crashed on a real machine. This
time far less output and again i only see the "L" of "Linux user
startup! ....."

> Otherwise, some trace output context might be quite useful in
> resolving this issue.

I will look deeper into that. But i'd like a working copy as soon as
possible. Could you send me your image.elf that used to work and
describe the machine you were using?

Henning