Bug 2348 - xf86KbdBSD.c: KEY_ScrollLock should be 0x19?
Summary: xf86KbdBSD.c: KEY_ScrollLock should be 0x19?
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Matthieu Herrb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-21 05:35 UTC by Bauke Jan Douma
Modified: 2005-03-28 18:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Bauke Jan Douma 2005-01-21 05:35:33 UTC
xc/programs/Xserver/hw/xfree86/common/xf86KbdBSD.c
has in wsSunMap[]:

        /* 0x17 */ KEY_NOTUSED,         /* props */
        /* 0x18 */ KEY_Left,
        /* 0x19 */ KEY_ScrollLock,

I wonder if this shouldn't be 0x17 for KEY_ScrollLock
and 0x19 for KEY_NOTUSED.

bjd
Comment 1 Matthieu Herrb 2005-01-22 01:53:41 UTC
Why ? Did you check it on a actual Sun Keyboard ? 
Checking on OpenBSD/sparc64 the current codes are correct.

You need to provide more information (which OS/Architecture, which X.Org version
you're using, on what kind of hardware...) attaching you /var/log/Xorg.0.log
file to this report would be a good starting point. 

The current classification of PC/Linux for this report is probably wrong. The
code you're referring is/was only used on NetBSD and OpenBSD for sparc or
sparc64 systems. 

BTW in X.Org 6.8.2 and -HEAD the code in xf86KbdBSD.c is no longer used
in the default builds. X.Org switched to the new XInput-based 'kbd' driver,
which uses os-support/bsd/bsd_KbdMap.c to handle wskbd.  
Comment 2 Matthieu Herrb 2005-02-03 12:13:24 UTC
If you don't provide some more information on why you think there is a bug 
here, this bug report is going to be closed.
Comment 3 Matthieu Herrb 2005-03-29 12:50:33 UTC
Feedback timeout. 
Please reopen the bug if you've some more information to provide.


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.