[Buildroot] [Bug 10851] New: Patch to handle numpad Enter key properly

[Buildroot] [Bug 10851] New: Patch to handle numpad Enter key properly

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10851

            Bug ID: 10851
           Summary: Patch to handle numpad Enter key properly
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: igor.liferenko at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 7506
  --> https://bugs.busybox.net/attachment.cgi?id=7506&action=edit
Patch to handle KEY_ENTER

Hello,

Numpad Enter key is not recognized in application mode.

Please consider applying the attached patch.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10851] Patch to handle numpad Enter key properly

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10851

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
Thanks. 3 comments:

- Judging from the paths in this patch, it seems to come from openwrt. Who is
the author?

- kconfig comes from the Linux kernel. Has this been submitted upstream? I
don't seem to see any KEY_ENTER references in there?

- We prefer patches to be submitted to the mailing list with git-style commit
logs and signed-off-by. See
https://buildroot.org/downloads/manual/manual.html#submitting-patches for
details.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10851] Patch to handle numpad Enter key properly

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10851

--- Comment #2 from Igor Liferenko <igor.liferenko@gmail.com> ---
Hi,

I did a quick investigation and created this patch myself, because I could not
use numpad enter key while configuring openwrt. And as I read on openwrt
website that they use buildroot, I filed this bug report here. I did not submit
this patch to anywhere except here.

Please help me to figure out if I should post this patch to Linux kconfig or to
openwrt. Or could you please just add these changes yourself, the way it seems
more appropriate. Just to make that numpad enter key work the same way as
ordinary enter key in "make menuconfig".

Thanks,
Igor

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10851] Patch to handle numpad Enter key properly

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10851

--- Comment #3 from Peter Korsgaard <jacmet@uclibc.org> ---
Openwrt is not directly related to Buildroot, so openwrt patches should be
submitted to openwrt and not here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10851] Patch to handle numpad Enter key properly

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10851

Arnout Vandecappelle <arnout@mind.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10851] Patch to handle numpad Enter key properly

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10851

--- Comment #4 from Alexandre Esse <alexandre.esse.dev@gmail.com> ---
Hello,

I have the same problem. And I use another workaround that doesn't involves
patch on Buildroot.

Under X:
 - Return keycode is 36 (keysym 0xff0d, Return)
 - Enter (Keypad key) keycode is 104 (keysym 0xff8d, KP_Enter)

Then, I remap the Enter key with ~/.xmodmap.conf file containing one line:
keycode 104 = Return

And apply this configuration: xmodmap ~/.xmodmap.conf

Then, launch: make menuconfig

-- 
You are receiving this mail because:
You are on the CC list for the bug.