DOSEMU Technical Guide
PrevNext

6. Old Keyboard Code

This file describes the old keyboard code which was written in late '95 for scottb's dosemu-0.61, and adapted to the mainstream 0.63 in mid-'96.

It was last updated by R.Zimmermann <zimmerm@mathematik.uni-marburg.de> on 18 Sep 96 and updated by Hans <lermen@fgan.de> on 17 Jan 97. ( correction notes marked *HH -- Hans )

6.1. Whats New

What's new in the new keyboard code? A lot.

To the user:

To the dosemu hacker:

There is a compile-time option NEW_KBD_CODE (on by default) to activate the new keyboard code. The old stuff is still in there, but I haven't recently checked whether it still works, or even compiles. Once the new code is reasonably well tested I'll remove it. ( *HH: the old code is made workeable and remains ON per default, it will stay maintained for a while, so we can easily check where the bugs come from )

6.2. Status

Almost everything seems to work well now.

The keyboard server should now quite accurately emulate all key combinations described the `MAKE CODES' & `SCAN CODES' tables of HelpPC 2.1, which I used as a reference.

See below for a list of known bugs.

What I need now is YOUR beta-testing... please go ahead and try if all your application's wierd key combinations work, and let me know if they don't.

6.3. Keyboard server interface

This is all you should need to know if you just want to send keystrokes to DOS.

Use the functions

You may also read (but not write!) the variable 'shiftstate' if necessary.

ehm... see the DANG comments in base/newkbd-server.c for more information...

NOTE: the server's queue is limited to a relatively small number of keyboard events (currently 15). IMO, it is not a good idea to let the queue be arbitrarily long, as this would render the behaviour more incontrollable if the user typed a lot of mad things while a dos program wasn't polling the keyboard.

For pasting, there is special support in base/keyboard/keyb_clients.c which runs on top of the server.

6.4. Keyboard server structure

