j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
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: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Segher Boessenkool Sent: Wednesday, April 26, 2006 11:50 AM To: The OpenBIOS Mailinglist Cc: firstname.lastname@example.org Subject: Re: [OpenBIOS] Sparc32 progress
d# 256 encode-int " mmu-nctx" int-property
d# 256 " mmu-nctx" int-property
d# 256 encode-int " mmu-nctx" property
(The former is shorter, the latter is standard OF, can be tokenized).
On Wed, 2006-04-26 at 12:13 -0700, Asif Haswarey wrote:
At some point I plan to start testing with OpenBIOS and endorse the support of OpenBIOS in our fibre-channel and iSCSI products.
Out of curiosity do you have drafts of how you see fibre-channel/iSCSI working with OpenBIOS/1275?