Disable mouse, keyboard or other input devices / drivers
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Disable mouse, keyboard or other input devices / drivers
My problem is, that I schedule my program with FIFO - have to be, because it's
a very time critical app. (output) - maschine-nc-program.
That part (subprogram, terminal based) is written in NASM and in there I have to
disable the mouse, because of the user activities - the DM(Display Manager) can't execute the mouse events during that app. runtime, I only say left bottom corner, so unusual things could happen after return and the mouse events get executed.
Well I have some ideas : (1= easiest)[list=1][*]Clear the event buffer the DM is reading from, before switching back to SCHED_OTHER.[*]Keep the x-server away from writing to that event buffer and/or generating a mouse event during app. runtime[*]Keep linux away from handle the mouse IRQs - unload the mouse driver perhaps, that's silly I know,
because the interrupt have to be handled and the x-server generates also an mouse event, that couldn't be
decoded from the missing device driver (left bottom corner).[*]That could work: make a copy of the IDT and set the possible
mouse entries (serial,usb,ps2) to I_NULL, than load it in IDTR.
Also silly, I think that makes surly an INT13 and linux close the app (surly also as root).[/list=1]
So please give me any solution or hint you could have, or how I can realize such ideas.
O.K. it seems, that I have read in to fast cycles from the keyboard interface port 0x60. Now I stretched the cycles and all goes fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.