From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Marcos D. Marado Torres" <marado@student.dei.uc.pt>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] psmouse info in 2.6.1-rc1
Date: Mon, 5 Jan 2004 13:17:23 -0500 [thread overview]
Message-ID: <200401051317.23795.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0401051711170.23750@student.dei.uc.pt>
On Monday 05 January 2004 12:16 pm, Marcos D. Marado Torres wrote:
> Hi there...
> I don't really know if this is only in -rc1-mm1 but I suppose -rc1 is
> affected also.
>
> The new changes in drivers/input/mouse/psmouse-base.c make that we
> don't have anymore to give to kernel psmouse_proto=imps, but only
> proto=imps , so the info about it is wrong... Please apply the patch:
>
> --- linux-2.6.1-rc1-mm2/drivers/input/mouse/Kconfig 2004-01-05
> 10:51:16.000000000 +0100 +++
> linux-2.6.1-rc1-mm2-mbn1/drivers/input/mouse/Kconfig 2004-01-05
> 13:34:26.000000000 +0100 @@ -30,7 +30,7 @@
> http://www.geocities.com/dt_or/gpm/gpm.html
> to take advantage of the advanced features of the touchpad.
> If you do not want install specialized drivers but want
> tapping - working please use option psmouse.proto=imps.
> + working please use option proto=imps.
>
> If unsure, say Y.
It is psmouse.proto=imps if psmouse is built in the kernel and proto=imps
if psmouse is compiled as a module. I mentioned only the first form because
I assumed that most people have it built-in.
Generally with the module_param macros kernel parameters have a prefix
in form of "module_name." if module is built into the kernel.
Dmitry
next prev parent reply other threads:[~2004-01-05 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 17:16 [PATCH] psmouse info in 2.6.1-rc1 Marcos D. Marado Torres
2004-01-05 18:17 ` Dmitry Torokhov [this message]
2004-01-05 18:29 ` Marcos D. Marado Torres
2004-01-05 20:52 ` Marcos D. Marado Torres
2004-01-06 5:21 ` Dmitry Torokhov
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=200401051317.23795.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marado@student.dei.uc.pt \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.