[coyotos-dev] New binutils, gcc, crtfiles, newlib

[Sam Mason]

On Sat, Apr 12, 2008 at 01:16:03AM +0100, Sam Mason wrote:
> When I've tried to boot Coyotos recently, I've wondered why the
> HelloWorld test doesn't actually print out "hello world".  I've just
> (not sure why I didn't think of this earlier) looked through the code
> and found a console_detach() procedure that is run before the "first
> user mode instruction".  For some reason I'd always been looking for
> something explicit in the user-mode code so far.

Hum, it's all documented as doing that.  It's got quite a steep learning
curve this doesn't it!

> I've noticed the KernLog
> interface, but don't see how to get anything back out again.
[...]
> I'm tempted to try and hack something together that gets the current
> contents of the kernel message buffer and dumps it off to the
> TextConsole.

Hum, this is a completely inappropriate way of solving the problem isn't
it!  I've started writing a "KernelConsoleLogger" driver that implements
the KernLog interface and dumps output to both a TextConsole and some
other KernLog capability it's given.

I'm struggling to get it all working though.  For some reason I think
it would be nice to have my KernelConsoleLogger receive capabilities to
the actual KernLog and TextConsole to use.  I can't figure out how to
do this though.  Other bits of code set things up in the "tools" and go
from there, but I can't see a way of passing a predefined set of tools
in, so I'm assuming that tools are private to a process.  The only thing
I seem to get control over is the "runtime", is this the right place to
give capabilities to a child?  If so, should I be creating a copy of the
runtime?


  Sam