New subject: Sparc32 progress

26 Apr 2006


      Hi Segher,
Just wanted to mention that it is always safe to
stick to the OpenFirmware spec as far as tokens
are concerned.
"int-property" might break the current Sun's tokenizer,
unless "int-property" exists in the tokenizer dictionary
or it is explicitly defined earlier in the FCode.
The key to increase the credibility and interest of
OpenBIOS among the masses is to _not break the OF spec_.
(By-the-way, I am not criticizing anyone.)
At some point I plan to start testing with OpenBIOS and
endorse the support of OpenBIOS in our fibre-channel and iSCSI
products.
_____________
Asif Haswarey
C1069W
QLogic Corporation
26650 Aliso Viejo Parkway
Aliso Viejo, CA 92656
Phone: 949.389.7607
Fax: 949.389.6308
-----Original Message-----
From: openbios-bounces@openbios.org
[mailto:openbios-bounces@openbios.org] On Behalf Of Segher Boessenkool
Sent: Wednesday, April 26, 2006 11:50 AM
To: The OpenBIOS Mailinglist
Cc: stepan@coresystems.de
Subject: Re: [OpenBIOS] Sparc32 progress
...
d# 256 encode-int " mmu-nctx" int-property
Use either
d# 256 " mmu-nctx" int-property
or
d# 256 encode-int " mmu-nctx" property
(The former is shorter, the latter is standard OF, can be tokenized).
Segher
-- 
OpenBIOS                 http://openbios.org/
Mailinglist:       http://www.openbios.org/mailman/listinfo
Free your System - May the Forth be with you