On 5 January 2013 02:10, Samuel Thibault <sthiba...@debian.org> wrote: > Alan Coopersmith, le Mon 31 Dec 2012 17:46:47 -0800, a écrit : >> On 12/31/12 05:36 PM, Samuel Thibault wrote: >> > Michal Suchanek, le Mon 31 Dec 2012 19:22:13 +0100, a écrit : >> >> why is that patch needed? >> >> >> >> It is quite non-obvious why would dummy driver require a console under >> >> any circumstances. It does not render anything anywhere so does not >> >> use console for anything. >> > >> > The console *is* needed for keyboard input. >> > >> > Again, the use case is blind people who have use of possessing an actual >> > screen, and thus don't have any, and thus have to use the dummy driver. >> >> So it sounds like that should be handled by the input driver, not the >> output driver. > > Ok, that makes sense. Input drivers however don't currently have a way > to request the core to callxf86OpenConsole, similar to the absence of > the HW_SKIP_CONSOLE flag in the case of video drivers. > > What do you recommend to add to the InputDriverRec? A driverFunc method > like video drivers? Something else? >
I still don't understand the problem. The evdev driver opens the evdev device when loaded and reads input there. That happens even with dummy video driver so long as you do not carefully prevent the evdev driver from loading, does it not? Thanks Michal -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caomqcttfpntzfryqz-v5mcqoctbk8y0tq_ckxo7dbmg6igt...@mail.gmail.com
