Bug 3952 - SUN Type6 USB keyboard support on x86
Summary: SUN Type6 USB keyboard support on x86
Status: RESOLVED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: doc (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2005-08-02 22:28 UTC by Hanno Hecker
Modified: 2018-12-28 00:52 UTC (History)
6 users (show)

See Also:
i915 platform:
i915 features:


Attachments
reattached diff (4.58 KB, text/plain)
2005-10-03 22:44 UTC, Hanno Hecker
Details
additional "se" layout (538 bytes, text/plain)
2005-11-15 23:08 UTC, Hanno Hecker
Details

Description Hanno Hecker 2005-08-02 22:28:33 UTC
This patch adds support for SUN Type6 USB keyboards on x86 (at least it was just
tested there). Layouts supported are currently de, us, fr_CH and their
nodeadkeys variants. The keyboard section looks like this now:

Section "InputDevice"
    Identifier "Keyboard0"
    Driver    "kbd"
    Option     "XKbModel"   "sun6"
#    Option     "XKbLayout"  "fr_CH"
    Option     "XKbLayout"  "de"
#    Option     "XKbLayout"  "us"
    Option     "XkbVariant"  "nodeadkeys"
EndSection

P.S.: will be available for feedback at end of 08/2005.
Comment 1 Hanno Hecker 2005-08-02 22:29:41 UTC
Created attachment 3212 [details] [review]
dri-not-really-broken-1.patch
Comment 2 Adam Jackson 2005-10-03 18:06:50 UTC
reporter: ping.  the attachment seems to have been corrupted, could you reattach
this patch?
Comment 3 Hanno Hecker 2005-10-03 22:44:00 UTC
Created attachment 3475 [details]
reattached diff 

ok, done.
Comment 4 Hanno Hecker 2005-11-15 23:08:48 UTC
Created attachment 3813 [details]
additional "se" layout

This adds an "se" XkbLayout including "nodeadkeys" variant to the diff.
Comment 5 Sergey V. Udaltsov 2006-04-06 09:14:06 UTC
It seems the patches are somehow messed in the DB. Could you please have a look
at the current xkeyboard-config and create new patches against it? Thanks...
Comment 6 Benjamin Close 2008-01-11 02:37:36 UTC
Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler
Comment 7 dann 2008-03-10 23:04:43 UTC
It would be great if someone could get this keyboard type to work.
If the keycodes are needed, I can supply that. The layout should be available in the Solaris version of this keyboard. (No idea how to put them together, tried a few times and couldn't work it out...)
Comment 8 Alan Coopersmith 2008-04-15 14:28:36 UTC
For reference, the OpenSolaris XKB data files (still based on 
Xorg 7.0 xkb-data unfortunately, not xkb-config) are at:
http://src.opensolaris.org/source/xref/nv-g11n/g11n/src/xorg/keytables/sun-src/

These are pretty much what's also used on Solaris, modulo version skew.
Comment 9 Sergey V. Udaltsov 2008-11-29 11:08:53 UTC
Alan, would it be possible to make a set of proper patches against xk-c?
Comment 10 Stefan 2009-06-05 12:50:46 UTC
Hello,

if created a short patch against xkb-data 1.5.1 under debian unstable. Atleast my Sun Type 6 USB Keyboard (german variant) worked after that.

You can find it under
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513981

Please compile some working keyboard layouts for these keyboard - the current one makes the backspace and the lt/gt/bar keys unusable.

Best Regards,
Stefan
Comment 11 Alan Coopersmith 2009-07-24 20:27:24 UTC
(In reply to comment #9)
> Alan, would it be possible to make a set of proper patches against xk-c?

I don't work on these directly since our globalization teams took them
over a couple of years ago, and don't really have time to sort through
their changes myself, so they'd be the ones to prepare patches.   They
have updated their packages to be based on xkb-config 1.4 now, instead
of the ancient xorg-xkb-data.

Comment 12 Sergey V. Udaltsov 2009-09-15 08:28:09 UTC
Stefan,

I have committed your changes. Not sure about 'working layout'. If you're saying that current layouts (for example, 'us') do not work, may be some other (unused) keysyms should be used in the keycodes and model-specific symbol files?
Comment 13 Stefan 2010-02-02 14:16:41 UTC
With release 1.7 (debian unstable package 1.7-2) the sun Type 6 USB Keyboard (german) work flawlessly except BackSpace 

xev output shows:

  KeyRelease event, serial 34, synthetic NO, window 0x4c00001,
    root 0x142, subw 0x0, time 3557221, (359,-78), root:(1627,677),
    state 0x20, keycode 22 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:                                   
    XFilterEvent returns: False 

having no xorg.conf files, i do not really know what rules are loaded, therefor trying to fix it within /usr/share/X11/xkb/keycodes/sun_vndr/ does not work for me...

The Xorg.0.log shows has the folloing lines, maybe it helps:

(II) XINPUT: Adding extended input device ""CNF7166"" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "sun6"
(**) Option "xkb_layout" "de"

best regards,
Stefan
Comment 14 Stefan 2010-02-02 15:21:15 UTC
looking further it turned out that the symbol definition was missing.
Dumping my current config with "xkbcomp :0.0 -xkb" shows:

xkb_keymap {
xkb_keycodes "evdev+aliases(qwertz)" {
...

xkb_symbols "sun_vndr/us(type6)+de+inet(evdev)+altwin(menu)" {
...

within this symbols, backspace is never defined. I just had to add the following line to /usr/share/X11/xkb/symbols/sun_vndr/us under "sunbasic"
   key <BKSP> { [ BackSpace ] };

regards,
Stefan
Comment 15 Sergey V. Udaltsov 2010-02-02 15:46:48 UTC
Stefan, I just committed huge chunk of code provided by Sun for symbols/sun_vndr. Could you please check from git, if it is ok for you now?

Thanks
Comment 16 Stefan 2010-02-03 15:22:34 UTC
Hi, downloaded master branch from git and all keys work as expected (type6 german layout). The only key i did not test was the sleep key on the upper right edge...

Thanks
Comment 17 Daniel Stone 2018-12-28 00:52:27 UTC
Fixed quite a long time ago.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.