Recent Oracle Sparc processors (M7 and M8) have a coprocessor which lives on the cpu chip. The coprocessor is called DAX, and is controlled via sun4v hypercalls. The programmatic interface to the coprocessor is somewhat unorthodox, and is described in detail in the documentation file. The machine descriptor identifies the device as "dax", and all internal documentation refers to it as "dax". But since the term "dax" already has other meanings and uses, we propose to call this driver "oradax"; other suggestions are welcome. To answer the most obvious question "who will use this?", there is a companion userspace library which will be published under UPL shortly. This is a comprehensive collection of higher level functions along with tests and documentation. We'll include a link to this before the code is submitted as a patch. Apart from general comments about the code, style, formatting, logic, etc., we seek suggestions about where the source files ought to live. Right now we've got the main driver source file in drivers/sbus/char, but seeing as "sbus" is a very old Sparc feature and not used anymore, this doesn't seem to be a great place for it. Any and all feedback welcome and appreciated. Thanks, Rob Gardner Sanath Kumar Jonathan Helman -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
