Thanks Mark, Alex, Xavier, Branden.
Mark Vojkovich wrote: > > On Mon, 30 Sep 2002, Thomas Winischhofer wrote: > > The hardware I am developing for has two CRT controllers (actually it's [...] > > registers. However, involving the BIOS is definitely not desired.) > > Those key presses often never get passed the BIOS. They > won't even get to the X-server. That's the way they work on the > recent laptops that I've had experience with. No software outside > of the BIOS knows about it. I know. That's the problem. This key combination causes a *complete* machine lock-up here and on many others. And the idea also was to keep the BIOS from messing around with the registers (eg. while Xv is active, etc). I have seen (literally *seen*, felt like 10 years ago in my assembler era) many SiS BIOSes causing the strangest effects (mouse cursor jumps around wildly in the first left 32 pixels of the screen, xv is totally skrewed up, etc). And the final - and most important - reason is that the BIOS drives the video bridge in slave mode (don't bother...) and this would end up in a catastophe in dual head mode. > > So, I thought of another q&d solution: In the good, old > > CTRL-ALT-KP_Plus/Minus-manner why not intercept eg. CTRL-ALT-KP_Multiply > > and cycle through all possible output devices (LCD, TV and - > > theoretically - secondary VGA, that is)? > > > > Can this be done from within a video driver? I looked though the input > > related code but could not find a solution. > > I suspect that it's not possible for the video driver to intercept > key presses. To hear that from Mark makes it sound quite final.. :( But then, sorry, if I'm annoying: Remember, what I want is not necessarily a secure or standard compliant solution; the target user group is a few people who know what they're doing. What about installing a wakuphandler (or wrapping the old one), wrapping some xkb resource or something like that? Alex Deucher wrote: > you could create a little cli app like s3switch for savage based cards > that will switch the output between tv and crt2. > > then map the keyboard shortcut to run that cli app using your window > manager, etc. This would result in writing a server extension. Otherwise an application outside the server won't be able to communicate with the driver, if I'm not mistaken... (And the driver not only NEEDS to know about the change, it is also the driver which is to PERFORM it; setting up LCD or TV on SiS chipsets is ca 500k source code since the driver supports 8 chipsets with each 4 possible video bridges and so far ca. 60 different panel types) - if anybody knows better, feel free to object! Branden Robinson wrote: > Apart from what Mark said, that particular key combination is already > reserved, though it's not trapped by the server by default. You can be > forgiven for not knowing this, though, as it's not documented everywhere > it should be. ;-) As so many other things as well... :) I saw no code anywhere indicating this. Well then, I don't insist on this very combination anyway. In case I somehow manage to do what I originally intended: What would be a suitable and not-yet reserved combination? Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.winischhofer.net _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
