On Tue, Mar 29, 2016 at 12:18:40PM -0700, Greg KH wrote:

quoted

That is encouraging and persuasive.  I will make submitting the driver
one of my pet projects.  I need to put a new coat of paint on it before
I submit it for consideration, though.  Do I post to this mailing list
when I'm ready?  Or is there a more pertinent one?

I can take it "as-is" through the staging tree (drivers/staging/) which
lets the community start to clean it up now, if you don't have the
time to do the work now.  Then you can work within the kernel
development process to polish up the remaining issues before we merge it
out of the staging tree into the "real" portion of the kernel.

If you are interested in this, just let me know.

In looking at your driver closer, what exactly is it doing?  At first
glance, it seems to be just a bunch of ioctls to directly access the
memory in the card, is that correct?  If so, why not just use the UIO
layer instead?  If not, what is the driver trying to do?

thanks,

greg k-h