(Solved) Keyboard decoder logic

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
Octocontrabass
Member
Member
Posts: 5587
Joined: Mon Mar 25, 2013 7:01 pm

Re: Keyboard decoder logic

Post by Octocontrabass »

octacone wrote:0xE0 = backspace
No it isn't. Try 0x0E instead.
Top
User avatar
Octacone
Member
Member
Posts: 1138
Joined: Fri Aug 07, 2015 6:13 am

Re: Keyboard decoder logic

Post by Octacone »

Octocontrabass wrote:
octacone wrote:0xE0 = backspace
No it isn't. Try 0x0E instead.
+1 for that one. My bad. But that other question still remains a mystery.

Edit: Also right control doesn't work because it's scan code is equal to other trigger...
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
Top
Octocontrabass
Member
Member
Posts: 5587
Joined: Mon Mar 25, 2013 7:01 pm

Re: Keyboard decoder logic

Post by Octocontrabass »

octacone wrote:Edit: Also right control doesn't work because it's scan code is equal to other trigger...
No it isn't. Pause uses 0xE1 as its first byte, not 0xE0.
Top
User avatar
BrightLight
Member
Member
Posts: 901
Joined: Sat Dec 27, 2014 9:11 am
Location: Maadi, Cairo, Egypt
Contact:
Contact BrightLight

Re: Keyboard decoder logic

Post by BrightLight »

Here's a reference for most, if not all, the scancodes that exist on all current keyboards. It explains how the escape sequences work, both 0xE0 and 0xE1.
You know your OS is advanced when you stop using the Intel programming guide as a reference.
Top
Post Reply

Return to “OS Development”