From: Phil Hannent <phil@hannent.co.uk>
To: mwilder <mwilder@cs.nmsu.edu>
Cc: Greg KH <gregkh@suse.de>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] Input: add mmio xi driver
Date: Tue, 25 Nov 2008 09:48:15 +0000 [thread overview]
Message-ID: <492BC9DF.2@hannent.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0811242028360.15284@gremlin.cs.nmsu.edu>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
mwilder wrote:
> What _is_ wrong with the driver? I am guessing that phil@hannet.co.uk is
> just struggling with creating X bindings for the module, but I would like
> to hear some elaboration on what is actually happening here. Enlighten
> me.
>
Hello,
The driver is great, however I have been given the Mimio Xi protocol
documentation and it describes what all of the hex is doing.
Unfortunately I am not at liberty to share the documentation with
anybody due to an NDA, however I would hope that the code will be fairly
clear as to what's happening as a lot of the protocol hex I have setup
as defines.
The initialisation sequence in the current driver is just a series of
hex codes which I am reimplementing as per the Xi protocol. Also the
board has on-board flash for the boards layout, dpi and firmware based
upgrade methods. I am going to implement access to these.
I am also, as you state, working on the X side of things.
I certainly would not want to tread on your toes with regard to the
development of this driver, however as you had mentioned to me in the
past that you did not have the time to devote to this I decided to move
ahead with it myself. Are you planing on making changes to the existing
driver?
Regards
Phil Hannent
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2008-11-25 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 23:22 [PATCH] Input: add mmio xi driver Greg KH
[not found] ` <20080925232237.GA22938-l3A5Bk7waGM@public.gmane.org>
2008-09-26 1:20 ` Randy Dunlap
2008-09-26 3:19 ` Greg KH
2008-09-26 10:51 ` Phil Hannent
2008-09-26 17:46 ` Greg KH
[not found] ` <20080926174607.GA700-l3A5Bk7waGM@public.gmane.org>
2008-11-25 4:19 ` mwilder
2008-11-25 9:48 ` Phil Hannent [this message]
2008-10-02 6:12 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=492BC9DF.2@hannent.co.uk \
--to=phil@hannent.co.uk \
--cc=gregkh@suse.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mwilder@cs.nmsu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).