linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
	Pavel Pisa <ppisa4lists@pikron.com>,
	linux-input <linux-input@atrey.karlin.mff.cuni.cz>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH] Generic, platform independent matrix keyboard support
Date: Wed, 10 Oct 2007 09:10:04 -0400	[thread overview]
Message-ID: <d120d5000710100610n50d7c62cuf365ad0d2ded5916@mail.gmail.com> (raw)
In-Reply-To: <200710091905.39882.david-b@pacbell.net>

On 10/9/07, David Brownell <david-b@pacbell.net> wrote:
> On Tuesday 09 October 2007, Pavel Pisa wrote:
> > On the other hand I cannot imagine electronic designed wanting
> > so many wires. Reduction of the wires counts is why matrix keyboards
> > are used. The 32 bits limitation then means that maximal supported
> > keyboard can be 32x32 key => 1024 keys, that is quite imposing.
>
> Yes:  http://weblog.sinteur.com/?p=20412  :)
>

Thank you David ;)

-- 
Dmitry

  reply	other threads:[~2007-10-10 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200709021228.58354.ppisa4lists@pikron.com>
     [not found] ` <200710090218.27964.ppisa4lists@pikron.com>
     [not found]   ` <20071009074020.GA14231@flint.arm.linux.org.uk>
     [not found]     ` <200710091222.10677.ppisa4lists@pikron.com>
2007-10-09 16:22       ` [PATCH] Generic, platform independent matrix keyboard support Dmitry Torokhov
2007-10-10  1:32         ` Pavel Pisa
2007-10-10  2:05           ` David Brownell
2007-10-10 13:10             ` Dmitry Torokhov [this message]
2007-10-14 20:57               ` Pavel Pisa
2007-10-15  0:18                 ` David Brownell
2007-10-10 13:48           ` Dmitry Torokhov
2007-08-26 18:48 Pavel Pisa

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=d120d5000710100610n50d7c62cuf365ad0d2ded5916@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux@arm.linux.org.uk \
    --cc=ppisa4lists@pikron.com \
    --cc=s.hauer@pengutronix.de \
    /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).