Launchpad has imported 13 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=25332.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2009-11-28T14:09:25+00:00 Pali wrote:

I have PS/2 keyboard "Intelligent Keyboard K04" with multimedia keys
which is not in keyboard list.

I add xkb_symbols in symbols/inet for this keyboard and now for me
works.

I attached patch.

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/2

------------------------------------------------------------------------
On 2009-11-28T14:10:40+00:00 Pali wrote:

Created attachment 31534
Patch for new keyboard

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/3

------------------------------------------------------------------------
On 2009-11-28T15:09:31+00:00 Sergey V. Udaltsov wrote:

A couple of notes to improve your patch:

1. Why do set vendor as "Generic"? I guess there must be some company
producing these kbds?

2. Did you read the submission Rules
(http://www.freedesktop.org/wiki/Software/XKeyboardConfig/Rules)? In
particular, the section that recommends reusing sections "*_common". It
seems your code can be greatly reduced by using these sections. Also,
I'd appreciate if you sort kbd mapping by keycode.

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/4

------------------------------------------------------------------------
On 2010-01-19T15:41:20+00:00 Pali wrote:

On this keyboard, box and CD driver for Windows isnt any company name,
so I dont know (There is no logo)

I create new patch which use media_nav_acpi_common, it is now correct?

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/5

------------------------------------------------------------------------
On 2010-01-19T15:42:19+00:00 Pali wrote:

Created attachment 32715
New patch for this keyboard

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/6

------------------------------------------------------------------------
On 2010-05-20T15:02:21+00:00 Pali wrote:

Is this new patch ok now?

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/8

------------------------------------------------------------------------
On 2010-05-20T21:01:43+00:00 Sergey V. Udaltsov wrote:

Sorry for delay.

A couple of questions:
1. I32 is mapped usually as XF86WWW. Is it absolutely essential to change it to 
XF86HomePage? Semantically they are very close...
2. I6D is already XF86AudioMedia. Why do you want to add it again?

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/9

------------------------------------------------------------------------
On 2011-04-04T18:36:13+00:00 Pali wrote:

*** Bug 34352 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/13

------------------------------------------------------------------------
On 2011-04-04T18:45:51+00:00 Pali wrote:

1. I used informations and behaviour from Windows driver. On Windows
pressing is this key change URL of browser to homepage.

2. Sorry this is my mistake.

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/14

------------------------------------------------------------------------
On 2011-04-04T19:36:01+00:00 Sergey V. Udaltsov wrote:

I guess the difference between those keysyms lies within the app that
interprets them. Does your browser support them? Is it configurable?

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/15

------------------------------------------------------------------------
On 2011-04-04T19:42:21+00:00 Pali wrote:

I used KDE browser Konqueror and I configured this keysym to homepage
URL.

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/16

------------------------------------------------------------------------
On 2012-04-30T20:42:43+00:00 Bryce Harrington wrote:

What's the status on this bug?

We're carrying this patch (105_intelligent_keyboard.patch) in Ubuntu
Precise, but I'd love to see this finalized upstream rather than carry
it as a divergence from upstream.

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/19

------------------------------------------------------------------------
On 2012-05-01T00:01:10+00:00 Sergey V. Udaltsov wrote:

I am really not sure I should commit that keyboard...

I32 is typically XF86WWW - there is not much difference with XF86HomePage, 
usually handled by the DEs
I67 is XF86Reload - similar to XF86Refresh
and it is already agreed that I6D mapping is redundant.

And, on top of that, this is not used with modern xorg and evdev driver.

Reply at: https://bugs.launchpad.net/xkeyboard-
config/+bug/458206/comments/20


** Changed in: xkeyboard-config
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458206

Title:
  [patch] Please add support for new keyboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/458206/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to