On Thu, Jun 06, 2013 at 12:34:57PM +0100, Nick Dyer wrote: > Mark Brown wrote: > > This is yet another reason for implementing the protocol properly > > instead of trying to bodge around the kernel. It really seems like > > the biggest problem here is the decision to try to bodge the entire > > thing into userspace with no kernel support. > With the interface I am proposing it is handled properly, in the kernel driver. You're proposing doing this using direct register I/O... > From an Atmel perspective, Linux is just another platform and we want to > use our existing investment in tools and documentation to manage & debug > chips embedded in Linux based devices. So providing a bridge using a Broadly speaking the kernel upstream just don't care about this. > > That sounded like what you were talking about, it's pretty common and is > > sane enough for reads. > The address pointer is shared between reads and writes on maXTouch, but I > guess that's not a huge problem. That's totally normal.
Attachment:
signature.asc
Description: Digital signature
