From owner-freebsd-hardware@freebsd.org Tue Feb 21 00:49:42 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0624CE6E6B for ; Tue, 21 Feb 2017 00:49:42 +0000 (UTC) (envelope-from large.hadron.collider@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D7C91597 for ; Tue, 21 Feb 2017 00:49:42 +0000 (UTC) (envelope-from large.hadron.collider@gmx.com) Received: from [192.168.0.12] ([50.69.17.158]) by mail.gmx.com (mrgmx002 [212.227.17.184]) with ESMTPSA (Nemesis) id 0LlVZv-1c6uXi2ODH-00bIa2 for ; Tue, 21 Feb 2017 01:49:33 +0100 To: freebsd-hardware@freebsd.org From: Large Hadron Collider Subject: In which a touchscreen is rehabilitated, or: How I learned to stop being scared and just hack at /usr/src/sys/dev Message-ID: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> Date: Mon, 20 Feb 2017 16:49:32 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:aO9MHDV5xYWs10uZbe2ShO0WSE0ecGly5l84dwPq5et59NRll9O aVZAgs9PML5AahvI8ZBy1k1emSB7PoEv8CP9s87NHkRUBXtq4adjumuoDavhp3QTwaSlgQt ChmT+a01OsD4OkNjS7ljnauT63bkvetVDB6uA0w1a63pxlfXrrx7YsHxNU5dlVvOnoxnLRY HHaxupI9yrnz+LyJgYeKQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:BW2BfDT61TI=:l8xmjrFWaNyZI6vF37m04i lD2/5EujWFOvLucr1J9yntCvOGiMcMNpYyg35wlQ5HnZ/3x2XXqq7PHqm4RKSCJ6rmhPKB3q5 1FEBTJ1g00fgIpoLJAoCe+6c6YFAwVGS/ztpUf9c2wwvKs+X/x0r3Swq9KWwJozabQHpoBP// 0qLSTj4wZefiKBqrubfZzEq4XERH2sNaTnauQMpYMbdz56UBq3tUzvgqi6OVBeNTu5FxElReX tZbDD+ZfCWdjZN0sbBymOCYRstsET3rnjzucVwPeKzyMF3DkOOHRMRFQbpqCpTQcr1j/JtHCI sOgLEP0OM/MNvATiB8SlfSN86Mp7tvfZ3KgQL7zETrrypZl+9Ugf5LwMq2UElI4bpdMPOWZpC sZ0pAsfub6Z30EidBfDDFjdE60dgCLY91qGrrxf2ri0gmnHjFEhdI5+pBmQV+bKZTF2as2LJC 9maOgDpDdg== X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 00:49:42 -0000 (Apologies if this doesn't line break at 79 chars - full formatting in HTML but this may be lost - shouldn't lose any info though) Good day subscribers to this list. I'm here with what could be described as a success story and a patch in the same e-mail. Please do stop me if WACF00E has already been slated for the next major release - but I would like to share how I got my HP Elitebook 2760p's touchscreen working. So I, a former and now again user of FreeBSD (I got hacked the first time... silly Ellie shouldn't give shells to strangers, should she now?) have a laptop whose screen is touch-capable, and whose touchscreen subsystem is based on a serial Wacom tablet. It worked under Linux and too I presume Windows (with which the laptop shipped), but not FreeBSD. I thought, what was going on? What was I doing wrong? So after some poking around I discovered that the screen is a WACF00E - not supported in 11.0-RELEASE-p1 by the driver that handles the UART. It showed unknown pnpinfo _HID=WACF00E _UID=0 at handle=\_SB_.PCI0.LPCB.SIO_.DIGI as the devinfo line. Intriguingly, there was this line in uart_bus_acpi.c:static struct isa_pnp_id acpi_ns8250_ids[]: {0x04f0235c, "Wacom Tablet PC Screen"}, /* WACF004 */ So I thought what the hell, I'd copy that line under itself and change 04f0 (which is byte-swapped, counterintuitively) to 0ef0, representing WACF00E. Adding this: {0x0ef0235c, "Wacom Tablet PC Screen 00e"}, /* WACF00e */ to uart_bus_acpi.c and this: {0x0ef0235c, NULL}, /* WACF004 - Wacom Tablet PC Screen*/ (Yes it should read WACF00E in the comment) under the WACF004 entry in uart_bus_isa.c, then recompiling and installing in whatever way your configuration might demand seems to make the kernel detect the tablet as a UART. So it detected it, and the dev file was /dev/cuau4, for uart4, the WACF00E (it was ttyS4 under Linux). Great. X didn't detect it on its own, but that let me debug it using Minicom, which I promptly installed. After telling Minicom to use /dev/cuau4 as the modem, and telling it to use 38400 8N1, touches to the screen resulted in what can only be described as euphoric garbage, indicating that this ugly hack on top of hack alert worked. So I set up /usr/local/etc/X11/xorg.conf.d/wacom.conf to include (slightly amended from my actual setup, which only has ISDV4 in the stylus but still works for touch, haven't tested for stylus): Section "InputDevice" Identifier "wacom stylus" Driver "wacom" Option "Type" "stylus" Option "Device" "/dev/cuau4" Option "ForceDevice" "ISDV4" Option "AutoServerLayout" "true" EndSection Section "InputDevice" Identifier "wacom eraser" Driver "wacom" Option "Type" "eraser" Option "Device" "/dev/cuau4" Option "ForceDevice" "ISDV4" Option "AutoServerLayout" "true" EndSection Section "InputDevice" Identifier "wacom touch" Driver "wacom" Option "Type" "touch" Option "Touch" "on" Option "Device" "/dev/cuau4" Option "ForceDevice" "ISDV4" Option "AutoServerLayout" "true" EndSection Restarted X, and after % xsetwacom set "wacom touch" Touch on (I didn't initially have Touch on in the options list for "wacom touch") it was almost like striking platinum in a gold mine or something when the mouse just followed my finger the way I was used to it doing so under Linux. To those of you who say that FreeBSD will never be ready for the desktop, you're only right when you're talking to newbs. And this is living proof that if you know some C and you're intrepid enough, miracles really can happen. From owner-freebsd-hardware@freebsd.org Tue Feb 21 00:50:21 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2979CCE6F09 for ; Tue, 21 Feb 2017 00:50:21 +0000 (UTC) (envelope-from large.hadron.collider@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8190815F9 for ; Tue, 21 Feb 2017 00:50:20 +0000 (UTC) (envelope-from large.hadron.collider@gmx.com) Received: from [192.168.0.12] ([50.69.17.158]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0LrNE4-1cEQnG197U-0137rF for ; Tue, 21 Feb 2017 01:50:18 +0100 To: freebsd-hardware@freebsd.org From: Large Hadron Collider Subject: ... re: previous message, hopefully that wasn't off-topic. Message-ID: Date: Mon, 20 Feb 2017 16:50:16 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:5kQvrphmQqKnujzGlhoUkTR62T3mX1TLtsGy9ocs6Tkuuai0R6R kHVpuZ429iZVVKCm2/6WYFR4jq/SihIIMliILmZ082JN92pUYFL2RVSKbh+KzQNLW25n9CW x2QTFaa1Pvz6z2uUx+iypuwCHt9NO1Rz4tp6mxhfw35+PxFdXXYFmNh7X66DBulZr8Jg7GC cHdJh9Lb3S115y7q+jGtQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:beuTAoMSj6I=:7366hf++Wb9maHRbjnsY4J DNjqvImUWlmWK4AGi9wsvIMJgAgthg0eOxbzoJjdNNZ8JVnOeCq/DhoIU1NemjcSgSSZhpYsc nXvFN794/yXde2RcVxJC4n7wnaxfIWbu399zS8SjdqmftsyAYc5Mo5AVBhe8t0TpwkKNUGkCU V7aNftBZ10uhWkWadqbm1TacAuFF6xr2F+rFUHlmParbMXqBabIkm6KMpYL4Bu255HMgBK4Qp 2tyfXb7Op15U1l7f5hknfPJi+VFNehp9geVylaaUGGj7fnX0NlVvd9PBYWmUBybdF9ajmUIT9 h4VscgSmJHGDoJuyA4TD3cqa2wBHCXRjbvxKKw4+hPTTqeP3FIb8J/kDuXaUovdREqGY3PVoV 7kNS2M0/+G+5S8kZnMZKP6vZKvM1uvbJPAMG+YqK3EFvw7d+lcSENGTkblo3lkXLyy0ii4i1O m7ccYuOdPA== X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 00:50:21 -0000 I figured, it's a hardware-related post, and this is the hardware list. From owner-freebsd-hardware@freebsd.org Wed Feb 22 21:11:20 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21D6FCE97AF for ; Wed, 22 Feb 2017 21:11:20 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFE3117A1 for ; Wed, 22 Feb 2017 21:11:19 +0000 (UTC) (envelope-from isoa@kapsi.fi) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=ezuEatDh96sEPlLnSRLwFQF2jXIaTjx9oeISYQja43s=; b=s9PTewgxdh65/3Cx234hRrCoqW1EyHT8BR7JbQpz1qBn0XrGH58KMB/eQ+c3oIZOwOrGBDRYJY43GncHO+wXS+l2H5l2ozBwWzZDbySk1WDvDKtbVqaHYzfMS24LpLjiZiLI5ouU1GHIOpue2A6gKExDkO0SOj4YvLWBZXwT45sZOmWkS05D2bL7ul/Bcg8Ozb54CLViNlrCJNndJsR8iUhP9341ZVbOdH2/8rMeMER0fz1o7GnPEADTrIlaO59VD30/ubNAF2HiNLEY+iBRrRPxnzTwP9RN0iD5pjV03ZFRYSs9MBdhvV7VUCG09yzANvcHbN1I5v3wmcQ8+56tEg==; Received: from dsl-jklbrasgw1-54fb0c-179.dhcp.inet.fi ([84.251.12.179] helo=[192.168.255.112]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cgeBw-00066c-IK for freebsd-hardware@freebsd.org; Wed, 22 Feb 2017 23:11:16 +0200 Subject: Re: In which a touchscreen is rehabilitated, or: How I learned to stop being scared and just hack at /usr/src/sys/dev To: freebsd-hardware@freebsd.org References: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> From: Arto Pekkanen Message-ID: <6503fcce-fa54-e449-d158-f77323bebfcb@kapsi.fi> Date: Wed, 22 Feb 2017 23:11:12 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jV12FLkip2oIbpc3ulPBgNGf45hCKsH4w" X-SA-Exim-Connect-IP: 84.251.12.179 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 21:11:20 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jV12FLkip2oIbpc3ulPBgNGf45hCKsH4w Content-Type: multipart/mixed; boundary="S7bCitMox3tUDSxh0bSr0h7IPI7B5H1Xh"; protected-headers="v1" From: Arto Pekkanen To: freebsd-hardware@freebsd.org Message-ID: <6503fcce-fa54-e449-d158-f77323bebfcb@kapsi.fi> Subject: Re: In which a touchscreen is rehabilitated, or: How I learned to stop being scared and just hack at /usr/src/sys/dev References: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> In-Reply-To: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> --S7bCitMox3tUDSxh0bSr0h7IPI7B5H1Xh Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Please contribute your patch and get it approved and MFC'd by maintainers so that other people who are not knowledgeable enough can have the thing working without having to figure out how to hack and patch the kernel. Thanks. On 21.2.2017 2:49, Large Hadron Collider wrote: > (Apologies if this doesn't line break at 79 chars - full formatting in > HTML but this may be lost - shouldn't lose any info though) >=20 > Good day subscribers to this list. >=20 > I'm here with what could be described as a success story and a patch in= > the same e-mail. >=20 > Please do stop me if WACF00E has already been slated for the next major= > release - but I would like to share how I got my HP Elitebook 2760p's > touchscreen working. >=20 > So I, a former and now again user of FreeBSD (I got hacked the first > time... silly Ellie shouldn't give shells to strangers, should she now?= ) > have a laptop whose screen is touch-capable, and whose touchscreen > subsystem is based on a serial Wacom tablet. >=20 > It worked under Linux and too I presume Windows (with which the laptop > shipped), but not FreeBSD. I thought, what was going on? What was I > doing wrong? So after some poking around I discovered that the screen i= s > a WACF00E - not supported in 11.0-RELEASE-p1 by the driver that handles= > the UART. >=20 > It showed >=20 > unknown pnpinfo _HID=3DWACF00E _UID=3D0 at handle=3D\_SB_.PCI0.LPCB= =2ESIO_.DIGI >=20 > as the devinfo line. >=20 > Intriguingly, there was this line in uart_bus_acpi.c:static struct > isa_pnp_id acpi_ns8250_ids[]: >=20 > {0x04f0235c, "Wacom Tablet PC Screen"}, /* WACF004 */ >=20 > So I thought what the hell, I'd copy that line under itself and change > 04f0 (which is byte-swapped, counterintuitively) to 0ef0, representing > WACF00E. >=20 > Adding this: >=20 > {0x0ef0235c, "Wacom Tablet PC Screen 00e"}, /* WACF00e */ >=20 > to uart_bus_acpi.c and this: >=20 > {0x0ef0235c, NULL}, /* WACF004 - Wacom Tablet PC Screen*/ >=20 > (Yes it should read WACF00E in the comment) under the WACF004 entry in > uart_bus_isa.c, then recompiling and installing in whatever way your > configuration might demand seems to make the kernel detect the tablet a= s > a UART. >=20 > So it detected it, and the dev file was /dev/cuau4, for uart4, the > WACF00E (it was ttyS4 under Linux). >=20 > Great. X didn't detect it on its own, but that let me debug it using > Minicom, which I promptly installed. >=20 > After telling Minicom to use /dev/cuau4 as the modem, and telling it to= > use 38400 8N1, touches to the screen resulted in what can only be > described as euphoric garbage, indicating that this ugly hack on top of= > hack alert worked. >=20 > So I set up /usr/local/etc/X11/xorg.conf.d/wacom.conf to include > (slightly amended from my actual setup, which only has ISDV4 in the > stylus but still works for touch, haven't tested for stylus): >=20 > Section "InputDevice" > Identifier "wacom stylus" > Driver "wacom" > Option "Type" "stylus" > Option "Device" "/dev/cuau4" > Option "ForceDevice" "ISDV4" > Option "AutoServerLayout" "true" > EndSection >=20 > Section "InputDevice" > Identifier "wacom eraser" > Driver "wacom" > Option "Type" "eraser" > Option "Device" "/dev/cuau4" > Option "ForceDevice" "ISDV4" > Option "AutoServerLayout" "true" > EndSection >=20 > Section "InputDevice" > Identifier "wacom touch" > Driver "wacom" > Option "Type" "touch" > Option "Touch" "on" > Option "Device" "/dev/cuau4" > Option "ForceDevice" "ISDV4" > Option "AutoServerLayout" "true" > EndSection >=20 > Restarted X, and after >=20 > % xsetwacom set "wacom touch" Touch on >=20 > (I didn't initially have Touch on in the options list for "wacom touch"= ) > it was almost like striking platinum in a gold mine or something when > the mouse just followed my finger the way I was used to it doing so > under Linux. >=20 > To those of you who say that FreeBSD will never be ready for the > desktop, you're only right when you're talking to newbs. And this is > living proof that if you know some C and you're intrepid enough, > miracles really can happen. >=20 > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.= org" --=20 Arto Pekkanen --S7bCitMox3tUDSxh0bSr0h7IPI7B5H1Xh-- --jV12FLkip2oIbpc3ulPBgNGf45hCKsH4w Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlit/nIACgkQTBivhqtJa25CfgD/XvGMsxkzwu+Jpnyhaty/Dqun GERFgljRixdF0rl25zkA/2ZTv0IEgU0t6RKRSob/z+Q6bRmDoRIjUWFd4iLtcmF0 =J09D -----END PGP SIGNATURE----- --jV12FLkip2oIbpc3ulPBgNGf45hCKsH4w-- From owner-freebsd-hardware@freebsd.org Thu Feb 23 00:13:58 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E984CEAC9E for ; Thu, 23 Feb 2017 00:13:58 +0000 (UTC) (envelope-from large.hadron.collider@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95698FE7 for ; Thu, 23 Feb 2017 00:13:57 +0000 (UTC) (envelope-from large.hadron.collider@gmx.com) Received: from [192.168.0.12] ([50.69.17.158]) by mail.gmx.com (mrgmx002 [212.227.17.184]) with ESMTPSA (Nemesis) id 0Lt1S6-1cDi5Y3toA-012ZF8 for ; Thu, 23 Feb 2017 01:08:43 +0100 From: Large Hadron Collider Subject: (accidentally unicasted) Re: In which a touchscreen is rehabilitated, or: How I learned to stop being scared and just hack at /usr/src/sys/dev To: freebsd-hardware@freebsd.org References: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> <6503fcce-fa54-e449-d158-f77323bebfcb@kapsi.fi> Message-ID: Date: Wed, 22 Feb 2017 16:08:41 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <6503fcce-fa54-e449-d158-f77323bebfcb@kapsi.fi> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:UnG00i/z6z0ZWodXxPsMe+YcNhkltFzjsUJpksO8s8Bsj7/3vJP WWKBqJNxvIMXk2xe1TtyIhGgcdCx/JWGnPEMB83n9mTpwGHDvyEwVgtT72bCMZprQAqw1uW 6b5ehnpBnQW7INXJDsjYui+63W+9c/PhZB8S6pfad425D5zTL5xYn7Yqdds9ZTjKpCXLskd g+ZA+go+/LFirNNw6C6tw== X-UI-Out-Filterresults: notjunk:1;V01:K0:hPBjTsUEcCA=:S9sicsW9CvWnV8W3uFqt7l SdhSSJ7jybCWKt3M4e6vN2Vh+GAurDrtcDUhS3hIsl6EbGjBDLFbprHSTjlozP+JoztFsYEAA sDLiOD89BxMhP0BbRx3LQtjtjCzr/Ptja0oRaqUWb5NJgz0+JAaOpHjAnns4wa+wt+LR65mgS Ux8ZurI6Q4kxVe73mzbNdTWEZwotTm4nc6P2zt9v3jjhzGCS4gYweFbNS0CtvTusSDSYxi3vM 1LTmHGmsg9/6IRz88ZjbAXI03JDmO/iAG/lSxxVHSlTfyY606mfAgK++n65tD+H6Rapbggb+u UfYEBOgFRScE1vg3tEAZGv7GoknE3WOUytp+BLJ1TerFPnVIA4wA5u9Cr2h8XNrq2LoZyApy0 kAtdEGNCsAsl1MO5XT+BUU+wUxlmxGt1rQyiacNgrsIYzJe1xmAGfzLsSbyZPifX0w/7LY/Qj 2a4uOfXztg== X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 00:13:58 -0000 Hey, sorry to piss you off but I do not know how to do this. On 22/02/2017 13:11, Arto Pekkanen wrote: > Please contribute your patch and get it approved and MFC'd by > maintainers so that other people who are not knowledgeable enough can > have the thing working without having to figure out how to hack and > patch the kernel. Thanks. > > On 21.2.2017 2:49, Large Hadron Collider wrote: >> (Apologies if this doesn't line break at 79 chars - full formatting in >> HTML but this may be lost - shouldn't lose any info though) >> >> Good day subscribers to this list. >> >> I'm here with what could be described as a success story and a patch in >> the same e-mail. >> >> Please do stop me if WACF00E has already been slated for the next major >> release - but I would like to share how I got my HP Elitebook 2760p's >> touchscreen working. >> >> So I, a former and now again user of FreeBSD (I got hacked the first >> time... silly Ellie shouldn't give shells to strangers, should she now?) >> have a laptop whose screen is touch-capable, and whose touchscreen >> subsystem is based on a serial Wacom tablet. >> >> It worked under Linux and too I presume Windows (with which the laptop >> shipped), but not FreeBSD. I thought, what was going on? What was I >> doing wrong? So after some poking around I discovered that the screen is >> a WACF00E - not supported in 11.0-RELEASE-p1 by the driver that handles >> the UART. >> >> It showed >> >> unknown pnpinfo _HID=WACF00E _UID=0 at handle=\_SB_.PCI0.LPCB.SIO_.DIGI >> >> as the devinfo line. >> >> Intriguingly, there was this line in uart_bus_acpi.c:static struct >> isa_pnp_id acpi_ns8250_ids[]: >> >> {0x04f0235c, "Wacom Tablet PC Screen"}, /* WACF004 */ >> >> So I thought what the hell, I'd copy that line under itself and change >> 04f0 (which is byte-swapped, counterintuitively) to 0ef0, representing >> WACF00E. >> >> Adding this: >> >> {0x0ef0235c, "Wacom Tablet PC Screen 00e"}, /* WACF00e */ >> >> to uart_bus_acpi.c and this: >> >> {0x0ef0235c, NULL}, /* WACF004 - Wacom Tablet PC Screen*/ >> >> (Yes it should read WACF00E in the comment) under the WACF004 entry in >> uart_bus_isa.c, then recompiling and installing in whatever way your >> configuration might demand seems to make the kernel detect the tablet as >> a UART. >> >> So it detected it, and the dev file was /dev/cuau4, for uart4, the >> WACF00E (it was ttyS4 under Linux). >> >> Great. X didn't detect it on its own, but that let me debug it using >> Minicom, which I promptly installed. >> >> After telling Minicom to use /dev/cuau4 as the modem, and telling it to >> use 38400 8N1, touches to the screen resulted in what can only be >> described as euphoric garbage, indicating that this ugly hack on top of >> hack alert worked. >> >> So I set up /usr/local/etc/X11/xorg.conf.d/wacom.conf to include >> (slightly amended from my actual setup, which only has ISDV4 in the >> stylus but still works for touch, haven't tested for stylus): >> >> Section "InputDevice" >> Identifier "wacom stylus" >> Driver "wacom" >> Option "Type" "stylus" >> Option "Device" "/dev/cuau4" >> Option "ForceDevice" "ISDV4" >> Option "AutoServerLayout" "true" >> EndSection >> >> Section "InputDevice" >> Identifier "wacom eraser" >> Driver "wacom" >> Option "Type" "eraser" >> Option "Device" "/dev/cuau4" >> Option "ForceDevice" "ISDV4" >> Option "AutoServerLayout" "true" >> EndSection >> >> Section "InputDevice" >> Identifier "wacom touch" >> Driver "wacom" >> Option "Type" "touch" >> Option "Touch" "on" >> Option "Device" "/dev/cuau4" >> Option "ForceDevice" "ISDV4" >> Option "AutoServerLayout" "true" >> EndSection >> >> Restarted X, and after >> >> % xsetwacom set "wacom touch" Touch on >> >> (I didn't initially have Touch on in the options list for "wacom touch") >> it was almost like striking platinum in a gold mine or something when >> the mouse just followed my finger the way I was used to it doing so >> under Linux. >> >> To those of you who say that FreeBSD will never be ready for the >> desktop, you're only right when you're talking to newbs. And this is >> living proof that if you know some C and you're intrepid enough, >> miracles really can happen. >> >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@freebsd.org Thu Feb 23 00:48:47 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56153CE7323 for ; Thu, 23 Feb 2017 00:48:47 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00FC51C91 for ; Thu, 23 Feb 2017 00:48:46 +0000 (UTC) (envelope-from isoa@kapsi.fi) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=+zwf7WNQCgoUONP119S+9XwaoKdnvZ1QhKvk2nHgR7Y=; b=KT4QLmw89xjVaBAuggUWCkmNZ+D0F7tVXfmHitnu6x45PEV/QWsriaqSk0wLEoU9ofhUia7EBs1OTRgY9+XkNuFnuGwpfdqWLDowV48FrzakuUznr0d6Y8jkKMl6VbFqiXGzxlsVMjdHR3GyKfEk9g1RpulOB6JxqPxlt0BLgeNaBtjJnE7bPXMAkKHyhv6VMcy4Iryikj8kK4aRu2WlSPL0rHGgqAyGMe6M7QkFHXFVskCVpPgoQ9fo7hJDPvmF9oOjv3Zhxv9nBnijVtgNpO6klk9m3w0Ua7foCn32SW+m0OGAsjOVEzCg8Zdtx5geprdjN3V+hipnrxayVwURKg==; Received: from dsl-jklbrasgw1-54fb0c-179.dhcp.inet.fi ([84.251.12.179] helo=[192.168.255.112]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cghaM-00022c-I3 for freebsd-hardware@freebsd.org; Thu, 23 Feb 2017 02:48:42 +0200 Subject: Re: (accidentally unicasted) Re: In which a touchscreen is rehabilitated, or: How I learned to stop being scared and just hack at /usr/src/sys/dev To: freebsd-hardware@freebsd.org References: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> <6503fcce-fa54-e449-d158-f77323bebfcb@kapsi.fi> From: Arto Pekkanen Message-ID: Date: Thu, 23 Feb 2017 02:48:28 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3BtGTLBta5xMA6iaKoHafhn2gaqHoDegA" X-SA-Exim-Connect-IP: 84.251.12.179 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 00:48:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3BtGTLBta5xMA6iaKoHafhn2gaqHoDegA Content-Type: multipart/mixed; boundary="d21XJW5UFOXamRvqIKiaA5Db8vVlsVlX4"; protected-headers="v1" From: Arto Pekkanen To: freebsd-hardware@freebsd.org Message-ID: Subject: Re: (accidentally unicasted) Re: In which a touchscreen is rehabilitated, or: How I learned to stop being scared and just hack at /usr/src/sys/dev References: <0c7ad294-86f0-a076-f337-83e17d58fdd0@gmx.com> <6503fcce-fa54-e449-d158-f77323bebfcb@kapsi.fi> In-Reply-To: --d21XJW5UFOXamRvqIKiaA5Db8vVlsVlX4 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I was just being direct in regards to having a new feature contributed, instead of it drowning into the noise of a mailing list, which tends to happen too often. Especially support for new devices are needed. As for getting the patch approved and MFC'd, read this first: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/contrib= -how.html A direct quote from above: "Once you have a set of diffs (which you may test with the patch(1) command), you should submit them for inclusion with FreeBSD as a bug report." To learn how to report a bug report: https://www.freebsd.org/support/bugreports.html A web based platform is used to submit and track the problem report. This is better for the maintainers than using mailing lists. Thanks. On 23.2.2017 2:08, Large Hadron Collider wrote: > Hey, sorry to piss you off but I do not know how to do this. >=20 >=20 > On 22/02/2017 13:11, Arto Pekkanen wrote: >> Please contribute your patch and get it approved and MFC'd by >> maintainers so that other people who are not knowledgeable enough can >> have the thing working without having to figure out how to hack and >> patch the kernel. Thanks. >> >> On 21.2.2017 2:49, Large Hadron Collider wrote: >>> (Apologies if this doesn't line break at 79 chars - full formatting i= n >>> HTML but this may be lost - shouldn't lose any info though) >>> >>> Good day subscribers to this list. >>> >>> I'm here with what could be described as a success story and a patch = in >>> the same e-mail. >>> >>> Please do stop me if WACF00E has already been slated for the next maj= or >>> release - but I would like to share how I got my HP Elitebook 2760p's= >>> touchscreen working. >>> >>> So I, a former and now again user of FreeBSD (I got hacked the first >>> time... silly Ellie shouldn't give shells to strangers, should she no= w?) >>> have a laptop whose screen is touch-capable, and whose touchscreen >>> subsystem is based on a serial Wacom tablet. >>> >>> It worked under Linux and too I presume Windows (with which the lapto= p >>> shipped), but not FreeBSD. I thought, what was going on? What was I >>> doing wrong? So after some poking around I discovered that the screen= is >>> a WACF00E - not supported in 11.0-RELEASE-p1 by the driver that handl= es >>> the UART. >>> >>> It showed >>> >>> unknown pnpinfo _HID=3DWACF00E _UID=3D0 at >>> handle=3D\_SB_.PCI0.LPCB.SIO_.DIGI >>> >>> as the devinfo line. >>> >>> Intriguingly, there was this line in uart_bus_acpi.c:static struct >>> isa_pnp_id acpi_ns8250_ids[]: >>> >>> {0x04f0235c, "Wacom Tablet PC Screen"}, /* WACF004 */ >>> >>> So I thought what the hell, I'd copy that line under itself and chang= e >>> 04f0 (which is byte-swapped, counterintuitively) to 0ef0, representin= g >>> WACF00E. >>> >>> Adding this: >>> >>> {0x0ef0235c, "Wacom Tablet PC Screen 00e"}, /* WACF00e */ >>> >>> to uart_bus_acpi.c and this: >>> >>> {0x0ef0235c, NULL}, /* WACF004 - Wacom Tablet PC Screen*/ >>> >>> (Yes it should read WACF00E in the comment) under the WACF004 entry i= n >>> uart_bus_isa.c, then recompiling and installing in whatever way your >>> configuration might demand seems to make the kernel detect the tablet= as >>> a UART. >>> >>> So it detected it, and the dev file was /dev/cuau4, for uart4, the >>> WACF00E (it was ttyS4 under Linux). >>> >>> Great. X didn't detect it on its own, but that let me debug it using >>> Minicom, which I promptly installed. >>> >>> After telling Minicom to use /dev/cuau4 as the modem, and telling it = to >>> use 38400 8N1, touches to the screen resulted in what can only be >>> described as euphoric garbage, indicating that this ugly hack on top = of >>> hack alert worked. >>> >>> So I set up /usr/local/etc/X11/xorg.conf.d/wacom.conf to include >>> (slightly amended from my actual setup, which only has ISDV4 in the >>> stylus but still works for touch, haven't tested for stylus): >>> >>> Section "InputDevice" >>> Identifier "wacom stylus" >>> Driver "wacom" >>> Option "Type" "stylus" >>> Option "Device" "/dev/cuau4" >>> Option "ForceDevice" "ISDV4" >>> Option "AutoServerLayout" "true" >>> EndSection >>> >>> Section "InputDevice" >>> Identifier "wacom eraser" >>> Driver "wacom" >>> Option "Type" "eraser" >>> Option "Device" "/dev/cuau4" >>> Option "ForceDevice" "ISDV4" >>> Option "AutoServerLayout" "true" >>> EndSection >>> >>> Section "InputDevice" >>> Identifier "wacom touch" >>> Driver "wacom" >>> Option "Type" "touch" >>> Option "Touch" "on" >>> Option "Device" "/dev/cuau4" >>> Option "ForceDevice" "ISDV4" >>> Option "AutoServerLayout" "true" >>> EndSection >>> >>> Restarted X, and after >>> >>> % xsetwacom set "wacom touch" Touch on >>> >>> (I didn't initially have Touch on in the options list for "wacom touc= h") >>> it was almost like striking platinum in a gold mine or something when= >>> the mouse just followed my finger the way I was used to it doing so >>> under Linux. >>> >>> To those of you who say that FreeBSD will never be ready for the >>> desktop, you're only right when you're talking to newbs. And this is >>> living proof that if you know some C and you're intrepid enough, >>> miracles really can happen. >>> >>> _______________________________________________ >>> freebsd-hardware@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>> To unsubscribe, send any mail to >>> "freebsd-hardware-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.= org" --=20 Arto Pekkanen --d21XJW5UFOXamRvqIKiaA5Db8vVlsVlX4-- --3BtGTLBta5xMA6iaKoHafhn2gaqHoDegA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliuMWgACgkQTBivhqtJa25VawD+JEfT8v7rD1vdjQakGxoUoAux c9M0dFnhc/J4TQoavc4BAIxCPwvrt37uVFQFLxQFhrgDtCmG/ANPIe6nhLc63TgL =e1Uf -----END PGP SIGNATURE----- --3BtGTLBta5xMA6iaKoHafhn2gaqHoDegA-- From owner-freebsd-hardware@freebsd.org Thu Feb 23 01:12:13 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41A99CE7BDC for ; Thu, 23 Feb 2017 01:12:13 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F00B0C8E for ; Thu, 23 Feb 2017 01:12:12 +0000 (UTC) (envelope-from isoa@kapsi.fi) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=26mj8a2rm3eK780+gdf2zqAWN6iGOlbRp2BddOKlIuA=; b=lNZw978pLP4lQbZ7K/KJguATjxkUaHiyW9lfplGrrropVRgTHYKuPUpvLa4LUFdwxCHuybkfnWv1uoxx58/9oDWQbuuQ62hWUWQvvRvUpDxxpe2Zi0Zv876bfbraRRdPei3QmCsGnzFMGnnNlbFxZ5kSG1pZJxGFFqZqrb1HSPwTe2og02F4FXYrnrDtdyFWLFw2gUMyY6apNJNVYj7IalvXboUIy2Uoe1foxZP0nAHkRn1aYLEpjgXJi1SiuRh2llexGFiyegkhqirIz8iuQuKFlVpoNXrkvirZxTU5SahdvSqwvBl8TlEnlo+mlspFRQaixbvJ5qKQrjowbYPjfA==; Received: from dsl-jklbrasgw1-54fb0c-179.dhcp.inet.fi ([84.251.12.179] helo=[192.168.255.112]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cghx5-0007Ab-6h for freebsd-hardware@freebsd.org; Thu, 23 Feb 2017 03:12:11 +0200 Subject: Re: Intel WiFi AC 7620 To: freebsd-hardware@freebsd.org References: <410c39fee559b8e691b09f4fe4069bf6@cs.wisc.edu> From: Arto Pekkanen Message-ID: Date: Thu, 23 Feb 2017 03:12:06 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <410c39fee559b8e691b09f4fe4069bf6@cs.wisc.edu> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dMcAanew4FPRgEjMcfG182RGENPPGliXQ" X-SA-Exim-Connect-IP: 84.251.12.179 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 01:12:13 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dMcAanew4FPRgEjMcfG182RGENPPGliXQ Content-Type: multipart/mixed; boundary="52A0kviWOCPG1HS2uWkrH4qs6umaeqd9s"; protected-headers="v1" From: Arto Pekkanen To: freebsd-hardware@freebsd.org Message-ID: Subject: Re: Intel WiFi AC 7620 References: <410c39fee559b8e691b09f4fe4069bf6@cs.wisc.edu> In-Reply-To: <410c39fee559b8e691b09f4fe4069bf6@cs.wisc.edu> --52A0kviWOCPG1HS2uWkrH4qs6umaeqd9s Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Have you checked the release notes for FreeBSD 11? That often contains information if support has been added for a specific piece of hardware. On 1.2.2017 20:09, roger wrote: > I've read online in some forums that the 7620 WiFi chipset from Intel i= s > supported now in the FreeBSD 11. Is this true? >=20 > roger > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.= org" --=20 Arto Pekkanen --52A0kviWOCPG1HS2uWkrH4qs6umaeqd9s-- --dMcAanew4FPRgEjMcfG182RGENPPGliXQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliuNukACgkQTBivhqtJa25thAD/SYRadKYAlNqxpouTPmPSmMRU LDyXGnAWF9XhxXtSfbQBALQhQD5C5gvUcYdCd8RTuqRE9hC1pUWN+MaevLIou4Y/ =aO6l -----END PGP SIGNATURE----- --dMcAanew4FPRgEjMcfG182RGENPPGliXQ--