Differences Between FCode 2.x and 3.x

D

This appendix discusses the FCodes and macros that have changed between FCode 2.x and FCode 3.x. The 3.x tokenizer will still tokenize code correctly using FCode 2.x names (excepting old #>, # and #s). The function of each of the equivalent FCodes is unchanged.The existing tokenized FCode programs using 2.x FCodes will not be affected on 3.x OpenBoot PROMs. The only functional exception is in the FCode 2.x names #>, #, and #s. FCode 3.x has the same names associated with functionally different FCodes and different byte values. If you have tokenized FCode using the 2.x tokenizer with these FCodes (for instance, #), you will get the same response (since the operation of old # is equivalent to new u# and tokenized code has 99 as byte value for your old #).

Table D-1

FCode 2.x	FCode 3.x (equivalent)	Byte Value
not	invert	26
<<	lshift	27
>>	rshift	28
ca1+	char+	62
na1+	cell+	65
/c*	chars	66
/n*	cells	69
flip	wbflip	80
version	FCode-revision	37

Table D-1 (Continued)

FCode 2.x	FCode 3.x (equivalent)	Byte Value
b(is)	b(to)	C3
eval	evaluate	CD
u*x	um*	D4
xu/mod	um/mod	D5
x+	d+	D8
x-	d-	D9
attribute	property	01 10
xdrint	encode-int	01 11
xdr+	encode+	01 12
xdrphys	encode-phys	01 13
xdrstring	encode-string	01 14
xdrbytes	encode-bytes	01 15
decode-2int	parse-2int	01 1B
map-sbus	map-low	01 30 (stack diag. enhanced)
get-my-attribute	get-my-property	02 1A
xdrtoint	decode-int	02 1B
xdrtostring	decode-string	02 1C
get-inherited-attribute	get-inherited-property	02 1D
delete-attribute	delete-property	02 1E
get-package-attribute	get-package-property	02 1F
wflips	wbflips	02 36
lflips	lwflips	02 37
is	to

---

Note - The following 2.x FCodes have changed names. The new 3.x FCodes with the same names function differently.

---

Table D-2

FCode 2.x	FCode 3.x (equivalent)	Byte Value
#>	u#>	97
#	u#	99
#s	u#s	9A

So if you are using the 3.x tokenizer to elicit the old response from #>, #, and #s, the source code must be changed so that the commands are replaced by u#>, u# and u#s respectively. For code previously tokenized using the 2.x tokenizer, the result is the same on both OpenBoot 2.x and 3.xPROMs .

Table D-3

FCode 2.x	Byte Value
4-byte-id	FE
dma-alloc	01 01
memmap	01 04
>physical	01 06
my-params	01 0F
intr	01 17
driver	01 18
group-code	01 23
processor-type	02 10
firmware-version	02 11
fcode-version	02 12
probe	02 38
probe-virtual	02 39

To access the functionality provided by dma-alloc, do:

: my-dma-alloc ( size -- addr ) " dma-alloc" $call-parent ;

and use my-dma-alloc.

To access the functionality provided by memmap, use map-low appropriately.

To replace intr, create " interrupts" and " intr" properties using property.

To access the functionality provided by firmware-version or fcode-version, use firmware-revision.

Table D-4

FCode 3.x	ByteValue
unloop	89
get-token	DA
set-token	DB
state	DC
compile,	DD
behavior	DE
decode-phys	01 28
push-package	01 29
pop-package	01 2A
interpose	01 2B
lwflip	02 26
lbflip	02 27
lbflips	02 28
next-property	02 3D
byte-load	02 3E
set-args	02 3F

Table D-5

FCode 3.x	Byte Value
#	C7
#s	C8
#>	C9

Table D-6

3.x FCodes	Stack Diagrams	Byte Value
rx@	( oaddr -- o )	02 2E
rx!	( o oaddr -- )	02 2F
bxjoin	( b.lo b.2 b.3 b.4 b.5 b.6 b.7 b.hi -- o )	02 41
<l@	( qaddr -- n )	02 42
lxjoin	( quad.lo quad.hi -- o )	02 43
wxjoin	( w.lo w.2 w.3 w.hi -- o )	02 44
x,	( o -- )	02 45
x@	( oaddr -- o )	02 46
x!	( o oaddr -- )	02 47
/x	( -- n )	02 48
/x*	( nu1 -- nu2 )	02 49
xa+	( addr1 index -- addr2 )	02 4A
xa1+	( addr1 -- addr2 )	02 4B
xbflip	( oct1 -- oct2 )	02 4C
xbflips	( oaddr len -- )	02 4D
xbsplit	( o -- b.lo b.2 b.3 b.4 b.5 b.6 b.7 b.hi )	02 4E
xlflip	( oct1 -- oct2 )	02 4F
xlflips	( oaddr len -- )	02 50
xlsplit	( o -- quad.lo quad.hi )	02 51
xwflip	( oct1 -- oct2 )	02 52
xwflips	( oaddr len -- )	02 53
xwsplit	( o -- w.lo w.2 w.3 w.hi )	02 54

The following device-handling-related user interface commands have changed between OpenBoot 2.x and OpenBoot 3.x. Their functional behavior is the same. Determine your system's OpenBoot PROM version by entering .version at the ok> prompt, then using the appropriate commands from the following table.

Table D-7

OpenBoot 2.x Command	OpenBoot 3.x Command
.attributes	.properties
cd	dev
reset (to reset full system)	reset-all