"OFA does support PPC platforms,"
In other words are you saying there is windows for PPC? I was sure this
was abounded about 10 years ago.
Thanks
Tzachi
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean Hefty
Sent: Monday, April 21, 2008 10:01 PM
To: Alex Naslednikov; Smith, Stan; Ishai Rabinovitz
Cc: [email protected]
Subject: RE: [ofw] WDK build environment migration thoughts
Q2.Does TO_LONG_PTR work for both big endian and little endian
systems?
TO_LONG_PTR works only with little endian, because we do not
support PPC platform
Currently, there's no need to extend it to support big endian
OFA does support PPC platforms, plus Itanium can be configured
for either little or big endian format. I'm fine deferring adding this
support, but the code should not assume that it will always be little
endian.
Q3. How is the padded space initialized?
Inside sdp, all padded space was initialized by class
constructor (except one specific case)
In all other code, that not C++, padded space was initialized by
cl_memclr before setting the field and before calling to ioctl procedure
Please, see my next mail with examples from the code
It's kind of ugly to require setting padded fields to specific
values. This only needs to be done when crossing from a 32-bit to
64-bit boundary, so we can restrict this to the kernel proxy. (Btw, you
can replace the unnamed union and add padding to structures only if
compiling in 32-bit mode.)
It's still not clear to me how you maintain binary compatibility
with the IBAL APIs. The IBAL calls take 64-bit pointers as input
parameters. What are the definitions for the ib_blah_handle_t types?
- Sean
_______________________________________________
ofw mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
