lkml.org 
[lkml]   [2008]   [Apr]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] OLPC: Add support for calling into Open Firmware


Yinghai Lu wrote:
> On Sun, Apr 20, 2008 at 8:09 PM, Mitch Bradley <wmb@firmworks.com> wrote:
>
>>
>> Yinghai Lu wrote:
>>
>>
>>> how about changing to ofw_32.c?
>>>
>>> YH
>>>
>>>
>>>
>> Is your suggestion to change the filename from "ofw.c" to "ofw_32.c"? That
>> seems like a good idea to me.
>>
>
> Yes.
>
> BTW, why olpc need OFW runtime service?
> why not just put the info in in ram with some signiture, so
> kernel/util just need to loot at the table if needed?
>

In SPARC land, at least on SunOS and Solaris, it was very convenient for
debugging to interrupt the OS with Stop-A and use OFW to inspect the
system state. That was especially handy for live crash analysis. Dumps
are useful as far as they go, but they often fail to capture detailed
I/O device state.

I was hoping to do that on x86 too. So far we (OLPC) haven't
implemented a sysrq hook to enter OFW, but I haven't given up hope yet.
It doesn't cost much to leave OFW around, but once you decide to eject
it, you can't easily get it back.

Apple made the early decision to eject OFW and just keep a device tree
table. That decision was probably due to several factors, including the
rather lame state of Apple's first OFW implementation and the complexity
of their OS startup process at the time (which included "trampolining"
to a 68000 emulator to run their legacy code). Once they went down that
path, the die was cast, and the PowerPC community got used to the "OFW
ends up as just a table" idea.

>


\
 
 \ /
  Last update: 2008-04-21 06:09    [W:0.101 / U:0.564 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site