diff options
| author | tmk <wakojun@gmail.com> | 2014-01-02 21:10:16 -0800 |
|---|---|---|
| committer | tmk <wakojun@gmail.com> | 2014-01-02 21:10:16 -0800 |
| commit | a35cf0e458090388202c2a0783c5d34f9b69acf7 (patch) | |
| tree | f6df4643f2c801c4386f0c73391000d17840809c /doc/USB_NKRO.txt | |
| parent | 73ab537bfc47263a11c5162bd5087203ef346a88 (diff) | |
| parent | e0a95d4075b972ef5d623aa125e009c28e0edaf8 (diff) | |
Merge pull request #90 from thomasrussellmurphy/master
Spellcheck of README.md and Documentation
Diffstat (limited to 'doc/USB_NKRO.txt')
| -rw-r--r-- | doc/USB_NKRO.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/USB_NKRO.txt b/doc/USB_NKRO.txt index 4751bca868..d9f1d12292 100644 --- a/doc/USB_NKRO.txt +++ b/doc/USB_NKRO.txt @@ -14,7 +14,7 @@ dfj's NKRO(2010/06) http://geekhack.org/showthread.php?p=204389#post204389 -Terminogy +Terminology --------- NKRO ghost @@ -26,7 +26,7 @@ membrane OS Support Status ----------------- USB NKRO is possible *without* a custom driver. -At least following OSes supports. +At least following OS's supports. Windows7 64bit WindowsXP Windows2000 SP4 @@ -37,7 +37,7 @@ At least following OSes supports. Custom Driver for USB NKRO -------------------------- NOT NEEDED -at least when using fllowing report formats on Windows, Linux or MacOSX. +at least when using following report formats on Windows, Linux or MacOSX. USB NKRO methods @@ -47,8 +47,8 @@ USB NKRO methods If the keyboard has 2 virtual keyboard with Standard report(6KRO), it gets 12KRO. Using this method means the keyboard is a composite device. -2. Exteded report - It needs large report size for this method to achive NKRO. +2. Extended report + It needs large report size for this method to achieve NKRO. If a keyboard has 101keys, it needs 103byte report. It seems to be inefficient. 3. Bitmap report @@ -122,8 +122,8 @@ Considerations Compatibility boot protocol minor/old system - Some BIOS doesn't send SET_PROTCOL request, a keyboard can't switch to boot protocol mode. - This may cuase a problem on a keyboard which uses other report than Standard. + Some BIOS doesn't send SET_PROTOCOL request, a keyboard can't switch to boot protocol mode. + This may cause a problem on a keyboard which uses other report than Standard. Reactivity USB polling time OS/Driver processing time |