From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
bzolnier@gmail.com, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: linux-next: Tree for July 30
Date: Thu, 31 Jul 2008 20:20:33 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0807312013460.7388@blonde.site> (raw)
In-Reply-To: <20080731115538.238b5e75.akpm@linux-foundation.org>
On Thu, 31 Jul 2008, Andrew Morton wrote:
> On Thu, 31 Jul 2008 14:34:41 -0400
> Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > >
> > > Where would I (Aunt Tillie running FC5) go to find out how to fix my
> > > machine up again?
> >
> > What is Aunt Tillie doing compiling her own kernels on FC5? You
> > OTOH managed to get an answer fairly quickly ;)
>
> I'll ask again: where do our users go to find out how to make their X
> server work again? If the answer is "nowhere" then can we please at
> least write up a simple step-by-step repair procedure, as we'll surely
> be needing it a lot.
Thanks for pursuing this, Andrew: here's a kernel patch deduced
from this thread, which has indeed got me moving again. Perhaps
an optional patch for hotfixes while the right answer is decided.
If you want to test 2.6.27-rc1-mm1, but your Synaptics pad is making X
crash immediately, and like Aunt Tillie and me you're more comfortable
patching your kernel than messing around in your userspace,
then reverting back from 768 to 512 keys should help.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
---
include/linux/input.h | 2 +-
include/linux/mod_devicetable.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- 2.6.27-rc1-mm1/include/linux/input.h 2008-07-31 09:30:09.000000000 +0100
+++ linux/include/linux/input.h 2008-07-31 19:39:20.000000000 +0100
@@ -592,7 +592,7 @@ struct input_absinfo {
/* We avoid low common keys in module aliases so they don't get huge. */
#define KEY_MIN_INTERESTING KEY_MUTE
-#define KEY_MAX 0x2ff
+#define KEY_MAX 0x1ff
#define KEY_CNT (KEY_MAX+1)
/*
--- 2.6.27-rc1-mm1/include/linux/mod_devicetable.h 2008-07-31 09:30:09.000000000 +0100
+++ linux/include/linux/mod_devicetable.h 2008-07-31 19:43:19.000000000 +0100
@@ -274,7 +274,7 @@ struct pcmcia_device_id {
/* Input */
#define INPUT_DEVICE_ID_EV_MAX 0x1f
#define INPUT_DEVICE_ID_KEY_MIN_INTERESTING 0x71
-#define INPUT_DEVICE_ID_KEY_MAX 0x2ff
+#define INPUT_DEVICE_ID_KEY_MAX 0x1ff
#define INPUT_DEVICE_ID_REL_MAX 0x0f
#define INPUT_DEVICE_ID_ABS_MAX 0x3f
#define INPUT_DEVICE_ID_MSC_MAX 0x07
next prev parent reply other threads:[~2008-07-31 19:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080730170635.f737ffe9.sfr@canb.auug.org.au>
2008-07-31 6:10 ` linux-next: Tree for July 30 Andrew Morton
2008-07-31 14:07 ` Dmitry Torokhov
2008-07-31 15:36 ` Bartlomiej Zolnierkiewicz
2008-07-31 15:56 ` Dmitry Torokhov
2008-07-31 17:44 ` Andrew Morton
2008-07-31 18:17 ` Dmitry Torokhov
2008-07-31 18:26 ` Andrew Morton
2008-07-31 18:34 ` Dmitry Torokhov
2008-07-31 18:55 ` Andrew Morton
2008-07-31 19:03 ` Dmitry Torokhov
2008-07-31 19:20 ` Hugh Dickins [this message]
2008-07-31 18:48 ` Rafael J. Wysocki
2008-07-31 18:54 ` Dmitry Torokhov
2008-07-31 19:10 ` Linus Torvalds
2008-07-31 19:24 ` Dmitry Torokhov
2008-07-31 19:42 ` Dmitry Torokhov
2008-07-31 20:10 ` Andrew Morton
2008-08-07 18:11 ` Dmitry Torokhov
2008-08-07 18:50 ` Andrew Morton
2008-08-07 19:06 ` Dmitry Torokhov
2008-08-07 18:55 ` Rafael J. Wysocki
2008-08-01 19:12 ` Linus Torvalds
2008-08-01 19:23 ` Dmitry Torokhov
2008-08-01 19:26 ` Linus Torvalds
2008-07-31 19:44 ` Linus Torvalds
2008-07-31 20:05 ` Dmitry Torokhov
2008-07-31 20:16 ` Linus Torvalds
2008-07-31 20:28 ` Linus Torvalds
2008-07-31 20:39 ` Dmitry Torokhov
2008-07-31 20:28 ` Dmitry Torokhov
2008-07-31 19:13 ` Andrew Morton
2008-07-31 19:57 ` Rafael J. Wysocki
2008-08-04 5:47 ` Stephen Rothwell
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=Pine.LNX.4.64.0807312013460.7388@blonde.site \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).