From: Greg Banks <gnb@alphalink.com.au>
To: Jaswinder Singh <jaswinder.singh@3disystems.com>
Cc: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Configure.help entries wanted
Date: Sun, 27 May 2001 12:10:04 +1000 [thread overview]
Message-ID: <3B1061FC.EB18967A@alphalink.com.au> (raw)
In-Reply-To: <E153pEG-0008RL-00@the-village.bc.nu> <01ce01c0e64c$b6cc01e0$52a6b3d0@Toshiba>
Jaswinder Singh wrote:
>
> "Alan Cox" <alan@lxorguk.ukuu.org.uk> wrote :
>
> >
> > Handwriting recognition with fscrib works very well indeed.
> >
>
> But not in Linux SH , there is so Touch Panel Interface in Linux SH yet :(
I have some code which could become the basis for such a thing.
It's a touch panel driver for the DMIDA but it also has a device-
independent layer which does supersampling, scaling, provides
raw and cooked Linux Input interfaces, and a /proc interface to
allow the calibration app to control the scaling.
Unfortunately I can't release it yet for (ahem) legal reasons.
Anyway the limitation with handwriting recognition is not getting
the data out of the hardware but recognising the sample stream as
characters. This is *difficult*.
Greg.
--
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce. - jd, slashdot, 11Feb2000.
next prev parent reply other threads:[~2001-05-27 2:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 5:22 Configure.help entries wanted Eric S. Raymond
2001-05-25 6:03 ` Keith Owens
2001-05-25 6:35 ` Eric S. Raymond
2001-05-25 6:59 ` Keith Owens
2001-05-25 7:10 ` Eric S. Raymond
2001-05-25 7:36 ` Philip Blundell
2001-05-25 8:04 ` [kbuild-devel] " Eric S. Raymond
2001-05-25 10:30 ` Russell King
2001-05-26 4:34 ` [kbuild-devel] " Greg Banks
2001-05-26 6:06 ` Jaswinder Singh
2001-05-26 10:06 ` Greg Banks
2001-05-26 18:50 ` Jaswinder Singh
2001-05-27 1:12 ` Greg Banks
2001-05-27 1:08 ` Jaswinder Singh
2001-05-27 1:29 ` Greg Banks
2001-05-27 1:28 ` Jaswinder Singh
2001-05-27 2:03 ` Greg Banks
2001-05-27 2:08 ` Jaswinder Singh
2001-05-27 1:20 ` Alan Cox
2001-05-27 1:31 ` Jaswinder Singh
2001-05-27 2:10 ` Greg Banks [this message]
2001-05-27 2:13 ` Jaswinder Singh
2001-05-27 2:52 ` Greg Banks
2001-05-27 16:27 ` Pavel Machek
2001-05-28 0:56 ` Greg Banks
2001-05-28 1:05 ` Alan Cox
2001-05-28 2:36 ` Greg Banks
2001-05-28 2:34 ` Jaswinder Singh
2001-05-28 2:58 ` Jaswinder Singh
2001-05-28 3:17 ` Greg Banks
2001-05-27 2:00 ` Greg Banks
2001-05-27 3:06 ` Greg Banks
2001-05-27 3:10 ` Jaswinder Singh
2001-05-27 15:24 ` Greg Banks
2001-05-27 5:03 ` Bill Pringlemeir
2001-05-26 21:48 ` esr
2001-05-27 1:54 ` Jaswinder Singh
2001-05-27 2:43 ` Greg Banks
-- strict thread matches above, loose matches on Subject: below --
2001-05-26 20:13 Jaswinder Singh
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=3B1061FC.EB18967A@alphalink.com.au \
--to=gnb@alphalink.com.au \
--cc=jaswinder.singh@3disystems.com \
--cc=kbuild-devel@lists.sourceforge.net \
--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