From: Karim Yaghmour <karym@opersys.com>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Eric Reischer <emr@engr.de.psu.edu>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org,
debian-powerpc@lists.debian.org
Subject: Re: Issue compiling 2.4test10
Date: Mon, 13 Nov 2000 04:12:09 -0500 [thread overview]
Message-ID: <3A0FB18A.534F2F21@opersys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10011021021110.19979-100000@opal.biophys.uni-duesseldorf.de>
Michael Schmitz wrote:
>
> Would this patch help?
>
> --- drivers/input/keybdev.c.org Thu Nov 2 10:13:39 2000
> +++ drivers/input/keybdev.c Thu Nov 2 10:19:43 2000
> @@ -36,7 +36,7 @@
> #include <linux/module.h>
> #include <linux/kbd_kern.h>
>
> -#if defined(CONFIG_X86) || defined(CONFIG_IA64) || defined(__alpha__) || defined(__mips__)
> +#if defined(CONFIG_X86) || defined(CONFIG_IA64) || defined(__alpha__) || defined(__mips__) || defined(CONFIG_MAC_HID)
>
I've tried this on my PowerBook and it doesn't work. The keymap is broken and
pressing anything on the keyboard will output something completely different.
This is fixed if the "defined(CONFIG_MAC_HID)" gets move the "#elif" part of
the "#if" mentionned above.
That said, 2 and 3 button emulation is broken for (at least) the PowerBook on test-10.
I've tried the
echo "1" > /proc/sys/dev/mac_hid/mouse_button_emulation
and there's no effect. Anyone know what this is about?
Thanks.
===================================================
Karim Yaghmour
karym@opersys.com
Operating System Consultant
(Linux kernel, real-time and distributed systems)
===================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-13 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 1:32 Eric Reischer
2000-11-02 9:22 ` Michael Schmitz
2000-11-13 9:12 ` Karim Yaghmour [this message]
2000-11-13 9:19 ` Michael Schmitz
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=3A0FB18A.534F2F21@opersys.com \
--to=karym@opersys.com \
--cc=debian-powerpc@lists.debian.org \
--cc=emr@engr.de.psu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.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
all inboxes | Powered by JetHome®