Hi David The properties I am proposing are Solaris properties. It looks to me like OBP IEEE-1275 already supports different block sizes, but chose a "block-size ( -- block-len )" 'method' implementation in conjunction with the "deblocker" and "disk-label" standard support packages instead of a 'property' implementation. Also, it seems to me that using "block-size" as a Solaris property name, instead of "blksize", might cause confusion since the Solaris property name would then conflict with the already defined OBP "block-size" method.
Please let me know if my understanding is flawed. -Chris > Chris, > > Is there any reason not to spell out the property names, > as in block-size, device-block-size, etc? The property > namespace is intended to be human readable names. > > Also, the 64-bit properties should really be described > as arrays of 2 32-bit ints, hi, low. (if you want > property compatibility with OF-encoding, which we > usually tend to do. There's no such thing as a 64-bit > int prop in OF.) > > It would be nice if the fast-track included the formal > definitions for all these properties, in the usual > form. > > Thanks, > -David >
