Linux-kernel mailing list archive 2000-15,: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5

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

David Woodhouse (dwmw2@infradead.org)
Wed, 12 Apr 2000 11:06:37 +0100

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- 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: Jeff Garzik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"

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: Jeff Garzik: "Re: CONFIG_{INPUT_,}MOUSEDEV_SCREEN_[XY] in 2.3.99-pre5"