I'm a little lost.

I don't have an old G5 with a PCI-E slot to dump the propreties of the card.

I'm not sure if the PCI Header is not being loaded that the FCode can match to the device(pci10de,0141).

I don't know if that's related to this issue or not.


When I do:

0 > 0 0 " 4,0" " /pci@f2000000" begin-package  ok
0 > dev /pci ls
fff8042c mac-io@c
fff83008 usb@d
fff83374 QEMU,VGA@e
fff87994 NE2000@f
fff87d44 pci10de,141@10
fffad3dc <noname>
 ok
0 >

It creates a <noname> device, but it has no address, so I can't get the .properties or words from it. I'm sure I'm not getting this command right, I don't think OpenBios has a "Slot" property for PCI Cards?

That maybe an issue?



On Sunday, December 17, 2017, 12:06:51 PM EST, Segher Boessenkool <segher@kernel.crashing.org> wrote:


Hi!

On Sun, Dec 17, 2017 at 10:22:29AM +0000, Mark Cave-Ayland wrote:
> On 15/12/17 23:26, Jd Lyons wrote:
> >I’m having trouble CC ing the list, I know stupid of me.
> >
> >Any idea what the unnamed FCode in the detok is?
> >
> >Does detok just not understand it, or is it words or methods?
>
> From memory I believe it's an anonymous Forth word, i.e. one where the
> dictionary name is empty but it can still be called by its address.

That's right.  It's a token created with new-token instead of named-token
or external-token (b5, b6, ca respectively).  It has no name, so you cannot
call it by name, but it is perfectly valid FCode, you can access the created
word by token number like everything else.


Segher


--
OpenBIOS                http://openbios.org/
Mailinglist:  http://lists.openbios.org/mailman/listinfo
Free your System - May the Forth be with you