mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Moles <jeremy@emperorlinux.com>
To: linux-kernel@vger.kernel.org
Subject: Seeking Guidance For Serial Driver Creation
Date: Tue, 10 Nov 2009 11:50:47 -0500	[thread overview]
Message-ID: <1257871847.2760.83.camel@localhost.localdomain> (raw)

I am working on getting all of the hardware for a Panasonic CF-H1
supported. I am also interested in writing an OSS driver for the
internal barcode scanner device.

What I'm looking for is someone familiar with the serial API to take a
quick look at some data I've snooped from Windows' COM1 device--which I
acquired by running a serial snooping utility on the serial port from
the time that I push the "scan" button to the time it stops--and perhaps
offer a quick bit of advice on how I should proceed. I have a lot of
experience hacking EXISTING specialty drivers (things like pcc-acpi,
ibm-acpi, sony-acpi, sonypi, etc.) and I'm no stranger to low-level C
code, but this will be the first time I've written a serious driver from
scratch.

The information grokked from Windows can be found here:

	http://jeremymoles.com/scanner

I've divided it up as best I can; unfortunately, this data is exported
as-is from the Windows tool. The most interesting file is probably:

	http://jeremymoles.com/scanner/packet-view.html



Something to note is that unlike normal serial barcode scanners, the
actual "begin scanning" message isn't initiated by hardware. :( On a
traditional device it seems that you simply press a button on the
scanner and the text representation of that barcode is just dumped out
on the tty for you to read. In the case of this machine, a button on the
front (which must be handled in software) is pressed, and the OS takes
over and initializes the device and somehow informs it to "begin
scanning." I believe this is the function of the first few lines of each
of the files I've uploaded, but I could be wrong.

Thanks beforehand...


                 reply	other threads:[~2009-11-10 17:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1257871847.2760.83.camel@localhost.localdomain \
    --to=jeremy@emperorlinux.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®