[NOTE: you won't need to read this unless you actually want to modify the keyboard server code. In that case, however, you MUST read it!]

[Note: I'll have to update this. The queue backend works somewhat different now.]

The central data structure of the keyboard server is the dosemu keyboard queue (to be distinguished from the bios keyboard buffer, which is run by int09 and int16).

The keyboard server code can be largely divided into the `queue frontend' (serv_xlat.c, serv_maps.c), which does keycode translation, and the `queue backend' (serv_backend.c, serv_8042.c), which does the interfacing to DOS. The two sides communicate only through the queue.

Each queue entry holds a data structure corresponding to (mostly) one keypress or release event. [The exception are the braindead 0xe02a / 0xe0aa shift key emulation codes the keyboard processor `decorates' some kinds of keyboard events with, which for convenience are treated as seperate events.]

Each queue entry holds a up to 4 bytes of raw keycodes for the port 60h emulation, along with a 2-byte translated int16h keycode and the shift state after this event was processed. Note that the bios_key field can be empty (=0), e.g. for shift keys, while the raw field should always contain something.

6.4.1. queue handling functions

  • static inline Boolean queue_empty(void);

  • static inline void clear_queue(void);

  • static inline void write_queue(Bit16u bios_key,t_shiftstate shift,Bit32u raw);

  • static void read_queue(Bit16u *bios_key, t_shiftstate *shift, t_rawkeycode *raw);

Accordingly, the keyboard code is largely divided into two parts,

  • the 'front end' of the queue, responsible for translating keyboard events into the 'queue entry' format.

  • the 'back end' of the queue, which reads the queue and sends keycodes to DOS

6.4.2. The Front End

    
     putrawkey() -------->----+
          \   \               |
           \   v              |
            \  translate()    |
             \     |          |
              \    v          \    (t_rawkeycode[4])      /---QUEUE----\
         /->---\---|-----------*------------------------> [ raw        ]
        /       \  \  (t_keysym+char)                     [            ]
     putkey() ->-\--*--------------> make_bios_code() --> [ bios_key   ]
        \         \                                       [            ]
         \         v                           /--------> [ shiftstate ]
          \---> do_shift_keys()               /           \------------/
                    |                        /
                    v        (t_shiftstate) /
                [shiftstate]---------------/
    
    
    --------->  data flow (&calls, sometimes)
    ,,,,,,,,,>  calls

6.4.2.1. Functions in serv_xlat.c

  • static Boolean do_shift_keys(Boolean make, t_keysym key);

  • static Bit16u make_bios_code(Boolean make, t_keysym key, uchar ascii);

  • static uchar translate(t_keysym key);

  • static Boolean handle_dosemu_keys(t_keysym key);

  • void putrawkey(t_rawkeycode code);

  • void putkey(Boolean make, t_keysym key, uchar ascii);

  • void putkey_shift(Boolean make, t_keysym key, uchar ascii, t_shiftstate s);

Any keyboard client or other part of dosemu wishing to send keyboard events to DOS will do so by calling one of the functions putrawkey, putkey, and putkey_shift.

6.4.2.1.1. putrawkey

is called with a single raw scancode byte. Scancodes from subsequent calls are assembled into complete keyboard events, translated and placed into the queue.

6.4.2.1.2. putkey & others

,,,to be documented.

6.4.3. The Back End

6.4.3.1. Queue Back End

    
                       EMULATOR SIDE        |    x86 SIDE
    		                        |
                          ....[through PIC].|....................
                          :                 |           :        v
    QUEUE      .....> out_b_8042() --> [ port 60h ] ----:---> other_int9_handler
    |         :                             |        \  `.......    (:) (|)
    |         :                             |         \         v   (v) (|)
    +->int_chk_q()-> bios_buffer----> [ get_bios_key ]-----> default_int9_handler
          ^  \                           :  |                   |       (|)
          :   \----> shiftstate_buffer   :  |                   v       (v)
          :               |         .....:  |               bios keyb buffer
          :               v        v        |
          :          copy_shift_state() ----+-------------> bios shiftstate
          :                                 |
          :                                 |
          :                                 |
        backend_run()                       |
    
    Abbreviations:
    int_chk_q() = int_check_queue()
    out_b_8042() = output_byte_8042()

6.4.3.2. Functions in newkbd-server.c

  • void do_irq1();

  • void clear_keybuf();

  • static inline Boolean keybuf_full(void);

  • static inline void put_keybuf(Bit16u scancode);

  • void copy_shift_state(t_shiftstate shift);

  • static void kbd_process(void);

Transfer of the keyboard events from the dosemu queue to DOS is done as follows:

As soon as a key is stored into the empty queue, kbd_process() triggers IRQ1 through the PIC emulation, which some time later will call do_irq1().

do_irq1() will prepare for the interrupt execution by reading from the queue and storing the values in the variables raw_buffer, shiftstate_buffer, and bios_buffer, and then call run_irq() to run the actual DOS interrupt handler.

There are two cases:

  • the default int09 handler in the dosemu bios (base/bios_emu.S) will call the helper function get_bios_key(), which returns the translated bios keycode from bios_buffer and copies the shiftstate from shiftstate_buffer. The raw keycodes are not used. get_bios_key() may also return 0 if no translated keycode is ready.

    The int9 handler will also call the `keyboard hook' int15h, ax=????.

  • if a dos application or TSR has redirected the keyboard interrupt, its handler might read from port 60h to get raw scancodes. Port 60h is of course virtualized, and the read returns the value from raw_buffer.

    Note that a mix between the two cases is also possible, e.g. a TSR's int9 handler first reads port 60h to check if a particular key was pressed, then gives over to the default int9 handler. Even these cases should be (and are, I think) handled properly.

    Note also that in any case, int9 is called once for each raw scancode byte. Eg.,suppose the user pressed the PgDn key, whose raw scancode is E0 51:

    • first call to int9: read port 60h = 0xe0 read port 60h = 0xe0 (**) call get_bios_key() = 0 iret do_irq1() reschedules IRQ1 because further scancodes are in the queue

    • second call to int9 read port 60h = 0x51 call get_bios_key() = 0x5100 (bios scancode of PgDn) iret

    (** multiple port 60h reads during the same interrupt yield the same result.)

This is not a complete documentation. If you actually want to hack the keyboard server, you can't avoid reading the code, I'm afraid ;-)

6.5. Known bugs & incompatibilites

6.6. Changes from 0.61.10

6.7. TODO

PrevHomeNext
New Keyboard Code Setting HogThreshold