NetBSD Problem Report #51258

From www@NetBSD.org  Mon Jun 20 00:20:52 2016
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 6F2AC7A46A
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 20 Jun 2016 00:20:52 +0000 (UTC)
Message-Id: <20160620002051.671CA7AAA4@mollari.NetBSD.org>
Date: Mon, 20 Jun 2016 00:20:51 +0000 (UTC)
From: venture37@geeklan.co.uk
Reply-To: venture37@geeklan.co.uk
To: gnats-bugs@NetBSD.org
Subject: CAPS_IS_CONTROL kernel option doesn't appear to work
X-Send-Pr-Version: www-1.0

>Number:         51258
>Category:       port-macppc
>Synopsis:       CAPS_IS_CONTROL kernel option doesn't appear to work
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-macppc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 20 00:25:00 +0000 2016
>Last-Modified:  Mon Jun 20 05:15:00 +0000 2016
>Originator:     Sevan Janiyan
>Release:        HEAD
>Organization:
>Environment:
>Description:
Compiling a new kernel with CAPS_IS_CONTROL option enabled doesn't appear to work on the 12" PowerBook G4 1.33Ghz PowerBook6,4 (I don't have another system to test if problem is specific to this model). The position of the caps lock & control key remain the same

dmesg:
http://pastebin.com/wbqXQtN3
>How-To-Repeat:
Compile a new kernel with options CAPS_IS_CONTROL enabled
Test the location of caps lock & control keys
>Fix:

>Audit-Trail:
From: Michael <macallan@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-macppc/51258: CAPS_IS_CONTROL kernel option doesn't appear
 to work
Date: Mon, 20 Jun 2016 01:14:46 -0400

 I never added CAPS_IS_CONTROL to the 'new' ADB subsystem, mostly because
 nobody seemed to miss it ( the driver is from 2007, and it's default
 since 2008 or so ) and also because of the weird way the caps lock key
 is handled by ADB keyboards - it tries to emulate a mechanical locking
 switch, which some older ADB keyboards actually have ( like the
 Extended II ) so you don't get normal up/down events, you get a single
 down for the first press, and a single up for the second.
 I'm not quite sure how this ever really worked with the old drivers.
 Mine's cheating and sends a down, up sequence for each press.
 To make things more annoying, on laptop keyboards the PMU handles the
 caps lock LED, not the keyboard driver.

Home	PR Database Search