Difference between revisions of "83Plus:Software:usb8x/Asm Interface/KBD/KBDInit"

From WikiTI
Jump to: navigation, search
(Inputs: **Changed KBD Input**)
(Notes: callback info)
Line 27: Line 27:
 
Use [[../KBDVersion|KBDVersion]] to find the exact amount of memory required for the keyboard driver's RAM, or just use 32 bytes as a safe static value.
 
Use [[../KBDVersion|KBDVersion]] to find the exact amount of memory required for the keyboard driver's RAM, or just use 32 bytes as a safe static value.
  
The current version of usb8x does not set the LED indicators on the keyboard to indicate caps/num/scroll lockIf bit 0 of the flag byte is reset, however, the driver will still keep track of the lock status and modify keypresses as appropriate.
+
The passthrough callback will use the callback you specified during U_CALL_INIT if you're using the U_CALL systemOtherwise specifiy the callback in register BC.
  
 
== See Also ==
 
== See Also ==
 
* [[../KBDGetKey|KBDGetKey]] - Get keypresses
 
* [[../KBDGetKey|KBDGetKey]] - Get keypresses

Revision as of 21:46, 1 September 2006

Synopsis

Name: KBDInit

Minimum usb8x version: 0.11

Initialize the keyboard driver and hardware

Inputs

  • HL: Address of buffer for keyboard driver's RAM storage
  • DE: Address of temporary buffer for descriptors
  • A: Flags
    • bit 0: reset = auto handle lock keys, reset = pass back locks as regular keys
    • bit 1: Initial state of CAPS LOCK key
    • bit 2: Initial state of NUM LOCK key
    • bit 3: Initial state of SCROLL LOCK key
    • bit 4: set = pass through call-backs to U_CALL_INIT's call-back

Outputs

  • NC: Success

Destroys

  • AF, BC, DE, HL, IX

Notes

Initializes the USB host but assumes the USB driver has already been initialized with [[../../DriverInit|DriverInit]]. KBDInit resets the callback address for use with the keyboard, so the callback address passed to U_CALL_INIT will not be used.

Use [[../KBDVersion|KBDVersion]] to find the exact amount of memory required for the keyboard driver's RAM, or just use 32 bytes as a safe static value.

The passthrough callback will use the callback you specified during U_CALL_INIT if you're using the U_CALL system. Otherwise specifiy the callback in register BC.

See Also

  • [[../KBDGetKey|KBDGetKey]] - Get keypresses