# US 2003/0188049 A1 · Interfacing devices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2003/0188049 A1 - Document ID: US20030188049A1 - Status: Published application - Kind: A1 - Application number: 10/370,279 - Filed: 2003-02-18 - Published: 2003-10-02 - Earliest claimed: 2002-02-21 - Assignees: Adder Technology Limited - Inventors: Nigel Anthony Dickens - Web page: https://patentgrep.com/patent/US20030188049A1 ## CPC - G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers} - G06F 3/0227: {Cooperation and interconnection of the input arrangement with other functional units of a computer (G06F3/023 - G06F3/037 take precedence)} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A device for interfacing an input device and a computer includes a microprocessor in communication with a memory, the memory storing download instructions and having a re-writable memory area for storing input device driver data downloadable by the microprocessor using the download instructions. The microprocessor is programmed to use the input device driver data to enable data transmission between the computer and the input device. In an alternative device, the microprocessor is programmed to extract input device driver data from data transmitted to the device in a standard input device protocol and to save the input device driver data in the memory. An upgradeable KVMA and KVM switch and extender including such devices are described. ## Claims ### Claim 1 A device for interfacing an input device and a computer connected to the device, the device including: a microprocessor in communication with a memory, said memory storing download instructions and having a re-writable memory area for storing input device driver data downloadable by the microprocessor using the download instructions, the microprocessor being programmed to use the input device driver data to enable data transmission between the computer and the input device. ### Claim 2 (depends on 1) A device as claimed in claim 1, in which input device driver data is re-writeable to the memory independently of other data stored in the memory. ### Claim 3 (depends on 1) A device as claimed in claim 1, in which the download instructions are protected from being overwritten by downloaded data. ### Claim 4 (depends on 1) A device as claimed in claim 1, in which the device driver data includes device driver instructions and driver data. ### Claim 5 (depends on 4) A device as claimed in claim 4, in which the driver data includes data selected from: data indicating conditions under which the driver code may look for certain data sequences; data identifying sequences of transmitted bytes; data indicating what the driver does when certain sequences of data are detected; state information telling the driver code what state the device is in when byte sequences are detected; data sent to the computer in response to a query from the computer; pointers to the location of other data items; and data that defines the sequences of data sent to the input device. ### Claim 6 (depends on 5) A device as claimed in claim 5, in which the driver data is stored in a look up table. ### Claim 7 (depends on 6) A device as claimed in claim 6, in which the device includes an EEPROM accessible by the processor and the look up table is stored in the EEPROM. ### Claim 8 (depends on 1) A device as claimed in claim 1, in which the memory includes a free area allocated to device driver data. ### Claim 9 (depends on 8) A device as claimed in claim 8, in which the free area is contiguous to device driver memory areas. ### Claim 10 (depends on 1) A device as claimed in claim 1, in which the memory also stores data transmission protocol conversion data. ### Claim 11 (depends on 1) A device as claimed in claim 1, in which the memory stores data transmission and/or reception routines. ### Claim 12 (depends on 1) A device as claimed in claim 1, in which the memory stores a download status data item. ### Claim 13 (depends on 1) A device as claimed in claim 1 in which the input device driver data is mouse and/or keyboard driver data. ### Claim 14 (depends on 1) A device as claimed in claim 1, in which the memory stores main control program data which is re-writable. ### Claim 15 A device for interfacing an input device and a computer connected to the device, the device including: a microprocessor in communication with a memory, the microprocessor being programmed to extract input device driver data from data transmitted to the device in a standard input device protocol and saving the input device driver data in the memory. ### Claim 16 (depends on 15) A device as claimed in claim 15, in which the standard input device protocol is PS/2. ### Claim 17 (depends on 16) A device as claimed in claim 16, in which the input device driver data is transmitted within a “set typematic rate/delay” data sequence. ### Claim 18 (depends on 15) A device as claimed in claim 15, in which the microprocessor is programmed to generate false key press data to communicate with the computer. ### Claim 19 A KVM or KVMA switch or extender including a device as claimed in any preceding claim. ### Claim 20 A method for configuring a device for interfacing an input device and a computer connected to the device, the method including: downloading input device driver data from the computer and storing the input device driver data in a re-writable memory area of a memory in communication with a microprocessor in the device; and the microprocessor using the input device driver data to enable data transmission between the computer and the input device. ### Claim 21 (depends on 20) A method as claimed in claim 20, and including using a download program stored in the memory to download the input device driver data. ### Claim 22 (depends on 20) A method as claimed in claim 20, in which the input device driver data is stored independently of data already stored in the memory. ### Claim 23 A method for configuring a device for interfacing an input device and a computer connected to the device, the method including: transmitting input device driver data to the device in a standard input device protocol; extracting input device driver data from the standard input device protocol; and saving the input device driver data in a memory in communication with a microprocessor in the device. ### Claim 24 (depends on 23) A method as claimed in claim 23, in which the standard input device protocol is PS/2. ### Claim 25 (depends on 23) A method as claimed in claim 23, in which input device driver data is transmitted within a keyboard data sequence. ### Claim 26 (depends on 23) A method as claimed in claim 23, in which input device driver data is transmitted within a mouse data sequence. ### Claim 27 (depends on 24) A method as claimed in claim 24, in which input device driver data is transmitted within a “set typematic rate/delay” data sequence.