I'm new to your code, have only seen a small bit of it, but from what I've seen, it does not offer "general DIAG".
On Mon, 10 Oct 2005, Christian Borntraeger wrote: > vmcp has the same capability. You can open the devicenode /dev/vmcp > read the repsonse and use an ioctl to query the return code. You > can also use another ioctl to query the size of the response, if > the buffer would have been large enough. So in fact, you can > implement the buffer resizing/retry logic on top of the vmcp kernel > module. You missed the point. The point is that neither 'vmcp' nor /dev/vmcp offer even a hint of the underlying DIAG interface. Both 'vmcp' and /dev/vmcp obscure the DIAG interface from the very programmers who should see it. In the CPINT case, yes, 'hcp' hides the DIAG details. That's as it should be. > We are currently discussion the user space application, the kernel > module is able to do all the different things using the ioctls. For which DIAGnose codes? By way of what /dev entries? -- R; ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
