New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux Hyper Key #288

Closed
SevereOverfl0w opened this Issue Apr 26, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@SevereOverfl0w

SevereOverfl0w commented Apr 26, 2016

Linux has a native hyper key code. Would it be possible to reference this somehow from this firmware? I already have mappings in place using it, and it's somewhat simpler in places.

@eltang

This comment has been minimized.

Show comment
Hide comment
@eltang

eltang Apr 26, 2016

Contributor

Do you know which one it is? If you don't, do you know the position of the key Linux recognizes as Hyper on a traditional keyboard?

Contributor

eltang commented Apr 26, 2016

Do you know which one it is? If you don't, do you know the position of the key Linux recognizes as Hyper on a traditional keyboard?

@SevereOverfl0w

This comment has been minimized.

Show comment
Hide comment
@SevereOverfl0w

SevereOverfl0w commented Apr 26, 2016

https://bbs.archlinux.org/viewtopic.php?pid=595002#p595002

Looks like it's e068? Or, escaped 0x68 (scancode)

@jackhumbert

This comment has been minimized.

Show comment
Hide comment
@jackhumbert

jackhumbert Apr 26, 2016

Member

Hyper is all on the OS's side - I don't think there's any way to map it natively, but you can stick in KC_MENU or something similar to be redefined in xmodmap or the equivalent for your distro.

Member

jackhumbert commented Apr 26, 2016

Hyper is all on the OS's side - I don't think there's any way to map it natively, but you can stick in KC_MENU or something similar to be redefined in xmodmap or the equivalent for your distro.

@jackhumbert

This comment has been minimized.

Show comment
Hide comment
@jackhumbert

jackhumbert Apr 26, 2016

Member

Scancodes and keycodes are different, but you could try sticking in 0x68 (KC_F13 I believe) to see what happens on your system.

Member

jackhumbert commented Apr 26, 2016

Scancodes and keycodes are different, but you could try sticking in 0x68 (KC_F13 I believe) to see what happens on your system.

@SevereOverfl0w

This comment has been minimized.

Show comment
Hide comment
@SevereOverfl0w

SevereOverfl0w Apr 26, 2016

http://www.usb.org/developers/hidpage/Hut1_12v2.pdf Page ~58. No reference to hyper in here.

I've had a look through the file /usr/include/linux/input.h and it's include, and it doesn't look like there is any reference to hyper in there.

XFree86 keycode:

    // Other codes never generated.  The XFree86 ddx never generates
    // these codes.
    // Thus we can use them as fake keys
    <HYPR> =   128; // <U80>

So I guess it's a fake key implemented at one of the keyboard layers after the fact. I think it's xfree86 (X.org) layer, but I'm not sure.

Regardless, this can be closed.

SevereOverfl0w commented Apr 26, 2016

http://www.usb.org/developers/hidpage/Hut1_12v2.pdf Page ~58. No reference to hyper in here.

I've had a look through the file /usr/include/linux/input.h and it's include, and it doesn't look like there is any reference to hyper in there.

XFree86 keycode:

    // Other codes never generated.  The XFree86 ddx never generates
    // these codes.
    // Thus we can use them as fake keys
    <HYPR> =   128; // <U80>

So I guess it's a fake key implemented at one of the keyboard layers after the fact. I think it's xfree86 (X.org) layer, but I'm not sure.

Regardless, this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment