From owner-freebsd-arm@freebsd.org Sun Mar 25 07:16:02 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D2BBF4FE55 for ; Sun, 25 Mar 2018 07:16:02 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CFE5B780D2 for ; Sun, 25 Mar 2018 07:16:01 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w2P6qEYf023386 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 24 Mar 2018 23:52:14 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w2P6qER2023385; Sat, 24 Mar 2018 23:52:14 -0700 (PDT) (envelope-from jmg) Date: Sat, 24 Mar 2018 23:52:14 -0700 From: John-Mark Gurney To: Udit agarwal Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD bootup freeze when running it on BeagleBone Black Message-ID: <20180325065214.GP75576@funkthat.com> Mail-Followup-To: Udit agarwal , freebsd-arm@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sat, 24 Mar 2018 23:52:15 -0700 (PDT) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 07:16:02 -0000 Udit agarwal wrote this message on Sun, Mar 18, 2018 at 16:19 +0530: > I am trying to build FreeBSD 12.0 on BeagleBone Black. However, during > kernel initialization it's getting freeze. I took the image from here > > .Here's the error log: Just a heads up, I'm getting the same thing, I also ran all three latest snapshots and seeing similar behavior: FreeBSD 12.0-CURRENT #0 r330034: Mon Feb 26 23:44:48 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm [...] cpswss0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a1007ff,0x4a101200-0x4a1012ff irq 38,39,40,41 on simplebus0 cpswss0: CPSW SS Version 1.12 (0) cpswss0: Initial queue size TX=128 RX=384 cpswss0: Unable to fill RX queue cpsw0: on cpswss0 miibus0: on cpsw0 smscphy0: PHY 0 on miibus0 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cpsw0: Ethernet address: xx:xx:xx:xx:xx:xx cryptosoft0: usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 and: FreeBSD 12.0-CURRENT #0 r330606: Wed Mar 7 19:26:58 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm [...] cpswss0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a1007ff,0x4a101200-0x4a1012ff irq 38,39,40,41 on simplebus0 cpswss0: CPSW SS Version 1.12 (0) cpswss0: Initial queue size TX=128 RX=384 cpswss0: Unable to fill RX queue cpsw0: on cpswss0 and: FreeBSD 12.0-CURRENT #0 r331001: Thu Mar 15 18:47:28 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm [...] cpswss0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a1007ff,0x4a101200-0x4a1012ff irq 38,39,40,41 on simplebus0 cpswss0: CPSW SS Version 1.12 (0) cpswss0: Initial queue size TX=128 RX=384 cpswss0: Unable to fill RX queue cpsw0: on cpswss0 So, it looks like Feb 26th got a bit farther, but it still hung. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@freebsd.org Sun Mar 25 21:00:37 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4F50F6CC32 for ; Sun, 25 Mar 2018 21:00:36 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85C5C7806C for ; Sun, 25 Mar 2018 21:00:36 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id AA6B514B2C for ; Sun, 25 Mar 2018 21:00:35 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2PL0Z4N063463 for ; Sun, 25 Mar 2018 21:00:35 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2PL0ZTx063451 for freebsd-arm@FreeBSD.org; Sun, 25 Mar 2018 21:00:35 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201803252100.w2PL0ZTx063451@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 25 Mar 2018 21:00:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 21:00:37 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 220297 | arch(7) rename arm64 to aarch64 respecting `uname 1 problems total for which you should take action. From owner-freebsd-arm@freebsd.org Sun Mar 25 23:19:30 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D36CEF5125D for ; Sun, 25 Mar 2018 23:19:30 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic310-15.consmr.mail.bf2.yahoo.com (sonic310-15.consmr.mail.bf2.yahoo.com [74.6.135.125]) (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 685DF7EBAA for ; Sun, 25 Mar 2018 23:19:30 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: 42AyFwwVM1n5mxJ7cSRhFcv67GnI0L.cr2jA0zbd6C2jaWxYB7GZHy3yt3ks0dN GR7MLeJf5GKFxPDqoERyCC1YHFjkraZdMCgyabhFH1gzUYrsbdnk5Bjo.nh.GNyHog9Q2Xj9c2q_ 2hQH3pVCEsJDAGb_4FdZlI4_lP72xjSZDXKNm2d.58ELyQC_vgfTFQD3HmRt00b7hAprlNd.ZlLa 0y5vYVc4UDrByTpK2jpZFpjsoqRGqBDt3sdfEJFW.w8svYPFaLwu6ceM.OsJX.iSc4csKZt5kUan Uu2Qx9pLGrrAyY7.EUyQwuAssvG83FGLVDGWuFSp3EzTy8M4jPpcEfdNtF15t.1BZ53PjDkvLTzo thPVdnDAaQ86vmpNft_zFPzDk1Vn6.oOTV9G53.h.RbpzWaYubGrXxrTnRZ6cBcHBpiKirlBVLb4 Ie.vHCGvT.XPWyNblmRIiCyRwcowMWPdL.M.t8oE9ifsGpPmB8Ud2NBl.RWFrMs6eBYJeTfwK6Vn dMXcUPDfKXljtZKo578IEQqXbrCJSLndYYB5B Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.bf2.yahoo.com with HTTP; Sun, 25 Mar 2018 23:19:22 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp420.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID fb5803c1b483f2c7f72354c01f96aa91; Sun, 25 Mar 2018 23:19:20 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: aarch64-none-elf-gcc V6.3.0_2 from -r465491 fails to package because of 3 referenced-but-missing include-fixed files (amd64 context) Message-Id: <0C5C8C85-7569-4B64-895E-ABA0C4FAA3B3@yahoo.com> Date: Sun, 25 Mar 2018 16:19:18 -0700 To: freebsd-ports@freebsd.org, "freebsd-toolchain@FreeBSD.org" , freebsd-arm@FreeBSD.org X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 23:19:31 -0000 # svnlite info /usr/ports/ | grep "^Re[plv]" Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 465491 via a poudrirere-devel bulk -a run: =3D=3D=3D> Building package for aarch64-none-elf-gcc-6.3.0_2 pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc= /aarch64-none-elf/6.3.0/include-fixed/README:No such file or directory pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc= /aarch64-none-elf/6.3.0/include-fixed/limits.h:No such file or directory pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc= /aarch64-none-elf/6.3.0/include-fixed/syslimits.h:No such file or = directory *** Error code 1 Context: # uname -apKU FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r331499M amd64 = amd64 1200060 1200060 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Sun Mar 25 23:20:51 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC4C6F51435; Sun, 25 Mar 2018 23:20:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36E957ECA2; Sun, 25 Mar 2018 23:20:50 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w2PNBW7a071046 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 26 Mar 2018 01:11:34 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1522019494; bh=CkEcqrfFasXZKWcV1EseexUvBaOvBehCul1rL4PO5Bg=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=3k1Rfx4QhznOVRPlD2+qr/knVbash3KH+Fc6DV7ai9vE23qt+qHATkoDF/dohKR9Z hUGmFL2HhO/uvpy93V54Zwk1KOFrM7T21xsb2Wd+TqjYt4xPR72SfKnrRh5U29VnNN jtAep3M4pn7meVjJrksjNPWd9WLfBMtP8yN3ByOA= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w2PNBTJ2028393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 26 Mar 2018 01:11:29 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w2PNBTeg016794 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Mar 2018 01:11:29 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w2PNBS6H016793; Mon, 26 Mar 2018 01:11:28 +0200 (CEST) (envelope-from ticso) Date: Mon, 26 Mar 2018 01:11:28 +0200 From: Bernd Walter To: Hans Petter Selasky Cc: Bernd Walter , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180325231128.GA16646@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308200849.GC86413@cicely7.cicely.de> <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> <20180309114025.GJ86413@cicely7.cicely.de> <20180309132539.GL86413@cicely7.cicely.de> <20180310000336.GM86413@cicely7.cicely.de> <20180312111246.GA14138@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180312111246.GA14138@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 23:20:51 -0000 On Mon, Mar 12, 2018 at 12:12:47PM +0100, Bernd Walter wrote: > On Sat, Mar 10, 2018 at 01:03:39AM +0100, Bernd Walter wrote: > > On Fri, Mar 09, 2018 at 02:25:39PM +0100, Bernd Walter wrote: > > So the older 7" HDMI C Rev 1.1 with the non IPS panel won't even attach, but > > it always needed some special binary support for Linux, no surprises here. > > The newer Rev 2.1 with the IPS panel claims to be the same and work with > > webcamd, at least I get data via /dev/input/event0, which looks reasonable > > with evdev-dump. > > That's an interesting starting point. > > I've got a new model of the 10" HDMI B. > It behaves differently. > First of all - uep seems to take it, which it didn't for any of > the previous displays I'd tested. > I had to remove the driver from the loader.conf to have webcamd attach to it. > webcamd attaches fine and it delivers touch events: > [29]sa# evdev-dump /dev/input/event0 > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_TRACKING_ID 0x00000000 > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_POSITION_X 0x000001CF > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_POSITION_Y 0x0000025E > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_PRESSURE 0x00000005 > /dev/input/event0 3041705595.425438 EV_KEY BTN_TOUCH 0x00000001 > /dev/input/event0 3041705595.425438 EV_ABS ABS_X 0x000001CF > /dev/input/event0 3041705595.425438 EV_ABS ABS_Y 0x0000025E > /dev/input/event0 3041705595.425438 EV_ABS ABS_PRESSURE 0x00000005 > /dev/input/event0 3041705595.425438 EV_SYN SYN_REPORT 0x00000000 > > Whatever had been the cause for my previous problem, they obviously > have fixed them in firmware. Unfortunately I still have some problems. [63]sa# evdev-dump /dev/input/event1 /dev/input/event1 3043946310.664423 EV_ABS ABS_MT_TRACKING_ID 0x0000003F /dev/input/event1 3043946310.664423 EV_ABS ABS_MT_POSITION_X 0x000001C9 /dev/input/event1 3043946310.664423 EV_ABS ABS_MT_POSITION_Y 0x00000112 /dev/input/event1 3043946310.664423 EV_KEY BTN_TOUCH 0x00000001 /dev/input/event1 3043946310.664423 EV_ABS ABS_X 0x000001C9 /dev/input/event1 3043946310.664423 EV_ABS ABS_Y 0x00000112 /dev/input/event1 3043946310.664423 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946310.784395 EV_ABS ABS_MT_TRACKING_ID 0xFFFFFFFF /dev/input/event1 3043946310.784395 EV_KEY BTN_TOUCH 0x00000000 /dev/input/event1 3043946310.784395 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946316.944324 EV_ABS ABS_MT_TRACKING_ID 0x00000040 /dev/input/event1 3043946316.944324 EV_ABS ABS_MT_POSITION_X 0x000001CE /dev/input/event1 3043946316.944324 EV_ABS ABS_MT_POSITION_Y 0x000000FE /dev/input/event1 3043946316.944324 EV_KEY BTN_TOUCH 0x00000001 /dev/input/event1 3043946316.944324 EV_ABS ABS_X 0x000001CE /dev/input/event1 3043946316.944324 EV_ABS ABS_Y 0x000000FE /dev/input/event1 3043946316.944324 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946317.004303 EV_ABS ABS_MT_TRACKING_ID 0xFFFFFFFF /dev/input/event1 3043946317.004303 EV_KEY BTN_TOUCH 0x00000000 /dev/input/event1 3043946317.004303 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946319.744283 EV_ABS ABS_MT_TRACKING_ID 0x00000041 /dev/input/event1 3043946319.744283 EV_ABS ABS_MT_POSITION_X 0x0000020E /dev/input/event1 3043946319.744283 EV_ABS ABS_MT_POSITION_Y 0x000000D8 /dev/input/event1 3043946319.744283 EV_KEY BTN_TOUCH 0x00000001 /dev/input/event1 3043946319.744283 EV_ABS ABS_X 0x0000020E /dev/input/event1 3043946319.744283 EV_ABS ABS_Y 0x000000D8 /dev/input/event1 3043946319.744283 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946319.864240 EV_ABS ABS_MT_TRACKING_ID 0xFFFFFFFF /dev/input/event1 3043946319.864240 EV_KEY BTN_TOUCH 0x00000000 /dev/input/event1 3043946319.864240 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946322.004229 EV_ABS ABS_MT_TRACKING_ID 0x00000042 /dev/input/event1 3043946322.004229 EV_ABS ABS_MT_POSITION_X 0x00000209 /dev/input/event1 3043946322.004229 EV_ABS ABS_MT_POSITION_Y 0x000000CD /dev/input/event1 3043946322.004229 EV_KEY BTN_TOUCH 0x00000001 /dev/input/event1 3043946322.004229 EV_ABS ABS_X 0x00000209 /dev/input/event1 3043946322.004229 EV_ABS ABS_Y 0x000000CD /dev/input/event1 3043946322.004229 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946325.454187 EV_ABS ABS_MT_POSITION_X 0x0000016A /dev/input/event1 3043946325.454187 EV_ABS ABS_MT_POSITION_Y 0x000000D2 /dev/input/event1 3043946325.454187 EV_ABS ABS_X 0x0000016A /dev/input/event1 3043946325.454187 EV_ABS ABS_Y 0x000000D2 /dev/input/event1 3043946325.454187 EV_SYN SYN_REPORT 0x00000000 /dev/input/event1 3043946325.574174 EV_ABS ABS_MT_POSITION_X 0x0000016B /dev/input/event1 3043946325.574174 EV_ABS ABS_X 0x0000016B /dev/input/event1 3043946325.574174 EV_SYN SYN_REPORT 0x00000000 All 5 blocks are a single touch, which means finger on screen for a short moment. On the first 3 I get position data and BTN_TOUCH 1 as well as BTN_TOUCH 0. But this is not consistent, sometime I get only a 1 and sometime only a 0. In the 5th block I even got neither. The timestamps on the first 3 cases mark it clearly when I removed the finger. I got a 1 on touch-start and a 0 on touch-end. On the 4th case I got a touch-start, but no touch-end. In the 5th case I only got positon updates. This is a 7" display - the 10" also delivers ABS_PRESSURE, but the problem is the same that I don't consistently get the EV_KEY events. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sun Mar 25 23:28:34 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC3DBF51E3A; Sun, 25 Mar 2018 23:28:34 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E1BA7F392; Sun, 25 Mar 2018 23:28:12 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w2PNS9Sw071354 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 26 Mar 2018 01:28:10 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1522020490; bh=VubS/0LaKOWVIVOL3Am5oA7IKyw1122woxh654WKtfI=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=l9peoG7O6Abz76QSXAYJE9hGrnrflZCAP56Y90Babss7Xz+2xcfUVzsFCz3Qaz/TM XxHx98/jQerOIGKDCPxZJ+YN36305L82iW372BFv48kYK+ibdHS5nQhXS1T39Tl//8 XinCckesSOk1BQY2WqYWrsolMdtU4+c2EaoG8M6o= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w2PNS6Fh028573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 26 Mar 2018 01:28:06 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w2PNS6iq016877 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Mar 2018 01:28:06 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w2PNS6V1016876; Mon, 26 Mar 2018 01:28:06 +0200 (CEST) (envelope-from ticso) Date: Mon, 26 Mar 2018 01:28:06 +0200 From: Bernd Walter To: Hans Petter Selasky Cc: Bernd Walter , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180325232806.GB16646@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180308210805.GE86413@cicely7.cicely.de> <20180309004433.GI86413@cicely7.cicely.de> <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> <20180309114025.GJ86413@cicely7.cicely.de> <20180309132539.GL86413@cicely7.cicely.de> <20180310000336.GM86413@cicely7.cicely.de> <20180312111246.GA14138@cicely7.cicely.de> <20180325231128.GA16646@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180325231128.GA16646@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 23:28:35 -0000 On Mon, Mar 26, 2018 at 01:11:28AM +0200, Bernd Walter wrote: > On Mon, Mar 12, 2018 at 12:12:47PM +0100, Bernd Walter wrote: > > On Sat, Mar 10, 2018 at 01:03:39AM +0100, Bernd Walter wrote: > > > On Fri, Mar 09, 2018 at 02:25:39PM +0100, Bernd Walter wrote: > > > So the older 7" HDMI C Rev 1.1 with the non IPS panel won't even attach, but > > > it always needed some special binary support for Linux, no surprises here. > > > The newer Rev 2.1 with the IPS panel claims to be the same and work with > > > webcamd, at least I get data via /dev/input/event0, which looks reasonable > > > with evdev-dump. > > > That's an interesting starting point. > > > > I've got a new model of the 10" HDMI B. > > It behaves differently. > > First of all - uep seems to take it, which it didn't for any of > > the previous displays I'd tested. > > I had to remove the driver from the loader.conf to have webcamd attach to it. > > webcamd attaches fine and it delivers touch events: > > [29]sa# evdev-dump /dev/input/event0 > > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_TRACKING_ID 0x00000000 > > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_POSITION_X 0x000001CF > > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_POSITION_Y 0x0000025E > > /dev/input/event0 3041705595.425438 EV_ABS ABS_MT_PRESSURE 0x00000005 > > /dev/input/event0 3041705595.425438 EV_KEY BTN_TOUCH 0x00000001 > > /dev/input/event0 3041705595.425438 EV_ABS ABS_X 0x000001CF > > /dev/input/event0 3041705595.425438 EV_ABS ABS_Y 0x0000025E > > /dev/input/event0 3041705595.425438 EV_ABS ABS_PRESSURE 0x00000005 > > /dev/input/event0 3041705595.425438 EV_SYN SYN_REPORT 0x00000000 > > > > Whatever had been the cause for my previous problem, they obviously > > have fixed them in firmware. > > Unfortunately I still have some problems. > [63]sa# evdev-dump /dev/input/event1 > /dev/input/event1 3043946310.664423 EV_ABS ABS_MT_TRACKING_ID 0x0000003F > /dev/input/event1 3043946310.664423 EV_ABS ABS_MT_POSITION_X 0x000001C9 > /dev/input/event1 3043946310.664423 EV_ABS ABS_MT_POSITION_Y 0x00000112 > /dev/input/event1 3043946310.664423 EV_KEY BTN_TOUCH 0x00000001 > /dev/input/event1 3043946310.664423 EV_ABS ABS_X 0x000001C9 > /dev/input/event1 3043946310.664423 EV_ABS ABS_Y 0x00000112 > /dev/input/event1 3043946310.664423 EV_SYN SYN_REPORT 0x00000000 > /dev/input/event1 3043946310.784395 EV_ABS ABS_MT_TRACKING_ID 0xFFFFFFFF > /dev/input/event1 3043946310.784395 EV_KEY BTN_TOUCH 0x00000000 > /dev/input/event1 3043946310.784395 EV_SYN SYN_REPORT 0x00000000 > > > > > /dev/input/event1 3043946316.944324 EV_ABS ABS_MT_TRACKING_ID 0x00000040 > /dev/input/event1 3043946316.944324 EV_ABS ABS_MT_POSITION_X 0x000001CE > /dev/input/event1 3043946316.944324 EV_ABS ABS_MT_POSITION_Y 0x000000FE > /dev/input/event1 3043946316.944324 EV_KEY BTN_TOUCH 0x00000001 > /dev/input/event1 3043946316.944324 EV_ABS ABS_X 0x000001CE > /dev/input/event1 3043946316.944324 EV_ABS ABS_Y 0x000000FE > /dev/input/event1 3043946316.944324 EV_SYN SYN_REPORT 0x00000000 > /dev/input/event1 3043946317.004303 EV_ABS ABS_MT_TRACKING_ID 0xFFFFFFFF > /dev/input/event1 3043946317.004303 EV_KEY BTN_TOUCH 0x00000000 > /dev/input/event1 3043946317.004303 EV_SYN SYN_REPORT 0x00000000 > > > > /dev/input/event1 3043946319.744283 EV_ABS ABS_MT_TRACKING_ID 0x00000041 > /dev/input/event1 3043946319.744283 EV_ABS ABS_MT_POSITION_X 0x0000020E > /dev/input/event1 3043946319.744283 EV_ABS ABS_MT_POSITION_Y 0x000000D8 > /dev/input/event1 3043946319.744283 EV_KEY BTN_TOUCH 0x00000001 > /dev/input/event1 3043946319.744283 EV_ABS ABS_X 0x0000020E > /dev/input/event1 3043946319.744283 EV_ABS ABS_Y 0x000000D8 > /dev/input/event1 3043946319.744283 EV_SYN SYN_REPORT 0x00000000 > /dev/input/event1 3043946319.864240 EV_ABS ABS_MT_TRACKING_ID 0xFFFFFFFF > /dev/input/event1 3043946319.864240 EV_KEY BTN_TOUCH 0x00000000 > /dev/input/event1 3043946319.864240 EV_SYN SYN_REPORT 0x00000000 > > > > /dev/input/event1 3043946322.004229 EV_ABS ABS_MT_TRACKING_ID 0x00000042 > /dev/input/event1 3043946322.004229 EV_ABS ABS_MT_POSITION_X 0x00000209 > /dev/input/event1 3043946322.004229 EV_ABS ABS_MT_POSITION_Y 0x000000CD > /dev/input/event1 3043946322.004229 EV_KEY BTN_TOUCH 0x00000001 > /dev/input/event1 3043946322.004229 EV_ABS ABS_X 0x00000209 > /dev/input/event1 3043946322.004229 EV_ABS ABS_Y 0x000000CD > /dev/input/event1 3043946322.004229 EV_SYN SYN_REPORT 0x00000000 > > > > > /dev/input/event1 3043946325.454187 EV_ABS ABS_MT_POSITION_X 0x0000016A > /dev/input/event1 3043946325.454187 EV_ABS ABS_MT_POSITION_Y 0x000000D2 > /dev/input/event1 3043946325.454187 EV_ABS ABS_X 0x0000016A > /dev/input/event1 3043946325.454187 EV_ABS ABS_Y 0x000000D2 > /dev/input/event1 3043946325.454187 EV_SYN SYN_REPORT 0x00000000 > /dev/input/event1 3043946325.574174 EV_ABS ABS_MT_POSITION_X 0x0000016B > /dev/input/event1 3043946325.574174 EV_ABS ABS_X 0x0000016B > /dev/input/event1 3043946325.574174 EV_SYN SYN_REPORT 0x00000000 > > All 5 blocks are a single touch, which means finger on screen for a short > moment. > On the first 3 I get position data and BTN_TOUCH 1 as well as BTN_TOUCH 0. > But this is not consistent, sometime I get only a 1 and sometime only a 0. > In the 5th block I even got neither. > The timestamps on the first 3 cases mark it clearly when I removed the finger. > I got a 1 on touch-start and a 0 on touch-end. > On the 4th case I got a touch-start, but no touch-end. > In the 5th case I only got positon updates. > This is a 7" display - the 10" also delivers ABS_PRESSURE, but the problem > is the same that I don't consistently get the EV_KEY events. I somehow suspect that the device is dropping data, when the driver isn't retrieving it fast enough. I can't say for sure however, because usbdump has more interupt packets than there is events on the /dev/input , although X and Y coordinates come in the same packet. But I couldn't isolate the button packets yet. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Mon Mar 26 05:30:48 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46438F6D1DB for ; Mon, 26 Mar 2018 05:30:48 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B750D6B5FE for ; Mon, 26 Mar 2018 05:30:47 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2Q5UiYI031567 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 25 Mar 2018 22:30:45 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2Q5UiBX031566; Sun, 25 Mar 2018 22:30:44 -0700 (PDT) (envelope-from fbsd) Date: Sun, 25 Mar 2018 22:30:44 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Persistent kernel build trouble on RPi3 Message-ID: <20180326053044.GA31534@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2018 05:30:48 -0000 Recent attempts to compile a kernel on -current running on an RPi3 have been failing through r331541. The persistent error message is: --- all_subdir_armv8crypto --- In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: In file included from /usr/lib/clang/6.0.0/include/arm_neon.h:31: /usr/lib/clang/6.0.0/include/stdint.h:228:25: error: typedef redefinition with different types ('int16_t' (aka 'short') vs '__int_fast16_t' (aka 'int')) typedef __int_least16_t int_fast16_t; ^ /usr/src/sys/sys/stdint.h:51:25: note: previous definition is here typedef __int_fast16_t int_fast16_t; ^ In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: In file included from /usr/lib/clang/6.0.0/include/arm_neon.h:31: /usr/lib/clang/6.0.0/include/stdint.h:229:26: error: typedef redefinition with different types ('uint16_t' (aka 'unsigned short') vs '__uint_fast16_t' (aka 'unsigned int')) typedef __uint_least16_t uint_fast16_t; ^ /usr/src/sys/sys/stdint.h:56:26: note: previous definition is here typedef __uint_fast16_t uint_fast16_t; ^ In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: In file included from /usr/lib/clang/6.0.0/include/arm_neon.h:31: /usr/lib/clang/6.0.0/include/stdint.h:245:24: error: typedef redefinition with different types ('int8_t' (aka 'signed char') vs '__int_fast8_t' (aka 'int')) Repeated attempts to update source haven't cleared the error, including complete replacement checkout. Any guidance would be appreciated. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Mon Mar 26 11:44:31 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 205A3F63F91 for ; Mon, 26 Mar 2018 11:44:31 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3FB5798BC for ; Mon, 26 Mar 2018 11:44:30 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 202952110F for ; Mon, 26 Mar 2018 07:44:30 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute5.internal (MEProxy); Mon, 26 Mar 2018 07:44:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=2jsrmP rknwCoLAkAn+M80S1MF8v7uvCEs0bf2NMMziQ=; b=Oy0njKMuxEGNSUl2I7GRVK pM1gS350ImzdiG/Fl1gQYMnKiMoxTyA0XC7U51Zk/eU/eeHkYFDhEdiajHQZxeZ0 NNJVK/+cigYnULFfJPgh8nrOZ7o3s7rKx2j1tYPvMl79jykVn736HL0M6AZXwxej /4fl5yPmSf8qhsb2NtYihdVLEiOh+BJm+HRhKejSCXBW/ZqiC33L/HlPW4wdC1Ab XPnyrXdlxGGaRZ8ExhrC95Iv/80dD4Od3+5HrJ8UhmHmkCMhRZvaPIaRdjLjJYRZ XAVUvVho/5oLSlm7NL/uhd2WdPlENhnPR/NJMpvohwraTkReno6x2my5+qMTmriA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id F118FBA43B; Mon, 26 Mar 2018 07:44:29 -0400 (EDT) Message-Id: <1522064669.1615786.1316163736.13DB14DE@webmail.messagingengine.com> From: Brad Davis To: freebsd-arm@freebsd.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Subject: Re: ROCK64: support for RK3328 A53? Date: Mon, 26 Mar 2018 05:44:29 -0600 References: <20180317121812.2680c6f5@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180317121812.2680c6f5@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2018 11:44:31 -0000 On Sat, Mar 17, 2018, at 5:17 AM, O. Hartmann wrote: > > Hello list, > > I'm courios about the support of the ROCK64 SoC. This board is very > interesting and I'd > like to ask whether there is support via FreeBSD 12-CURRENT? IIRC, manu is working on it.. Regards, Brad Davis From owner-freebsd-arm@freebsd.org Tue Mar 27 04:25:09 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C9DDF71AF2; Tue, 27 Mar 2018 04:25:09 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1544A6B559; Tue, 27 Mar 2018 04:25:08 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w2R4Ou6F016830 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Mar 2018 06:24:57 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1522124698; bh=pORY5+hOOIsGZP9JM5tv9jjnMM5nRT39C6AnSNxs9YA=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=VH1v3Utz+sx319OCiKMe4YO3/uZNNJtB2Q6qfKrzEw3OM0M7+PcyT5apmSoubZUW6 LrfUoD/AGdjF1Gw73muGUyp3IL6xwmdtTWtDjEQ0S8B7HpYPD1a1mZX4dYReVAGwyV OvhnPavQ5+eSYuZ6SAkEq5phmejjiIePAiwcslAc= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w2R4OqB1058450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Mar 2018 06:24:52 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w2R4Oqas027302 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 27 Mar 2018 06:24:52 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w2R4OpUf027301; Tue, 27 Mar 2018 06:24:51 +0200 (CEST) (envelope-from ticso) Date: Tue, 27 Mar 2018 06:24:51 +0200 From: Bernd Walter To: Hans Petter Selasky Cc: Bernd Walter , freebsd-arm@freebsd.org, freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: webcamd based touchscreen problem on Pi3 Message-ID: <20180327042451.GE16646@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20180309004433.GI86413@cicely7.cicely.de> <4765ef04-6fb1-f9dc-315d-c4419d6ba016@selasky.org> <20180309114025.GJ86413@cicely7.cicely.de> <20180309132539.GL86413@cicely7.cicely.de> <20180310000336.GM86413@cicely7.cicely.de> <20180312111246.GA14138@cicely7.cicely.de> <20180325231128.GA16646@cicely7.cicely.de> <20180325232806.GB16646@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180325232806.GB16646@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 04:25:09 -0000 On Mon, Mar 26, 2018 at 01:28:06AM +0200, Bernd Walter wrote: > I somehow suspect that the device is dropping data, when the driver isn't > retrieving it fast enough. > I can't say for sure however, because usbdump has more interupt packets than > there is events on the /dev/input , although X and Y coordinates come in the > same packet. > But I couldn't isolate the button packets yet. The 10" (not the early model I had before) is working fine now using wmt(4). I'd tested with wmt(4) before, but it failed. Interestingly xf86-input-mouse via usbhidlib did work with mouse emulation on the 7", which the 10" doesn't have, but the emulation of the device was bad and in touch mode X crashed on both displays during device init. uep(4) doesn't work at all, it is for a completely different protocol used on some older eGalax devices - obviously some with resistive touch, but not sure. Similar the egalax_ts.c in webcamd is only for the older eGalax devices. Have to see why wmt(4) doesn't like the older devices, maybe this can be fixed. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Mar 30 23:50:42 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C27BF7478F for ; Fri, 30 Mar 2018 23:50:42 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 18E1186407 for ; Fri, 30 Mar 2018 23:50:41 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2UNodYD053852 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Mar 2018 16:50:40 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2UNodU2053851; Fri, 30 Mar 2018 16:50:39 -0700 (PDT) (envelope-from fbsd) Date: Fri, 30 Mar 2018 16:50:39 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: More problems self-hosting -current on RPi3 Message-ID: <20180330235039.GA53786@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 23:50:42 -0000 Here's a strange buildworld failure with -current on an RPI3. To set the stage, a make -j2 buildworld/buildkernel was run from a clean (run make cleandir twice, rm -rf /usr/obj/usr/src) start. Kernel and sources were at, or close to, r331146. Buildworld finished, but the kernel build failed on an error of long standing, something about mismatches between various versions of stdint.h in the file system. Svnlite update reported quite a bit of activity, so the world/kernel build was restarted with -j2 and -DNO_CLEAN. Some hours later, the system was found with all ssh sessions terminated and the top output recorded in the link below. It looks as if the system decided it was out of swap, and then went on a killing spree when lld.ld didn't go away. Disregarding the stated swap usage, ld.lld was less than 1.4 GB in size with 3 GB of swap. Details are at http://www.zefox.net/~fbsd/rpi3/crashes/20180330/ It's worth noting that gstat reports write speeds of 2-3 MB/sec to the microSD card and USB flash, which does not seem much worse than mechanical hard disks. The system _does_ seem prone to a sort of "swap frenzy" when swap usage goes much over 10%, recovering at intervals when all the cores are busy. Some months ago it was at least occasionally possible to finish a -j4 buildworld, now even -j2 buildworld is extremely uncertain. Is anybody able to self host -current in the last few weeks on an RPI3? Thanks for reading, bob prohaska