From: joshua.clayton@uniwest.com (Joshua Clayton)
To: linux-arm-kernel@lists.infradead.org
Subject: Scanner Protocol:
Date: Wed, 11 Nov 2015 11:05:30 -0800 [thread overview]
Message-ID: <2380450.3tgYhTh7KL@jclayton-pc> (raw)
In-Reply-To: <564381D1.50003@uniwest.com>
On Wednesday, November 11, 2015 09:58:41 AM Steve Eagan wrote:
Chris,
> I still need the latest protocol that uses the scannercode command and I
> will deal with the user vs scannercode problem by defining commands and
> have a library file that they use
Look at source/include/scanner_codes.h in evi.
Its a bit terse, but the codes are all there.
Yeefoo had a more descriptive document somewhere, but neither Chris or I know
where. You could look in Yeefoo's folder on engineering or in Design Notebook.
--
Joshua Clayton
Software Engineer
UniWest
122 S. 4th Avenue
Pasco, WA 99301
(509) 544-0720
parent reply other threads:[~2015-11-11 19:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <564381D1.50003@uniwest.com>]
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=2380450.3tgYhTh7KL@jclayton-pc \
--to=joshua.clayton@uniwest.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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