On Thu, Dec 10, 2009 at 12:47:06PM -0500, Gary Stein wrote: > Ok, I'll go through the coding issues, that checkpatch.pl was useful, > I was not positive on all of the coding standards, but with that > script I can setup my IDE properly to make sure everything works out > (like c99 comments and 80 char limits) > > The wrapping is whatever gmail wants to do in their web interface. > Yeah, gmail web interface is not suitable for patch exchange. However you can use conventional mailers (mutt for example) to send patches via gmail. And they say IMAP works OK with gmail as well. You can also send patch both inline (for commenting) and as an attachment (for applying) if you are forced to use web interface. > I wanted to do FF_CUSTOM (which appears in input.h) and I did try that > for awhile but in the end ff-memless didn't seem to pass everything > along even if I set it up in the flags, etc. > > It would be more work, but is there any way to add a different > FF_CONSTANT through the union process? The problem with adding a new constant (and FF_CUSTOM really) is that only _your_ application and device will make use of it. Have you tried expanding the cosine table in fixp-arith.h to provide better granularity? -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
