From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Marcos D. Marado Torres" <marado@student.dei.uc.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-mm2
Date: Tue, 30 Dec 2003 00:21:57 -0500 [thread overview]
Message-ID: <200312300021.57227.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0312300454120.7711@student.dei.uc.pt>
On Tuesday 30 December 2003 12:03 am, Marcos D. Marado Torres wrote:
> First of all, thanks for the help, my problem is now solved, and it's
Glad to hear it!
> good to see the patch you sent so used just have to pass
> psmouse_proto=... to the kernel whenever they compiled it as a module
> or built-in in the kernel. However the question is still there... I
> mean: I now know the sollution because I asked here on lkml, and now I
> understand what's really happening, but if the target is to get the
> work easy for those upgrading from 2.4, then you're failing... I mean,
> for those who are in the same sittuation than me they will just stop
> having the mouse tap feature with the kernel update, so why don't just
> make the psmouse_proto={bare|imps|exps} argument selectable in the
> kernel configuration?
I might consider expanding psmouse help section a bit but I somewhat
concerned that it will not have much exposure.
>
> Once again, maybe there's something more that I can't see here, but
> makes pretty much more sense to me people have to do the choice while
> compiling the kernel than having no choice and then having to pass an
> argument to the kernel...
So a distribution for example does not have to supply bazillion kernel
versions to satisfy everyone.
BTW, are you opposed to having special driver or you just didn't have
time to try it out?
Dmitry
next prev parent reply other threads:[~2003-12-30 5:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 9:32 2.6.0-mm2 Andrew Morton
2003-12-29 11:06 ` 2.6.0-mm2 Joshua Kwan
2003-12-29 14:46 ` 2.6.0-mm2 Ian Soboroff
2003-12-29 16:39 ` 2.6.0-mm2 GCS
2003-12-29 20:10 ` 2.6.0-mm2 Marcos D. Marado Torres
2003-12-29 23:32 ` 2.6.0-mm2 Dmitry Torokhov
2003-12-30 3:05 ` 2.6.0-mm2 Marcos D. Marado Torres
2003-12-30 4:15 ` 2.6.0-mm2 Dmitry Torokhov
2003-12-30 5:03 ` 2.6.0-mm2 Marcos D. Marado Torres
2003-12-30 5:21 ` Dmitry Torokhov [this message]
2003-12-30 6:26 ` 2.6.0-mm2 Marcos D. Marado Torres
2003-12-29 18:31 ` 2.6.0-mm2 Dax Kelson
2003-12-29 18:53 ` 2.6.0-mm2 Joshua Kwan
2003-12-29 18:55 ` 2.6.0-mm2 Joshua Kwan
2003-12-29 19:28 ` 2.6.0-mm2 Stef van der Made
2003-12-29 20:24 ` 2.6.0-mm2 Shawn
2003-12-29 21:35 ` 2.6.0-mm2 Stef van der Made
2003-12-29 22:48 ` 2.6.0-mm2 Mike Fedyk
2003-12-29 23:01 ` 2.6.0-mm2 Linus Torvalds
2003-12-29 19:59 ` 2.6.0-mm2 Ramon Rey Vicente
2003-12-29 20:57 ` 2.6.0-mm2 Felipe Alfaro Solana
2003-12-29 21:52 ` 2.6.0-mm2 Davide Libenzi
2003-12-29 22:26 ` 2.6.0-mm2 Felipe Alfaro Solana
2003-12-29 22:38 ` 2.6.0-mm2 Diego Calleja
2003-12-30 9:45 ` 2.6.0-mm2 Jens Axboe
2003-12-31 1:25 ` 2.6.0-mm2 (compile stats) John Cherry
[not found] <1822L-89t-7@gated-at.bofh.it>
2003-12-29 12:08 ` 2.6.0-mm2 Ronny V. Vindenes
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=200312300021.57227.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox