Messages in this thread | | | Date | Mon, 2 Mar 2009 18:04:00 -0500 | Subject | Re: PATCH [1/3] drivers/input/xpad.c: Improve Xbox 360 wireless support and add sysfs interface | From | Mike Murphy <> |
| |
On Mon, Mar 2, 2009 at 5:39 PM, Greg KH <greg@kroah.com> wrote: > > I tried to create such an interface years ago, and the macro tricks > involved ended up being horrible, and in the end, it didn't work. But > if you can come up with something, I'd love to see it. > > thanks, > > greg k-h >
I could probably give it a shot, but possibly not until May... once the current semester ends. I really need to understand the kernel type system -- or at least the types that "should" be exposed to userspace -- before thinking about the design too much. Maybe that's the question that needs to be asked first: in general, what does a sysfs interface into a driver look like? It's certainly flexible enough to do a lot, and the existing interfaces allow it to do a lot, but is there a simplification that covers some large percentage of cases?
Mike -- Mike Murphy Ph.D. Candidate and NSF Graduate Research Fellow Clemson University School of Computing 120 McAdams Hall Clemson, SC 29634-0974 USA Tel: +1 864.656.2838 Fax: +1 864.656.0145 http://cirg.cs.clemson.edu/~mamurph -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |