Re: [PATCH] make mousedev resolution module parameter

From: Vojtech Pavlik (vojtech@suse.cz)
Date: Sun Oct 15 2000 - 17:25:01 EST

Next message: FORT David: "Re: [2.4.0test10-pre3]drm_proc_init incorrect when multiple deviceare registering"
Previous message: Andrea Arcangeli: "Re: mapping user space buffer to kernel address space"
In reply to: Erik Mouw: "[PATCH] make mousedev resolution module parameter"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, Oct 15, 2000 at 05:09:37PM +0200, Erik Mouw wrote:
> (Second try, this time with the correct mailing list address. Duh.)
>
> Hi,
>
> This patch makes the X and Y resolution in drivers/input/mousedev.c a
> module parameter. In this way the screen resolution can be set by
> using:
>
> modprobe mousedev xres=1280 yres=1024
>
> The configure-time resolution is used as a default resolution. The
> patch is against 2.4.0-test10-pre3. Please consider applying.

Yes, this is a very reasonable patch and I'll apply it to the input CVS.
I'll be forwarding it to Linus, too, but I doubt it'll be accepted in the
current freeze of things, since it doesn't fix any critical bugs.

-- 
Vojtech Pavlik
SuSE Labs
-
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 message: FORT David: "Re: [2.4.0test10-pre3]drm_proc_init incorrect when multiple deviceare registering"
Previous message: Andrea Arcangeli: "Re: mapping user space buffer to kernel address space"
In reply to: Erik Mouw: "[PATCH] make mousedev resolution module parameter"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:29 EST