From nobody Tue Nov 5 23:43:29 2024 X-Original-To: freebsd-usb@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XjlK32HFvz5bn7y for <freebsd-usb@mlmmj.nyi.freebsd.org>; Tue, 05 Nov 2024 23:43:35 +0000 (UTC) (envelope-from frank.hilgendorf@posteo.de) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XjlK22QRtz4nbW for <freebsd-usb@freebsd.org>; Tue, 5 Nov 2024 23:43:33 +0000 (UTC) (envelope-from frank.hilgendorf@posteo.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=posteo.de header.s=2017 header.b=ScUIZH3V; spf=pass (mx1.freebsd.org: domain of frank.hilgendorf@posteo.de designates 185.67.36.66 as permitted sender) smtp.mailfrom=frank.hilgendorf@posteo.de; dmarc=pass (policy=none) header.from=posteo.de Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 88771240101 for <freebsd-usb@freebsd.org>; Wed, 6 Nov 2024 00:43:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1730850211; bh=/w57NDv4z+/pNufb2bxxpiLaoqISY3jshLoV3teJIHQ=; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject: Message-Id:Date:To:From; b=ScUIZH3VXml13jAwBgBCo5UrLuVetZ4YEL1JmQvya9nn/9ab1PNk1jS3s8eJpYPiu fCO7uk0x7WxOEKm13QgXMni66fMAlVdK5HdwKDN3QTyRQgOH3mSwe8iqIqviANlr26 Xjk9a0/Ae3ziXLR6ph9Hv8Ae3X88k7qS1V7rCB9TgR51SD+tTo7aScIovqkG3qf7rn s2RyUYlhh8TJyoU5/7GmhlblUnY5YdireWaOZKMT2Dwb4/fX50qTy4c0Y4Ya6TXww4 SUOZ+eUM1dtLS2H7XTTaoF0Iul3PYdu7drPYn2sJTu/LvjWxsW6rlv51+/bo+e3dLJ avg4m9goLJZMg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4XjlJz0M9Yz6tvn for <freebsd-usb@freebsd.org>; Wed, 6 Nov 2024 00:43:30 +0100 (CET) From: Frank Hilgendorf <frank.hilgendorf@posteo.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: FreeBSD <freebsd-usb.freebsd.org> List-Archive: https://lists.freebsd.org/archives/freebsd-usb List-Help: <mailto:usb+help@freebsd.org> List-Post: <mailto:usb@freebsd.org> List-Subscribe: <mailto:usb+subscribe@freebsd.org> List-Unsubscribe: <mailto:usb+unsubscribe@freebsd.org> X-BeenThere: freebsd-usb@freebsd.org Sender: owner-freebsd-usb@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Apple Notebooks - Enable the FN key Message-Id: <E3C9FFD0-1F4E-4CE2-9BD5-7DDE714DBB56@posteo.de> Date: Tue, 5 Nov 2024 23:43:29 +0000 To: freebsd-usb@freebsd.org X-Spamd-Result: default: False [-5.28 / 15.00]; DWL_DNSWL_LOW(-1.00)[posteo.de:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.977]; DMARC_POLICY_ALLOW(-0.50)[posteo.de,none]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[185.67.36.66:from]; R_SPF_ALLOW(-0.20)[+ip4:185.67.36.0/23]; R_DKIM_ALLOW(-0.20)[posteo.de:s=2017]; RWL_MAILSPIKE_GOOD(-0.10)[185.67.36.66:from]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[posteo.de:+]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ASN(0.00)[asn:8495, ipnet:185.67.36.0/23, country:DE]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-usb@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-usb@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4XjlK22QRtz4nbW X-Spamd-Bar: ----- Hello, trying to adopt FeeBSD to my old MacBookPro 3,1 I ran into the problem = - like many others before - that the media key functions on the internal = keyboard cannot be used. Expectation is, that pressing the FN key in = conjunction with one of the function keys F1..F12 generates the = respective event, e.g. Screen Brightness UP or DOWN. This does not work = because FN key state changes do not pass the ukbd (and hkbd) keyboard = driver. Currently, the FN key is recognized by the driver. It has code 0x0003 on = the non-standard usage page 0xffff. Currently, when FN is pressed the = four arrow keys are mapped to Home / End / PgUp / PgDown. that's all, = the FN key state itself is not output by the driver. This is what I would like to change, by implementing two things: 1) Remap FN to an unused keyboard HID usage code (which?) 2) Treat FN like any of the other modifier keys Then, FN can be used as a modifier in xkb mappings of the media keys. =20= There should be no entry in the AT scan code translation table. Hence, = FN key actions should not cause problems with the console key mappings. Is this a useful approach? Any feedback is appreciated. Regards, Frank=