Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5

From: Jeff Garzik (jgarzik@mandrakesoft.com)
Date: Wed Apr 12 2000 - 05:50:08 EST

David Woodhouse wrote:
>
> For a start, drivers/usb/Config.in calls these variables
> CONFIG_INPUT_MOUSEDEV_SCREEN_[XY] while drivers/usb/mousedev.c calls them
> CONFIG_MOUSEDEV_SCREEN_[XY].
>
> But I'm more concerned at their existence in the first place.
>
> Do I really have to recompile my kernel every time I hit
> Ctrl-Alt-{Plus,Minus} to change my X server's screen resolution?
>
> Couldn't we at least make an _attempt_ at getting this information from a
> framebuffer device, or making it configureable at runtime?

It would be better to have userspace call the mouse device (via a sysctl
or similar) the dimensions of the framebuffer, since that information
might be coming from the X server not fbdev.. 

-- 
Jeff Garzik              | Nothing cures insomnia like the
Building 1024            | realization that it's time to get up.
MandrakeSoft, Inc.       |        -- random fortune

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:18 EST