public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Härdeman" <david@hardeman.nu>
To: linux-kernel@vger.kernel.org
Cc: dmitry.torokhov@gmail.com
Subject: Changing the number of keys supported by the input subsystem
Date: Thu, 25 Oct 2007 00:04:14 +0200	[thread overview]
Message-ID: <20071024220414.GC10219@hardeman.nu> (raw)

Currently the IR input handling of drivers/media/dvb/ttpci/budget-ci.c 
requires a rc5_device module option which specifies the rc5 device code 
to listen to (or as an alternative, all devices). This means, among 
other things, that multiple remotes can't be used with different 
keymaps.

My idea was to drop the module parameter and allow all rc5 device and 
command combinations to be mapped using one keyboard map.

rc5 device codes are 5 bits, command codes are 6 bits, giving a total of 
2048 possible keycodes.

However, the input subsystem is currently limited to 512 entries. So my 
question is whether it would be possible to extend that and/or make the 
size of the keymap (the keybit member of struct input_dev) dynamic?

-- 
David Härdeman

                 reply	other threads:[~2007-10-24 22:04 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=20071024220414.GC10219@hardeman.nu \
    --to=david@hardeman.nu \
    --cc=dmitry.torokhov@gmail.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