Skip to contentSkip to conversation

Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call

PATCH Ari G. Entlich 2 participants 2 messages Feb 19, 2010 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 16583928.142261266584767537.JavaMail.root@zimbra

#1 lore raw
Quoted 2 lines · ----- "Alan Cox

I don't want to change the existing values as they are somewhat visible to user space.

Sorry if I was unclear - I wasn't talking about changing the value, I was just saying that VT_ACKACQ and VT_PROCESS_AUTO are used in different contexts, so it shouldn't matter that they have the same value. One thing that probably would be nice though would be to move the VT_ACKACQ define to a different place in vt.h (probably after the VT_RELDISP define).

Quoted 3 lines

Yes. You could use the VT_EVENT facility for the switch monitoring but the asynchronous nature of the reporting probably isn't what is needed for input device switching etc.

Yeah, it looks like the X server would have to be constantly blocking inside a VT_WAITEVENT ioctl in order to use that, and then it wouldn't be getting anything else done. :-/

Ari

#2 lore raw
Quoted 5 lines

Sorry if I was unclear - I wasn't talking about changing the value, I was just saying that VT_ACKACQ and VT_PROCESS_AUTO are used in different contexts, so it shouldn't matter that they have the same value. One thing that probably would be nice though would be to move the VT_ACKACQ define to a different place in vt.h (probably after the VT_RELDISP define).

That would just as well. It just needs to be obvious for future maintainers that the overlap doesn't matter