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

From: David Woodhouse (dwmw2@infradead.org)
Date: Wed Apr 12 2000 - 05:06:37 EST

Next message: dLux: "Re: newbie question (how to measure time)"
Previous message: bert hubert: "Re: EXT2 and BadBlock updating....."
Next in thread: Jeff Garzik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"
Reply: Jeff Garzik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"
Reply: Vojtech Pavlik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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?

Why's it necessary anyway?

-- dwmw2

- 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/

Next message: dLux: "Re: newbie question (how to measure time)"
Previous message: bert hubert: "Re: EXT2 and BadBlock updating....."
Next in thread: Jeff Garzik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"
Reply: Jeff Garzik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"
Reply: Vojtech Pavlik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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