[SLOF] Loading file from disk image

[Jd Lyons]

> On Jan 2, 2018, at 8:43 AM, Jd Lyons <lyons_dj at yahoo.com> wrote:
> 
> Joy!peffpwpc……
> 
> 14677: [ a5] 0 0 0 2 1 5e77ef40 5e7d1078 4 0 
>   14679: [111] encode-int 0 0 2 1 5e77ef40 5e7d1078 4 5e7d107c 4 
>   1467b: [112] encode+ 0 0 2 1 5e77ef40 5e7d1078 8 
>   1467c: [ 12] b(") 0 0 2 1 5e77ef40 5e7d1078 8 1467e e 
>   1468d: [110] property 0 0 2 1 5e77ef40 
>   1468f: [127] finish-device 0 0 2 1 5e77ef40 
>   14691: [127] finish-device 0 0 2 1 5e77ef40 
>   14693: [de0] xde0 0 0 2 1 5e77ef40 
>   14694: [  0] end0 0 0 2 1 5e77ef40 
> restored fcode@ 5e77ef40 
> restored fcode-spread 1 
> restored fcode-offset 2 
> restored fcode-end 0 
> restored ip 0 
> ok
> 0 > dev /pci ls  
> 5e72ad60 :  /pci at 800000020000000
> 5e72d2e8 :  |-- ethernet at 0
> 5e72d9d8 :  +-- NVDA,Parent at 1
> 5e7cfab0 :      |-- 
> 

Seems to be having trouble populating the children,

I should see:

> 5e72d9d8 :  +-- NVDA,Parent at 1
> 5e7cfab0 :      |-- NVDA,Display-A

> 
>> On Jan 2, 2018, at 8:20 AM, Thomas Huth <thuth at redhat.com> wrote:
>> 
>> On 02.01.2018 14:09, Jd Lyons wrote:
>>> 
>>> 
>>>> On Jan 2, 2018, at 7:50 AM, Thomas Huth <thuth at redhat.com
>>>> <mailto:thuth at redhat.com>> wrote:
>>>> 
>>>> On 02.01.2018 13:23, Jd Lyons wrote:
>>>>> 
>>>>> 
>>>>>> On Jan 2, 2018, at 4:35 AM, Thomas Huth <thuth at redhat.com
>>>>>> <mailto:thuth at redhat.com>> wrote:
>>>>>> 
>>>>>> On 29.12.2017 10:09, Jd Lyons wrote:
>>>>>> [...]
>>>>>>> Now if there was only a byte-load word:-(
>>>>>> 
>>>>>> The FCode interpreter is currently disabled in SLOF by default - since
>>>>>> nobody was actively using it in years and pulling in all the required
>>>>>> Forth code slowed down the boot process quite a bit.
>>>>>> 
>>>>>> But you can enable it manually by typing this at the firmware prompt:
>>>>>> 
>>>>>> include evaluator.fs
>>>>>> 
>>>>>> After that, the "byte-load" word should be available.
>>>>>> I hope that's good enough for your experiments ... if there's a real
>>>>>> good reason for enabling it permanently again, please let us know, then
>>>>>> we should maybe come up with a better solution for this...
>>>>>> 
>>>>>> Thomas
>>>>> 
>>>>> Thanks Tom, is there a way to enable fcode-verbose?
>>>> 
>>>> What is fcode-verbose? That's not a standard Open Firmware Forth word,
>>>> is it?
>>>> 
>>>> There's a "eva-debug?" flag in the Fcode evaluator of SLOF, so that
>>>> might be related. You can enable it with:
>>>> 
>>>> true to eva-debug?
>>> 
>>> Thanks, this seems to do the same thing as ?fcode-verbose.
>>> 
>>> Let’s me see where the option rom’s forced is aborting, oddly enough it
>>> seem to be the around the same place I’m catching and exception in
>>> openbios, so if I can get it working in one, I maybe able to get it to
>>> work for the other.
>>> 
>>> 3e0935: [ 14] b?branch 3e0944 0 2 1 5e77e878 
>>>  3e0939: [9bd] x9bd 3e0944 0 2 1 5e77e878 2000014 
>>>  3e093a: [ 10] b(lit) 3e0944 0 2 1 5e77e878 2000014 ff 
>>>  3e093f: [ 23] AND 3e0944 0 2 1 5e77e878 14 
>>>  3e0941: [103] my-space 3e0944 0 2 1 5e77e878 14 800 
>>>  3e0942: [ 1e] + 3e0944 0 2 1 5e77e878 814 
>>>  3e0944: [a08] xa08  Aborted
>>> 0 > dev /pci   ok
>>> 0 > ls  
>>> 5e72ad60 :  /pci at 800000020000000
>>> 5e72d2e8 :  |-- ethernet
>>> 5e72d9d8 :  +-- vga ok
>>> 0 > dev vga   ok
>> 
>> Note that if you want to run the FCODE manually, you should make sure
>> that you've got an open instance of the corresponding device tree node
>> first. In SLOF, you can do this by typing:
>> 
>> s" /pci/vga" select-dev
>> 
>> Thomas
>