Paul,

    Don't quote me on this but I think that d, e, and f are all on the same bus.
Ditto for a, b, and c. This is backed up by Apple technote 1062, which gives
some Forth commands to decode the slot-names property of the bridge chip.

    You, too, can delve into the fun of OF. Just search the net for the OF
spec:  1275.ps. Then you can do fun things like:

    " scsi-int" select-dev show-children unselect-dev
    " scsi" select-dev show-children unselect-dev

                    kevin

P.S.:    I'll fire up my 9600 and get the output-device string I am using and
send it later tonight. Would have done it sooner but a transformer near my house
exploded and, due to a 14 hour power outage, I was forced to watch Monday Night
football on a 15 year old B&W LCD TV. How bout them rams?

paul beard wrote:

> On Monday 17 December 2001 09:59 am, you wrote:
> > The 'words' command will make sure there is an OF rom. It should print out
> > the list of commands that the rom provides.
>
> OK, that seems to settle that. DEFAULT CATCH would not be what I'm after.
> 0 > " pci1/ATY,mach64@F" select-dev words .properties unselect-dev DEFAULT
> CATCH!, code=FFF00300
>
> 0 > " pci1/@f" select-dev words .properties unselect-dev DEFAULT CATCH!,
> code=FFF00300
>  ok
>
> I moved the card to a different slot the other day: that's why it's on pci1 @
> F, rather than pci2 @ D.
>
> So howcum MacOS can use it? It doesn't care about OF since it's not a
> console? And I am pretty sure I used this in LinuxPPC. I know it worked as a
> console in OS X as well.
>
> But anyway,  I have a serial console and I have booting worked out. The
> scanner is the real deal right now.
>
> Thanks again for all your help.
> --
> Paul Beard
> 8040 27th Ave NE
> Seattle WA 98115
>
> Troubles are like babies; they only grow by nursing.