From owner-freebsd-arm@freebsd.org Sun Aug 4 04:03:48 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1042BC3E85 for ; Sun, 4 Aug 2019 04:03: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 461S1t42qKz44RM for ; Sun, 4 Aug 2019 04:03:45 +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 x7443eWO088277 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 3 Aug 2019 21:03:41 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x7443eUo088276; Sat, 3 Aug 2019 21:03:40 -0700 (PDT) (envelope-from fbsd) Date: Sat, 3 Aug 2019 21:03:40 -0700 From: bob prohaska To: Mika??l Urankar Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Clang8 crash on rpi3 at r349989 building openjdk8 Message-ID: <20190804040339.GA87346@www.zefox.net> References: <20190725001440.GA38603@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 461S1t42qKz44RM X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [2.17 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.08)[ip: (0.35), ipnet: 50.1.16.0/20(0.18), asn: 7065(-0.05), country: US(-0.05)]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.19)[0.189,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2019 04:03:48 -0000 On Thu, Jul 25, 2019 at 08:32:36AM +0200, Mika??l Urankar wrote: > Le jeu. 25 juil. 2019 ?? 02:15, bob prohaska a ??crit : > > > > In trying to compile www/chromium on an rpi3 at r349989 with > > ports at 507005 clang8 crashed in a way that superficially > > It's reported here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236566 Indeed, that looks familar 8-( > openjdkd11 is not affected by this bug (and it's the 'mixed' mode > version), if you want to try it : > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239246 > you'll probably need #237054 > It's a happy thought, but openjdk11 seems to be amd64 and i386 only. I'm on aarch64. Thanks for writing! bob prohaska From owner-freebsd-arm@freebsd.org Sun Aug 4 21:00:21 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5C63BB1881 for ; Sun, 4 Aug 2019 21:00:21 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 461tZs1n1Nz3NPj for ; Sun, 4 Aug 2019 21:00:21 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 205B092CB for ; Sun, 4 Aug 2019 21:00:21 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x74L0Le3003147 for ; Sun, 4 Aug 2019 21:00:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x74L0LHH003138 for freebsd-arm@FreeBSD.org; Sun, 4 Aug 2019 21:00:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201908042100.x74L0LHH003138@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, 4 Aug 2019 21:00:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2019 21:00:21 -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 ------------+-----------+--------------------------------------------------- Open | 238576 | Raspberry Pi 3B+ "shutdown -p" does not shut off 1 problems total for which you should take action. From owner-freebsd-arm@freebsd.org Mon Aug 5 03:21:25 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E5645B87BC for ; Mon, 5 Aug 2019 03:21:25 +0000 (UTC) (envelope-from dpolyg@gmail.com) Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46232Y03Xjz49KB for ; Mon, 5 Aug 2019 03:21:24 +0000 (UTC) (envelope-from dpolyg@gmail.com) Received: by mail-pl1-x636.google.com with SMTP id c2so35856846plz.13 for ; Sun, 04 Aug 2019 20:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=6x+Y+7FE6DfAjZtJaVmQ7Yy0pTEGLLE4Vxuq9knnfcQ=; b=EJxeqVsntGWadUseobFT1rLHVinD1NDnh+QQvytLgROXzEvPZ5bcjbLsyZ+39bfnI/ 7ZxOs9xH9HrXn6OcA426yWUNRkIr46woz4SUfNUepDrmPFPbOj09tcwOD6Gik3aDzAw+ FqbfFFZwvhTTHaDLmYo+SnH54aiL/QZWmI6Cxz5jZ42ioeDSV4R9h0PDR5vhyd+v4o4A lqzZp2ht1NZ9G2yo25Gd4YLp+Fg7unZtYsc/Wh0UackAGR4hLiJS4lsFtW4h1Kiq/sXH /CD4OYkTuwitFr8vlpHOL9qoGIZZRjUug1Ykrt9qM+/O8ScuIRxrrMcjA4CrzbbCLT5D E6vA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6x+Y+7FE6DfAjZtJaVmQ7Yy0pTEGLLE4Vxuq9knnfcQ=; b=onc5rFpXCj8aTtyXrBTyKDXSaO+tNRfK0HgGWcApevR5Xj9YjLyvNnqJZBFbP8BUA/ ZLeP48Qcz4Z5ZcWPfmt44Tia0WahRp0eTnJM/ny64fUMvrE7QtCLx8bN0Asl1Gmc3zjh Dbfi0CiRBi4+mTwLNP+P8l+mV4S6blKVSPcl80+Tq8xPGnXIKu9O6OQI25S4M6VGtSUi WhfT/3JC8BrLa6vFnysqhdEsoQG0+VjRg5XiXjeo4KB7Li9BcKvM7+qc/c1BQDbXrv0e 0l3IuxJoKHWac1shty1rlpu6ZtENdx0gjMGyXa6z4kX21tP6p15hdBlrE6XIG/Qfj0um 5pGg== X-Gm-Message-State: APjAAAUMsjK+Axh3jXZSTduwmQ+Qa8viHxru2Uc6qy6Zl325c5gt/V0m 2oACM9FGJLyc8qS9XUzWaIsspYYh X-Google-Smtp-Source: APXvYqyixbw6cugtsPKkS6ryz5mWBksXNf++fubfpRnI0rrCh+JD230Sb/X+kevujoigI/CD9ZCCIQ== X-Received: by 2002:a17:902:aa8a:: with SMTP id d10mr145421306plr.154.1564975282782; Sun, 04 Aug 2019 20:21:22 -0700 (PDT) Received: from [192.168.1.100] (ngn7-ppp1611.tokyo.sannet.ne.jp. [157.192.94.87]) by smtp.googlemail.com with ESMTPSA id o128sm88038862pfb.42.2019.08.04.20.21.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Aug 2019 20:21:21 -0700 (PDT) Subject: Re: Booting FreeBSD on Rock64 To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org References: <169de7cf-32f2-7b7b-c12e-a86a4b6a9e87@gmail.com> <20190715200127.4b649877d8baefeb5282df64@bidouilliste.com> <878b15d5-92a5-5137-121c-5a5038323857@gmail.com> <20190718145840.c4487d2174930374300a0d7d@bidouilliste.com> <300bcdce-1471-e9a6-e332-84d3f822a65c@gmail.com> <20190728164619.7f40eccb59717d18996164b1@bidouilliste.com> From: Denis Polygalov Message-ID: <668cc179-4f33-091e-d0b8-1c2fa52dbbaf@gmail.com> Date: Mon, 5 Aug 2019 12:21:18 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190728164619.7f40eccb59717d18996164b1@bidouilliste.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46232Y03Xjz49KB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=EJxeqVsn; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of dpolyg@gmail.com designates 2607:f8b0:4864:20::636 as permitted sender) smtp.mailfrom=dpolyg@gmail.com X-Spamd-Result: default: False [-2.99 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.99)[-0.990,0]; RECEIVED_SPAMHAUS_PBL(0.00)[87.94.192.157.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[6.3.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.26), ipnet: 2607:f8b0::/32(-3.07), asn: 15169(-2.46), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2019 03:21:26 -0000 > BTW there is a new u-boot-rock64 port that you might want to use, you > can boot from sdcard now. > I can confirm that the /usr/ports/sysutils/u-boot-rock64 works for me. The only thing I've noticed is that the u-boot from ports does not read real MAC address from my board and assign random one during each boot instead. I'm not sure is this a bug or a future... So my complete set of commands to manually boot ROCK64 is: => env set ethaddr 82:d6:05:XX:XX:XX => dhcp => tftpboot ${kernel_addr_r} boot/loader.efi => tftpboot ${fdt_addr_r} boot/dtb/rockchip/rk3328-rock64.dtb => fdt addr ${fdt_addr_r} => bootefi ${kernel_addr_r} ${fdt_addr_r} Note that seems like the 'fdt addr' is essential here, as distinct of ayufun's u-boot where it had no effect (for me at least). You also need to connect pin 21 to GND in order to prevent execution of the SPI (wrong one) u-boot. Thanks a lot! Denis. From owner-freebsd-arm@freebsd.org Mon Aug 5 06:06:10 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5C15BBABBD for ; Mon, 5 Aug 2019 06:06:10 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ipmail02.adl2.internode.on.net (ipmail02.adl2.internode.on.net [150.101.137.139]) by mx1.freebsd.org (Postfix) with ESMTP id 4626hc4LrNz4GnC for ; Mon, 5 Aug 2019 06:06:08 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ppp118-210-90-250.adl-adc-lon-bras32.tpg.internode.on.net (HELO midget.dons.net.au) ([118.210.90.250]) by ipmail02.adl2.internode.on.net with ESMTP; 05 Aug 2019 15:30:55 +0930 Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.2/8.15.2) with ESMTPS id x7560oN0055224 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 5 Aug 2019 15:30:51 +0930 (ACST) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.2/8.15.2/Submit) id x755wxRF051541 for ; Mon, 5 Aug 2019 15:28:59 +0930 (ACST) (envelope-from darius@dons.net.au) X-Authentication-Warning: midget.dons.net.au: mailnull set sender to using -f Received: from havok.gsoft.com.au (Havok.gsoft.com.au [203.31.81.177]) by ppp118-210-90-250.adl-adc-lon-bras32.tpg.internode.on.net (envelope-sender ) (MIMEDefang) with ESMTP id x755wrSC051537; Mon, 05 Aug 2019 15:28:59 +0930 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Is it a good idea to use a usb-serial adapter for PPS input? Yes, it is. From: "O'Connor, Daniel" In-Reply-To: Date: Mon, 5 Aug 2019 15:28:53 +0930 Cc: "freebsd-arm@FreeBSD.org" , "usb@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Ian Lepore X-Mailer: Apple Mail (2.3445.104.11) X-Spam-Score: 0 () No, score=0.0 required=5.0 tests=SPF_HELO_NONE, SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.1 X-Scanned-By: MIMEDefang 2.83 on 10.0.2.1 X-Rspamd-Queue-Id: 4626hc4LrNz4GnC X-Spamd-Bar: ++++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of darius@dons.net.au has no SPF policy when checking 150.101.137.139) smtp.mailfrom=darius@dons.net.au X-Spamd-Result: default: False [6.20 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_XAW(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(2.86)[ip: (8.08), ipnet: 150.101.0.0/16(4.31), asn: 4739(1.87), country: AU(0.01)]; R_DKIM_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[139.137.101.150.list.dnswl.org : 127.0.5.1]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:4739, ipnet:150.101.0.0/16, country:AU]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.95)[0.946,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.997,0]; DMARC_NA(0.00)[dons.net.au]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; GREYLIST(0.00)[pass,body] X-Spam: Yes X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2019 06:06:10 -0000 Hi Ian, Firstly, this is a very cool test - thank you for running it :) > On 3 Aug 2019, at 06:46, Ian Lepore wrote: > PPS(2) is an FTDI 232R, a USB 1.1 serial adapter, connected to a port > on a USB 2.0 hub that's connected to a USB 2.0 host port on the > Wandboard. =20 >=20 > PPS(3) is an FTDI 4232H, a USB 2.0 serial adapter, connected to a port > on the same USB hub as PPS(2). =20 > Most people are not worried about their kernel clock being 200 > microseconds off from UTC, even if they're using the PPS signal from a > GPS receiver. So I think most people should feel completely at ease > using a USB serial adapter as the input device for a PPS signal. =20 Does the USB clock derive from the 10MHz Rb clock? If so that would mean = you would see a lot less jitter than a 'normal' user where the USB clock = is not locked too GPS. Do you have a more detailed write up of things like the NTP = configuration file? I think I could replicate your test here although I = have a Beaglebone Black, not a Wanboard so I will need to check if it = can take an external clock. (We have GPS modules & Rb oscillators at = work to create reference clock for bi-static meteor applications). Thanks again. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum From owner-freebsd-arm@freebsd.org Mon Aug 5 14:42:38 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 58160C53EA for ; Mon, 5 Aug 2019 14:42:38 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 462L8Y6nz4z3Gf4 for ; Mon, 5 Aug 2019 14:42:37 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1565016155; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=SR/2jEPaC8rnwFjD76KGUO7Zuc6fhwsugZRLy8tNNzLjQnSR67Jn1ezZFerB7Ckxmczi3BRdafvpT EiZP0/8DF8nVz8kM4Hul3BMX9Xqh/2geenBi7N7/8cSSdlMhQoaQh1xXMfst9qcNyyK3z/Bj9LqLcl uetPMFIiz3GtRmljdrnAL896q1Y8fBoQB/ExSho6Iyut670sU81T7A/mS51XdqpoNsQxCTC20MgPvf yl+Z+1WDlRQl4OY0IyEagqkUXsMiFqfqs1X+5lBXec2uKxS9+Ptdb9ISlo1yn+2WHBtdWMrHHisNdV c49ENDvl6Q/CyK5eh92AzJleNu+Vw2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=c71SP4R8yGAivSaYiL6Q5t3pdnaILEc7M5cjzdREcNQ=; b=MdW0DSkpqZjkz7tVJHb7Fx7AB11/LNaLL1oJKiIfC0eK2s3UZvaPFAwhZbkMqRPLP1eQSSM/LPoOX JF7iYQiq3WafWNk5CCXrqoRtWFLtOwRFp00FuHdYmTbIEPCrjvh2TSG5++anUNlUvMrEJPuz6n6RoK p5pUInGSdBQsxkA7cHFOrbmY85DIF0slVk+o3roo39eTo2IlGirc4V8rGJygKAxnyiFML10IJyM4bn TZLdTbQpD6/5uWg/PpfOEfbaPJjm3veBboZGBN8fj0b12pg3Th9U9T/aHhzyPbKSrW7iWEJ0AnHiXf lPdw8h08bDZvKEYa/hmNV0YONUBPmsQ== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=c71SP4R8yGAivSaYiL6Q5t3pdnaILEc7M5cjzdREcNQ=; b=mLEGneShySupY5Oi0rhwxiD/moMkS6wIFvJqtuhlrdvI01vpiWk6l8Ge8ke2F4VmkF/wE35DLiaBw IxFKXKZZRA1zlP/sP/NYHQBxHErvwYLgwPVtw2G3DXwy5Y1oA/hFb2xVb4hPLRpCc3pyRohKAYVRVz SXZVeUxjYwkc1KnPLc2nUGNxBVuxTdBbXjXjYNbEP/7xZcqkzQgtUcDtCIhFzg+fK1FPf9BvIPKrjn fkBbeeJuyVdFzaflaZh6TEEZ3wyzfeVAUAB9BMf+tLL9ikJrDpufvvu32AD3YZ+KghufCI4dNsopJJ UNypwvpn5spMOGcE+SQI8UzelrWYXPA== X-MHO-RoutePath: aGlwcGll X-MHO-User: 41d5c614-b78f-11e9-85ec-13b9aae3a1d2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 41d5c614-b78f-11e9-85ec-13b9aae3a1d2; Mon, 05 Aug 2019 14:42:34 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x75EgVHu017258; Mon, 5 Aug 2019 08:42:32 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Is it a good idea to use a usb-serial adapter for PPS input? Yes, it is. From: Ian Lepore To: "O'Connor, Daniel" Cc: "usb@freebsd.org" , "freebsd-arm@FreeBSD.org" Date: Mon, 05 Aug 2019 08:42:31 -0600 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 462L8Y6nz4z3Gf4 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.56 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.81)[-0.807,0]; NEURAL_HAM_SHORT(-0.75)[-0.754,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2019 14:42:38 -0000 On Mon, 2019-08-05 at 15:28 +0930, O'Connor, Daniel wrote: > Hi Ian, > > Firstly, this is a very cool test - thank you for running it :) > > > On 3 Aug 2019, at 06:46, Ian Lepore wrote: > > PPS(2) is an FTDI 232R, a USB 1.1 serial adapter, connected to a port > > on a USB 2.0 hub that's connected to a USB 2.0 host port on the > > Wandboard. > > > > PPS(3) is an FTDI 4232H, a USB 2.0 serial adapter, connected to a port > > on the same USB hub as PPS(2). > > > > > Most people are not worried about their kernel clock being 200 > > microseconds off from UTC, even if they're using the PPS signal from a > > GPS receiver. So I think most people should feel completely at ease > > using a USB serial adapter as the input device for a PPS signal. > > Does the USB clock derive from the 10MHz Rb clock? If so that would mean you would see a lot less jitter than a 'normal' user where the USB clock is not locked too GPS. > No, usb is derived from the same 24mhz crystal that clocks the cpus. I think usb and its need for clocks at 48 and 480mhz is why so many small arm systems use a 24mhz main clock. > Do you have a more detailed write up of things like the NTP configuration file? I think I could replicate your test here although I have a Beaglebone Black, not a Wanboard so I will need to check if it can take an external clock. (We have GPS modules & Rb oscillators at work to create reference clock for bi-static meteor applications). > The same setup should be possible on a BBB. There is a TCLKIN pin mentioned in the manual. Some searching on the web yields a few clues that it might be possible to mux that to a pin on the P9 header [1]. There is already a dmtpps capture driver for TI, but I'm afraid it may have bitrotted over the past couple years. Also, even when it last worked, it just barely worked, because the reduction of kernel timecounters from 10 to 2 timehands causes the PPS capture to almost always get lost on single-core processors which are in cpu_idle() at the time the hardclock interrupt happens. (But that's fixable by just increasing the number of timehands, I think at least 4 are required.) So all in all, it's doable, but it'll take a bit of work. I can help with the driver stuff. The ntp config is pretty simple, it uses instances of the "atom" clock, which is a bare-PPS refclock which needs to be paired with any network peer to operate. The network peer is used to obtain the initial time of day, then the PPS signal is used to steer phase. The network peer must be marked 'prefer' for some reason, it's just an ntp rule. In my test setup I forced ntp to steer to the "perfect" pps signal by marking all the others as "noselect", otherwise any of the atom clocks would be eligible to be the system peer. server iburst prefer server 127.127.22.0 minpoll 4 maxpoll 4 fudge 127.127.22.0 stratum 0 refid gpt server 127.127.22.1 minpoll 4 maxpoll 4 noselect fudge 127.127.22.1 stratum 0 refid gpio server 127.127.22.2 minpoll 4 maxpoll 4 noselect fudge 127.127.22.2 stratum 0 refid usb1 server 127.127.22.3 minpoll 4 maxpoll 4 noselect fudge 127.127.22.3 stratum 0 refid usb2 [1] http://e2e.ti.com/support/processors/f/791/t/406121?AM335x-TCLKIN-on-Linux-3-19 -- Ian From owner-freebsd-arm@freebsd.org Tue Aug 6 12:09:44 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 88DD2C0B06 for ; Tue, 6 Aug 2019 12:09:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 462tjh34Brz3yMH for ; Tue, 6 Aug 2019 12:09:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 46CB92BAF1 for ; Tue, 6 Aug 2019 12:09:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x76C9ihc008823 for ; Tue, 6 Aug 2019 12:09:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x76C9idK008805 for freebsd-arm@FreeBSD.org; Tue, 6 Aug 2019 12:09:44 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 239673] Spurious Interrupt message from /dev/led/led1 Date: Tue, 06 Aug 2019 12:09:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 12.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: phk@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 12:09:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239673 Bug ID: 239673 Summary: Spurious Interrupt message from /dev/led/led1 Product: Base System Version: 12.0-STABLE Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: phk@FreeBSD.org With 12.0 RPI2 image on a 1.1 RPI2: echo "f" > /dev/led/led1 Results in console messages: gpio0: Stray irq 35 disabled gpio0: Stray irq 35 disabled gpio0: Stray irq 35 disabled One message appears each time the red LED turns on. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Aug 6 14:14:23 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0E3C4C2D00 for ; Tue, 6 Aug 2019 14:14:23 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 462xTT702Tz448w for ; Tue, 6 Aug 2019 14:14:21 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Tue, 06 Aug 2019 16:14:18 +0200 id 00F406AA.5D498B3A.00005A6B Date: Tue, 6 Aug 2019 16:14:15 +0200 From: Milan Obuch To: freebsd-arm@freebsd.org Subject: Re: Attempt to use uart0 on Zybo Z7 Message-ID: <20190806161415.4be2a991@zeta.dino.sk> In-Reply-To: <20190803091019.2d067756@zeta.dino.sk> References: <20190803091019.2d067756@zeta.dino.sk> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; i386-portbld-freebsd11.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 462xTT702Tz448w X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-arm@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-arm@dino.sk X-Spamd-Result: default: False [-6.23 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.986,0]; RCVD_IN_DNSWL_NONE(0.00)[72.65.245.84.list.dnswl.org : 127.0.10.0]; IP_SCORE(-2.94)[ip: (-8.32), ipnet: 84.245.64.0/18(-4.16), asn: 16160(-2.30), country: SK(0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16160, ipnet:84.245.64.0/18, country:SK]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 14:14:23 -0000 On Sat, 3 Aug 2019 09:10:19 +0200 Milan Obuch wrote: > Hi, > > Zynq SoC has several peripherals available on its PS/ARM side of > thing. Currently supported list contains UART, USB, ethernet, SDIO > and GPIO. No driver yet for SPI, I2C and CAN. > > Available GPIO pins are on JF6 (MIO pmod connector), I tested them as > inputs and they are working as expected. Also, I did a 'hardware loopback' - connected pins 9 and 10, which should be MIO14 and MIO15, one of them configured as output, and it was doing what it should - toggling the output makes toggle the input, as expected. > All other peripherals are present in pairs, so I decided to try the > simplest one - UART. > > On Zybo Z7 we use uart1 as console for both u-boot and kernel, so the > unused one is uart0. In order to create its driver instance, it was > necessary to add just > > &uart0 {status = "okay";}; > > into dts, create dtb from it and use it for boot. This is enough for > uart0 to present itself as > > uart0: mem 0-0xfff irq 6 on simplebus1 > > in dmesg (or > > uart0: mem 0-0xfff irq 6 on simplebus1 > uart0: fast interrupt > uart0: PPS capture mode: DCD > > in verbose boot dmesg). > > That was really easy. Now we need uart0 interface (rx and tx) to > appear on some available pins. According to MIO-at-a-glance table in > Zynq TRM (section 2.5.4) there are two possibilities - MIO10 and > MIO11 or MIO14 and MIO15. > > I played a bit with zy7_slcr_attach() function in > arm/xilinx/zy7_slcr.c file. With some printf and RD4 calls I can see > MIO pin configuration - currently we have no pinmux for Zynq, so I > decided to try register access to check and eventually program. > Studying existing configuration and Zynq TRM, appendix B.28 for > registers detail of slcr leads me to believe I need something like > > WR4(sc, ZY7_SLCR_MIO_PIN(14), 0x16E0); > WR4(sc, ZY7_SLCR_MIO_PIN(15), 0x16E1); > > to do the necessary pinmuxing. As access to slcr register is locked, > it was necessary to add call > > zy7_slcr_unlock(sc); > > before in order for write to be executed at all, which I verified with > values being read back correctly. Without this call no change to > registers was done. > In Zynq TRM, section 19.5.1 - MIO programming is description of what should be done for pinmux, using 0x12E0 and 0x12E1 for 1.8 V instead of 3.3 V as I did, so this should be OK. > Unfortunatelly, I am still missing something - I tried to create > physical loop connecting pins MIO14 and MIO15 (on my board connected > to JF9 and JF10 pins) but nothing - typing anything to 'cu > -l /dev/cuau0' does not make to read it back. > > Did anybody any clue what I am missing? I verified I am connecting the > right pins, but I see nothing arriving back when typing... > Could this be interrupt issue? Output of 'vmstat -i' command is something like interrupt total rate gic0,p13: mp_tmr0 1692019 28 gic0,s22: cgem0 2985 0 gic0,s24:-dhci_fdt0 1103 0 gic0,s50: uart1 200 0 cpu0:rendezvous 5 0 cpu1:rendezvous 31 0 cpu0:preempt 192954 3 cpu1:preempt 258906 4 cpu0:hardclock 17 0 Total 2148220 36 When I am doing something on console, there is increase in number on line beginning with gic0,s50: uart1. In another session, I am invoking 'cu -l /dev/cuau0 -s 9600'. No sign of activity when typing here - no echo, no interrupt for uart0 seen. In fact, I need to issue 'vmstat -ia' to see all interrupts, grepping for uart gives me gic0,s27: uart0 0 0 gic0,s50: uart1 232 0 (I did something on console in between.) Part of 'devinfo -r' output is uart0 Interrupts: 0x6 Device Memory: 0xe0000000-0xe0000fff uart1 Interrupts: 0x7 Device Memory: 0xe0001000-0xe0001fff And here the question: how does those numbers relate to each other? I mean, in devinfo output uart0 has interrupt 6, in vmstat line begins with gic0,s27 and for uart they are interrupt 7 and gic0,s50. I see interrupts 27 and 50 in zynq-7000.dtsi, I do not know where 6 and 7 is coming from - it looks like they are in order of device discovery on boot. Is here something to be done for interrupts? One more difference between uart0 and uart1 are clocks - 'clocks' property in dts differs, whereas 'clock-names' does not. Is here something to be done to enable uart0? Any hint appreciated... Regards, Milan From owner-freebsd-arm@freebsd.org Tue Aug 6 15:44:56 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 30CB4C4403 for ; Tue, 6 Aug 2019 15:44:56 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 462zTz23crz48Qf for ; Tue, 6 Aug 2019 15:44:54 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Tue, 06 Aug 2019 17:44:53 +0200 id 00F406C1.5D49A075.00006639 Date: Tue, 6 Aug 2019 17:44:49 +0200 From: Milan Obuch To: freebsd-arm@freebsd.org Subject: Re: Attempt to use uart0 on Zybo Z7 Message-ID: <20190806174449.24493f85@zeta.dino.sk> In-Reply-To: <20190806172337.31f87439@zeta.dino.sk> References: <20190803091019.2d067756@zeta.dino.sk> <20190806161415.4be2a991@zeta.dino.sk> <20190806172337.31f87439@zeta.dino.sk> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; i386-portbld-freebsd11.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 462zTz23crz48Qf X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-arm@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-arm@dino.sk X-Spamd-Result: default: False [-6.28 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; RCVD_IN_DNSWL_NONE(0.00)[72.65.245.84.list.dnswl.org : 127.0.10.0]; IP_SCORE(-2.99)[ip: (-8.39), ipnet: 84.245.64.0/18(-4.20), asn: 16160(-2.40), country: SK(0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16160, ipnet:84.245.64.0/18, country:SK]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 15:44:56 -0000 On Tue, 6 Aug 2019 17:23:37 +0200 Milan Obuch wrote: > On Tue, 6 Aug 2019 16:14:15 +0200 > Milan Obuch wrote: > > > On Sat, 3 Aug 2019 09:10:19 +0200 > > Milan Obuch wrote: > > > > > Hi, > > > > > > Zynq SoC has several peripherals available on its PS/ARM side of > > > thing. Currently supported list contains UART, USB, ethernet, SDIO > > > and GPIO. No driver yet for SPI, I2C and CAN. > > > > > > Available GPIO pins are on JF6 (MIO pmod connector), I tested them > > > as inputs and they are working as expected. > > > > After some testing I found a way to enable uart0. Currently only > devices initialized by u-boot could be used, I think, and uart0 had no > clocks initialized. Now my hardware loopback works, I am going to > connect TTL-RS232 level converter and/or USB/UART convertor to check > from other box. > > Summary: > > zy7_slcr_unlock(sc); > WR4(sc, ZY7_SLCR_MIO_PIN(14), 0x16E1); > WR4(sc, ZY7_SLCR_MIO_PIN(15), 0x16E0); > > j = RD4(sc, ZY7_SLCR_APER_CLK_CTRL); > WR4(sc, ZY7_SLCR_APER_CLK_CTRL, j | > ZY7_SLCR_APER_CLK_CTRL_UART0_CPU_1XCLKACT); > > j = RD4(sc, ZY7_SLCR_UART_CLK_CTRL); > WR4(sc, ZY7_SLCR_UART_CLK_CTRL, j | 1); > > This makes necessary MIO routing change, enables APB and refererence > clocks for uart0. I put this at end of zy7_slcr_attach() function as > mentioned in original mail. > Testing with TTL-RS232 level converter: it works almost perfect, just bit rate is doubled. On Zybo I use cu -l /dev/cuau0 -s 9600 and on the other box cu -l /dev/cuaU3 -s 19200 and then I see all I type over the wire, on the other end, correctly. Milan From owner-freebsd-arm@freebsd.org Tue Aug 6 15:23:44 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 90C2BC4010 for ; Tue, 6 Aug 2019 15:23:44 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 462z1W3SbCz47cB for ; Tue, 6 Aug 2019 15:23:42 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Tue, 06 Aug 2019 17:23:40 +0200 id 00F406AD.5D499B7C.000062D0 Date: Tue, 6 Aug 2019 17:23:37 +0200 From: Milan Obuch To: freebsd-arm@freebsd.org Subject: Re: Attempt to use uart0 on Zybo Z7 Message-ID: <20190806172337.31f87439@zeta.dino.sk> In-Reply-To: <20190806161415.4be2a991@zeta.dino.sk> References: <20190803091019.2d067756@zeta.dino.sk> <20190806161415.4be2a991@zeta.dino.sk> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; i386-portbld-freebsd11.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 462z1W3SbCz47cB X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-arm@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-arm@dino.sk X-Spamd-Result: default: False [-6.26 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; RCVD_IN_DNSWL_NONE(0.00)[72.65.245.84.list.dnswl.org : 127.0.10.0]; IP_SCORE(-2.96)[ip: (-8.36), ipnet: 84.245.64.0/18(-4.18), asn: 16160(-2.35), country: SK(0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16160, ipnet:84.245.64.0/18, country:SK]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 15:23:44 -0000 On Tue, 6 Aug 2019 16:14:15 +0200 Milan Obuch wrote: > On Sat, 3 Aug 2019 09:10:19 +0200 > Milan Obuch wrote: > > > Hi, > > > > Zynq SoC has several peripherals available on its PS/ARM side of > > thing. Currently supported list contains UART, USB, ethernet, SDIO > > and GPIO. No driver yet for SPI, I2C and CAN. > > > > Available GPIO pins are on JF6 (MIO pmod connector), I tested them > > as inputs and they are working as expected. > After some testing I found a way to enable uart0. Currently only devices initialized by u-boot could be used, I think, and uart0 had no clocks initialized. Now my hardware loopback works, I am going to connect TTL-RS232 level converter and/or USB/UART convertor to check from other box. Summary: zy7_slcr_unlock(sc); WR4(sc, ZY7_SLCR_MIO_PIN(14), 0x16E1); WR4(sc, ZY7_SLCR_MIO_PIN(15), 0x16E0); j = RD4(sc, ZY7_SLCR_APER_CLK_CTRL); WR4(sc, ZY7_SLCR_APER_CLK_CTRL, j | ZY7_SLCR_APER_CLK_CTRL_UART0_CPU_1XCLKACT); j = RD4(sc, ZY7_SLCR_UART_CLK_CTRL); WR4(sc, ZY7_SLCR_UART_CLK_CTRL, j | 1); This makes necessary MIO routing change, enables APB and refererence clocks for uart0. I put this at end of zy7_slcr_attach() function as mentioned in original mail. Now the question is how to do this properly - we have no pinmux and clock infrastructure for Zynq yet. Regards, Milan From owner-freebsd-arm@freebsd.org Wed Aug 7 09:28:22 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4968BC445C for ; Wed, 7 Aug 2019 09:28:22 +0000 (UTC) (envelope-from bounce@seonews.co.za) Received: from m73.bnc.seonews.co.za (m73.bnc.seonews.co.za [164.132.119.73]) (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 463R4z75d4z4SNg for ; Wed, 7 Aug 2019 09:28:19 +0000 (UTC) (envelope-from bounce@seonews.co.za) Message-ID: <500b04d9a7b77ecd80a981c75b6b837f@seonews.co.za> Date: Wed, 07 Aug 2019 09:28:12 +0000 Subject: Search Engine Optimization Tips From: Bright House Solutions Reply-To: Bright House Solutions To: "freebsd-arm@freebsd.org" MIME-Version: 1.0 X-Twbx-Tracking-Did: 0 X-Twbx-Subscriber-Uid: je168zlvje522 X-Twbx-Mailer: SwiftMailer - 5.4.x X-Twbx-EBS: http://seonews.co.za/account/index.php/lists/block-address X-Twbx-Delivery-Sid: 1 X-Twbx-Customer-Uid: fv600mbvhs7be X-Twbx-Customer-Gid: 1 X-Twbx-Campaign-Uid: hm4047x1kw08a X-Sender: bounce@seonews.co.za X-Report-Abuse: Please report abuse for this campaign here: http://seonews.co.za/account/index.php/campaigns/hm4047x1kw08a/report-abuse/rn460m07z1d0a/je168zlvje522 X-Receiver: freebsd-arm@freebsd.org Precedence: bulk Feedback-ID: hm4047x1kw08a:je168zlvje522:rn460m07z1d0a:fv600mbvhs7be X-Rspamd-Queue-Id: 463R4z75d4z4SNg X-Spamd-Bar: / X-Spamd-Result: default: False [-0.05 / 15.00]; HAS_REPLYTO(0.00)[matthew@seotips.co.za]; R_SPF_ALLOW(0.00)[+ip4:164.132.119.73]; REPLYTO_DN_EQ_FROM_DN(0.00)[]; DKIM_TRACE(0.00)[seonews.co.za:+]; DMARC_POLICY_ALLOW(0.00)[seonews.co.za,quarantine]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; MAILLIST(-0.10)[generic]; FORGED_SENDER(0.00)[matthew@seonews.co.za,bounce@seonews.co.za]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.47)[ip: (-9.42), ipnet: 164.132.0.0/16(-4.13), asn: 16276(1.21), country: FR(-0.01)]; ASN(0.00)[asn:16276, ipnet:164.132.0.0/16, country:FR]; FROM_NEQ_ENVFROM(0.00)[matthew@seonews.co.za,bounce@seonews.co.za]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; ABUSE_SURBL(5.50)[seotips.co.za.multi.surbl.org]; R_DKIM_ALLOW(0.00)[seonews.co.za:s=mailer]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PRECEDENCE_BULK(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.984,0]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; BAD_REP_POLICIES(0.10)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; FORGED_SENDER_MAILLIST(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 09:28:22 -0000 =20 June 2019 - SEO News & Tips=20 Hi Guys,=20 We all need to dir= ect traffic to our websites. And not only direct existing customers to ou= r websites but new potential customers as well. In this email I would lik= e to introduce to you an amazing 205 point ultimate S.E.O strategy.=20 = 1. Myth of the Aging Domain Google engineer, Matt Cutts claims that in= the Google algorithm, domain age is an insignificant factor. Good cont= ent matters more than the domain age in the long run.=20 2. Use Keyword = as First Word of Domain Get the extra edge over others by starting the do= main name with the targeted keyword. This is a crucial and an indisputabl= e keyword ranking factor that can boost your site=E2=80=99s ranking on th= e search engines.=20 3. Keywords in Title Keeping the keywords in the ti= tle is a smart move if you are looking to increase your SEO ranking. This= can be a strong on page SEO signal to boost page ranking.=20 4. Title= Tag Starting with Keyword According to Moz data and Backlinko, title tag= s having keywords at the beginning perform much better than when the keyw= ords are used at the end of the title tag.=20 5. Keywords in Description= Using keywords in descriptions is quite relevant and does make a differe= nce, although it isn=E2=80=99t hugely important.=20 Please let us know= if we can send you the rest of the strategy.=20 Thank you. And have a g= reat day further.=20 Matthew Gathercole Bright House Solutions Tel= : (011) 764 1551 Cell: 072 185 7703 Email: matthew@seotips.co.za W= ebsite: www.seotips.co.za http://www.seotips.co.za =C2=A0 Unsubscribe = http://seonews.co.za/account/index.php/lists/rn460m07z1d0a/unsubscribe/je16= 8zlvje522/hm4047x1kw08a =C2=A0=20 =20 From owner-freebsd-arm@freebsd.org Wed Aug 7 09:29:34 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F1193C4544 for ; Wed, 7 Aug 2019 09:29:34 +0000 (UTC) (envelope-from 0102016c6b646749-aa191eda-2e08-4c05-be12-f4312c5371db-000000@eu-west-1.amazonses.com) Received: from a6-46.smtp-out.eu-west-1.amazonses.com (a6-46.smtp-out.eu-west-1.amazonses.com [54.240.6.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 463R6P53Z0z4SRt for ; Wed, 7 Aug 2019 09:29:33 +0000 (UTC) (envelope-from 0102016c6b646749-aa191eda-2e08-4c05-be12-f4312c5371db-000000@eu-west-1.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn; d=amazonses.com; t=1565169838; h=Message-ID:Date:Subject:From:To:MIME-Version:Content-Type:List-Unsubscribe:Feedback-ID; bh=pEalcbfnu3zr7FXsP7BLU+JJ7fdopXfGqXaMsMu68Os=; b=UFLsFaFW6lYCTU3IA+1BT1JmIDrqg35S1FKd/JRaYvLIuAyyJmOLAWsZDzVNL+uB L7xKYR5mgIJG2iM9b+tbWyxAZILGBTTLhPdY0SsBWY/TnMiA1L9f6NahekHMi3fkz27 k3e3eaqIkBlcoJpSCvkYR2eRB9G6VqHkwhF0HZI8= Message-ID: <0102016c6b646749-aa191eda-2e08-4c05-be12-f4312c5371db-000000@eu-west-1.amazonses.com> Date: Wed, 7 Aug 2019 09:23:57 +0000 Subject: Smashing Savings! From: Snatcher Deals To: freebsd-arm@freebsd.org MIME-Version: 1.0 X-EmailOctopus-Version: 3 X-EmailOctopus-Started-Preparing-At: 2019-08-07T09:14:20+00:00 X-EmailOctopus-Ses-Configuration-Set-Name: emailoctopus-92ac08625b86fcb74e8dc6e633188d55 X-EmailOctopus-Sent-At: 2019-08-07T09:23:57+00:00 X-EmailOctopus-Parent-Type-Id: campaign X-EmailOctopus-Parent-Id: d1a9f9ef-b8f1-11e9-9307-06b4694bee2a X-EmailOctopus-List-Id: 196ba77e-b8ee-11e9-9307-06b4694bee2a X-EmailOctopus-List-Contact-Id: 6065b071-b8ee-11e9-9307-06b4694bee2a X-SES-Outgoing: 2019.08.07-54.240.6.46 Feedback-ID: 1.eu-west-1.S9D/OG//uxqWxLXWwJC1jmPHR4F3B2r9y7EKQ4EbeeU=:AmazonSES X-Rspamd-Queue-Id: 463R6P53Z0z4SRt X-Spamd-Bar: ++++++++++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=amazonses.com header.s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn header.b=UFLsFaFW; dmarc=none; spf=pass (mx1.freebsd.org: domain of 0102016c6b646749-aa191eda-2e08-4c05-be12-f4312c5371db-000000@eu-west-1.amazonses.com designates 54.240.6.46 as permitted sender) smtp.mailfrom=0102016c6b646749-aa191eda-2e08-4c05-be12-f4312c5371db-000000@eu-west-1.amazonses.com X-Spamd-Result: default: False [10.46 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18:c]; ZERO_FONT(0.10)[1]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[amazonses.com:+]; SUBJECT_ENDS_EXCLAIM(0.00)[]; FORGED_SENDER(0.30)[mailer@snatcherdeals.co.za,0102016c6b646749-aa191eda-2e08-4c05-be12-f4312c5371db-000000@eu-west-1.amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(0.63)[ip: (5.91), ipnet: 54.240.0.0/21(-1.38), asn: 16509(-1.35), country: US(-0.05)]; ASN(0.00)[asn:16509, ipnet:54.240.0.0/21, country:US]; FROM_NEQ_ENVFROM(0.00)[mailer@snatcherdeals.co.za,0102016c6b646749-aa191eda-2e08-4c05-be12-f4312c5371db-000000@eu-west-1.amazonses.com]; R_PARTS_DIFFER(0.39)[69.6%]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[amazonses.com:s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HTML_SHORT_LINK_IMG_1(2.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[snatcherdeals.co.za]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; R_SUSPICIOUS_IMAGES(3.58)[]; MANY_INVISIBLE_PARTS(1.00)[10]; NEURAL_SPAM_SHORT(0.97)[0.971,0]; NEURAL_SPAM_MEDIUM(1.00)[1.000,0]; NEURAL_SPAM_LONG(1.00)[0.999,0]; RCVD_IN_DNSWL_NONE(0.00)[46.6.240.54.list.dnswl.org : 127.0.15.0]; GREYLIST(0.00)[pass,body] X-Spam: Yes Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 09:29:35 -0000 Up to 80% Discount=C2=A0 Snatch Now!=20 Smashing Savings! View this email in your browser [https://berrima.eomail1.com/web-version?lc=3D6065b071-b8ee-11e9-9307-06b46= 94bee2a&p=3Dd1a9f9ef-b8f1-11e9-9307-06b4694bee2a&pt=3Dcampaign&t=3D15651698= 37&s=3D842b12f8a3546df23508f76a2f435b59c285fd0fb796c34745fa4bf993284ca0] =09=09[Snatcher-Sign-1%20(002).jpg] [https://snatcher.co.za/collections/snatch-of-the-week] [Product%20Blue.png] [https://snatcher.co.za/products/16-mp-hd-digital-video-camera]=20 [snatcher-1500x750-KILLER.jpg] [https://snatcher.co.za/products/magic-stretchy-sand]=20 [Product%20Black.png] [https://snatcher.co.za/products/fake-dummy-camera-dome-waterproof-ir-led-s= ecurity-camera] =09=09 [Product%20Blue%20(1).png] [https://snatcher.co.za/products/cx-70-transformable-mini-bat-drone] =09=09 [Product%20Blue%20(2).png] [https://snatcher.co.za/products/6-piece-kitchen-gadget-set] =09=09 [Product%20Black%20(1).png] [https://snatcher.co.za/products/5l-collapsible-water-tank] =09=09 [Product%20Black%20(4).png] [https://snatcher.co.za/products/18w-nail-uv-led-lamp]=20 [Product%20Black%20(2).png] [https://snatcher.co.za/products/7-day-pill-organiser] =09=09 [Product%20Blue%20(3).png] [https://snatcher.co.za/products/king-kong-multi-functional-shovel] =09=09 [Product%20Blue%20(4).png] [https://snatcher.co.za/products/foldable-and-portable-backpack] =09=09 [Product%20Black%20(3).png] [https://snatcher.co.za/products/key-ninja-multi-tool] =09=09 [Product%20Blue%20(5).png] [https://snatcher.co.za/products/can-do-compact-can-opener] =09=09 [Product%20Black%20(5).png] [https://snatcher.co.za/products/cute-corn-led-night-light] =09=09 [Product%20Blue%20(6).png] [https://snatcher.co.za/products/kids-hobby-horses] =09=09 [Product%20Blue%20(7).png] [https://snatcher.co.za/products/emoji-ceramic-money-bank] =09=09 [Product%20Black%20(6).png] [https://snatcher.co.za/products/fluffy-flamingo-slippers] =09=09 =09=09 VIEW MORE DEALS! [https://snatcher.co.za/collections/best-selling-products] Unsubscribe from this list [https://berrima.eomail1.com/unsubscribe?l=3D196ba77e-b8ee-11e9-9307-06b469= 4bee2a&lc=3D6065b071-b8ee-11e9-9307-06b4694bee2a&p=3Dd1a9f9ef-b8f1-11e9-930= 7-06b4694bee2a&pt=3Dcampaign&spa=3D1565169260&t=3D1565169837&s=3D43896261dc= edfd05afc3b0a993b16f56f66cecc4b3bca8bd13fcaf8ea0f28282] Email Powered By Snatcher [https://snatcher.co.za/]=20 [https://snatcher.co.za/] From owner-freebsd-arm@freebsd.org Wed Aug 7 12:27:35 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2C426A9A95 for ; Wed, 7 Aug 2019 12:27:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 463W3q0Pt8z4fX8 for ; Wed, 7 Aug 2019 12:27:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E5118C993 for ; Wed, 7 Aug 2019 12:27:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x77CRYbb063804 for ; Wed, 7 Aug 2019 12:27:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x77CRYgj063803 for freebsd-arm@FreeBSD.org; Wed, 7 Aug 2019 12:27:34 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 239693] [patch] arm/axp81x: Switch to iicdev_readfrom/writeto Date: Wed, 07 Aug 2019 12:27:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hslester96@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 12:27:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239693 Bug ID: 239693 Summary: [patch] arm/axp81x: Switch to iicdev_readfrom/writeto Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Some People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: hslester96@gmail.com Created attachment 206330 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206330&action= =3Dedit axp81x patch Use iicdev_readfrom/writeto to shrink the code size. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Aug 7 14:57:42 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CFCDAACD87 for ; Wed, 7 Aug 2019 14:57:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 463ZP24w35z3Jyn for ; Wed, 7 Aug 2019 14:57:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8B0A6E4A1 for ; Wed, 7 Aug 2019 14:57:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x77EvgME098196 for ; Wed, 7 Aug 2019 14:57:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x77EvgDP098195 for freebsd-arm@FreeBSD.org; Wed, 7 Aug 2019 14:57:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 239697] [patch] arm/am335x: Switch to iicdev_readfrom/writeto Date: Wed, 07 Aug 2019 14:57:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hslester96@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 14:57:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239697 Bug ID: 239697 Summary: [patch] arm/am335x: Switch to iicdev_readfrom/writeto Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Some People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: hslester96@gmail.com Created attachment 206333 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206333&action= =3Dedit am335x patch Use iicdev_readfrom/writeto to shrink the code size. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Aug 7 16:53:55 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7E1CDB0B1A for ; Wed, 7 Aug 2019 16:53:55 +0000 (UTC) (envelope-from rwa@athabascau.ca) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750084.outbound.protection.outlook.com [40.107.75.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 463cz500gyz40fY for ; Wed, 7 Aug 2019 16:53:52 +0000 (UTC) (envelope-from rwa@athabascau.ca) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UMUqDLrdDvrJdQI9oxPNunbIS2Bd7cUTyM67Un/Y3v4wq8hOMNpr7812GCnCdIachKRWMMl977Iv5V4qW4C5PXYHwa/yP6l80PsinWR3EVcHKIcgqHyJ28jC9xEJ/5BfsMa+eB1+4TItOHh41JC4E/GBQmKoSV96K2++SBdUXC9A6SRQZ+Xsx4DCgkOP8jmeFjCns+X/lpRw1pzp4VEqnmlAGgu0Y56jdRuidbUV3Dm/Dtklfq8+o4ZaWL01KY2UMD/vYZuB/P/2NuliKQfPcH9WPs2j8d8QoVUsy4X5SJQS/qt6bZQFoQBRM2pGoyrw7sVRv9Ak8GSGRsXH7LXA6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=N1gdR1fSoeoP96Ks0Zdkizt1Cip+18ALEXnXaBeZNfs=; b=IiP69oIStu2p0EivSh1ZDOpZ/fh85hAskthOb/qaqSrvXKY20wpXn09dVSQE4uRsoto4V6Zf8b/6mzbcPVAFdEcnfUmqiSXMvmidve3B2ZZJy4G0skLDo30zUn24/lul7Ovk3pqRcScGy2cx/iaA4LmXDN+5aUcbu5ccE9YxFyXuhJDeoZRcYAi/X5auEYD4eU3L3WSSXxJBXD3csmy+IQd6clSGwhwRnr5zLsuZk0DzmaRJ1n2BZF4G6vpHoEkHhvO7594KCEQ8nen8gQwnl2pOKcu7gt9z6jFq/PDEyteXnzANWGpQ2rZ1cAzc5dsWf62vSgTvUcufzp8jBhSrRg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 131.232.32.37) smtp.rcpttodomain=freebsd.org smtp.mailfrom=athabascau.ca; dmarc=bestguesspass action=none header.from=athabascau.ca; dkim=none (message not signed); arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=austaff.onmicrosoft.com; s=selector2-austaff-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=N1gdR1fSoeoP96Ks0Zdkizt1Cip+18ALEXnXaBeZNfs=; b=VpBduRUxlAUyQ4hY+klU1tu7MQBCHvppYO6C1dTIW34AE9W3D4WOIcJQtSp9FlG9h1QEIJmuNPbvhG3s9zUdAg68FE7fMM6kH+xYaiM7gSQoQb/BM/VJM7JjMGQQrf7nUECIid/v3o/42ewVN9YTd1hf9ptLVDuRz8mZ7f+3Qq0= Received: from CY4PR13CA0040.namprd13.prod.outlook.com (2603:10b6:903:99::26) by DM6PR13MB2684.namprd13.prod.outlook.com (2603:10b6:5:13b::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.11; Wed, 7 Aug 2019 16:53:50 +0000 Received: from QB1CAN01FT003.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5c::205) by CY4PR13CA0040.outlook.office365.com (2603:10b6:903:99::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.11 via Frontend Transport; Wed, 7 Aug 2019 16:53:49 +0000 Received-SPF: Pass (protection.outlook.com: domain of athabascau.ca designates 131.232.32.37 as permitted sender) receiver=protection.outlook.com; client-ip=131.232.32.37; helo=smtp-relay.cs.athabascau.ca; Received: from smtp-relay.cs.athabascau.ca (131.232.32.37) by QB1CAN01FT003.mail.protection.outlook.com (10.152.120.124) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.15 via Frontend Transport; Wed, 7 Aug 2019 16:53:48 +0000 Received: from autopsy.pc.athabascau.ca (autopsy.pc.athabascau.ca [131.232.4.80]) by smtp-relay.cs.athabascau.ca (Postfix) with ESMTPS id AB8CD20170 for ; Wed, 7 Aug 2019 10:53:47 -0600 (MDT) Date: Wed, 7 Aug 2019 10:53:47 -0600 (MDT) From: Ross Alexander X-X-Sender: rwa@autopsy.pc.athabascau.ca To: freebsd-arm@freebsd.org Subject: Re: Is it a good idea to use a usb-serial adapter for PPS? Yes, it is. Message-ID: User-Agent: Alpine 2.21.99999 (BSF 352 2019-06-22) Organization: Athabasca University MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:131.232.32.37; IPV:NLI; CTRY:CA; EFV:NLI; SFV:NSPM; SFS:(10009020)(4636009)(346002)(136003)(376002)(396003)(39860400002)(2980300002)(189003)(199004)(186003)(23726003)(2906002)(8936002)(486006)(426003)(478600001)(8746002)(86362001)(26005)(336012)(50466002)(956004)(476003)(2351001)(246002)(8676002)(126002)(47776003)(7696005)(2361001)(70206006)(229853002)(70586007)(67846002)(55016002)(36916002)(6916009)(316002)(5660300002)(786003)(58126008)(6246003)(6266002)(305945005)(356004)(106002)(7636002)(14444005)(102196002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR13MB2684; H:smtp-relay.cs.athabascau.ca; FPR:; SPF:Pass; LANG:en; PTR:vs001lpmp1609.cs.athabascau.ca; MX:1; A:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 20dd8b0b-d9b2-4724-3d7c-08d71b57d1a6 X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(4709080)(1401327)(2017052603328); SRVR:DM6PR13MB2684; X-MS-TrafficTypeDiagnostic: DM6PR13MB2684: X-Microsoft-Antispam-PRVS: Content-Transfer-Encoding: quoted-printable X-MS-Oob-TLC-OOBClassifiers: OLM:9508; X-Forefront-PRVS: 01221E3973 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: nrg2ne5yYByM0VD8+3qziewkeNU5Me4L4oFu7bm1urcP+vnd9o2xfng0B77AFRpsivmnUqDfqwX5VtS9OGJyi7h2UUZmJqhFIFwXpBQyqodbq5Oqfhk8s0LcH9Yl6igYnXftWBIwDw/NnngVUCArCdP3jeS3KzS4W9QGAhQ7iIwXz4WQGjFZLehHNAJV+Kpr/UoaV2ynlmx4kelHBOGGUMFlj3hdNEKvuO8zK5/EHZWnoOKA9c0fRAVBLugFnWvt6fj/I6vtMzjx91NWsgnWk98Xp+EqehXJjEjRLnp8Ixbh1AqCK9GNlzqA38Sk4wkMLoxdFjagddJS93TaqYZfjYXyj0edbS5Wd3BhDI40k8HPAizJlndSVIp5RbgSgt7j0sx0W1XKILJhfQZ81WImEXMN9bboYlNfzEttmxT5PpQ= X-OriginatorOrg: athabascau.ca X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Aug 2019 16:53:48.4818 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 20dd8b0b-d9b2-4724-3d7c-08d71b57d1a6 X-MS-Exchange-CrossTenant-Id: a893bdd2-f460-4252-aa34-4d057436a09d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=a893bdd2-f460-4252-aa34-4d057436a09d; Ip=[131.232.32.37]; Helo=[smtp-relay.cs.athabascau.ca] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR13MB2684 X-Rspamd-Queue-Id: 463cz500gyz40fY X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=austaff.onmicrosoft.com header.s=selector2-austaff-onmicrosoft-com header.b=VpBduRUx; dmarc=none; spf=pass (mx1.freebsd.org: domain of rwa@athabascau.ca designates 40.107.75.84 as permitted sender) smtp.mailfrom=rwa@athabascau.ca X-Spamd-Result: default: False [-4.63 / 15.00]; FAKE_REPLY(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[austaff.onmicrosoft.com:s=selector2-austaff-onmicrosoft-com]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; DMARC_NA(0.00)[athabascau.ca]; DKIM_TRACE(0.00)[austaff.onmicrosoft.com:+]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; RCVD_IN_DNSWL_NONE(0.00)[84.75.107.40.list.dnswl.org : 127.0.3.0]; IP_SCORE(-1.13)[ipnet: 40.64.0.0/10(-3.33), asn: 8075(-2.28), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; ARC_ALLOW(-1.00)[i=1]; SUBJECT_HAS_QUESTION(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 16:53:55 -0000 In Message-ID: , someone wrote [sorry, attrib trail is a little blurry ed.]: >> Most people are not worried about their kernel clock being 200 >> microseconds off from UTC, even if they're using the PPS signal from a >> GPS receiver. So I think most people should feel completely at ease >> using a USB serial adapter as the input device for a PPS signal. Some people do worry, although getting PPS to work over USB is a fine first step and I'm grateful for the breadcrumb trail. I would really like to get my NTP strat 0 machines off of Linux, just because. regards, Ross =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Ross Alexander, (780) 675-6823 desk / (780) 689-0749 cell, rwa@athabascau.c= a 54.71593 N 113.30835 W Order is simply a thin, perilous condition we try to impose on the basic reality of chaos. -- William Gaddis, _J R_ -- This communication is intended for the use of the recipient to whom it is a= ddressed, and may contain confidential, personal, and or privileged informa= tion. Please contact us immediately if you are not the intended recipient o= f this communication, and do not copy, distribute, or take action relying o= n it. Any communications received in error, or subsequent reply, should be = deleted or destroyed. --- From owner-freebsd-arm@freebsd.org Thu Aug 8 20:26:51 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1F76DB1BBA for ; Thu, 8 Aug 2019 20:26:51 +0000 (UTC) (envelope-from per@hedeland.org) Received: from outbound1f.eu.mailhop.org (outbound1f.eu.mailhop.org [52.28.59.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 464KfK6Q3Gz4pq0 for ; Thu, 8 Aug 2019 20:26:49 +0000 (UTC) (envelope-from per@hedeland.org) ARC-Seal: i=1; a=rsa-sha256; t=1565296007; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=IO/1Ak/HMSLjkqikdA3tF/nzRMCYPi3R7usa97jW/C2UTIDpbC23ua7qdFey4sE4HQgm42ygCDaOd O0esPpIAw+VXu9ZLJ+Va59gQBIgsb6lmL4xKMjcuTfheEdn+28kk6ob2TdwzNUxU9i8BFY/lqNfL7+ Knas6B8/NcQ6vH8p2IE9BqrifopQdK7Wnin2TyLPUlHEdEJFEhl11+9a0/dxhvrQQE/2NbYhs1VGQ9 5ed/kWXGqB1oOph8ZNGcAyJCIyuL7Urbu0eMpOKuRNUsbZYAkVzDxpltvWNs7AFAePor6THjJRgP28 OSLiHSLGyU9+nFmfqWi4+e5FasNw30w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:content-type:in-reply-to:mime-version:date: message-id:from:references:to:subject:dkim-signature:from; bh=m/DAA4eBdCMQg2H+Rzpf5+PD2Eq7XwGbI36LWqHnuNA=; b=jg1uFVWALj2E5FN3x3Iahyakjazzgo4D6Tv4QHFMMSEuXqSV17MEHDT5Zl7UJ9MweBjZMRC8Zm1z7 2TwbFnSWrtvEav3sT/2vA0xA42zowds5019WI03qjh5N6yTSy3/F6tpP8YxqmENzTQKA8vkvV+34Ct jWFQtFTQNq8bDSz1QypA6ApzZMpJIHQRkAOxSMucv+n2RIKDhtaivSN0ISHAnIEv/CoFfC9tOgIAQN LCkD3xT7p0/Jp7Z1CQIEO8RImH9fDzw80jHify7U55UvN8RYdncQ/oqP2yRtfzHoVk5MucLyaiKApy jDCxeq5RirlXuwkoB5SFDsQ6Eamlnvg== ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=none smtp.mailfrom=hedeland.org smtp.remote-ip=81.228.157.209; dmarc=none header.from=hedeland.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:content-type:in-reply-to:mime-version:date: message-id:from:references:to:subject:from; bh=m/DAA4eBdCMQg2H+Rzpf5+PD2Eq7XwGbI36LWqHnuNA=; b=QjBCyCJv5g3sWMiPK8CUOViJA9IL2Qr0/XXIIXgD42sC+jBAy08JNsS0oHU7fv0Nm89e/BP3dnD95 3in3aNx3Hk8zvTbhOOOuTv/0Oz9kcGi++dzQnAeQR1kmpJbS/WN83G4sa/tOKhk9yEnST9BDfcrMge IBVhLXYqyuj+8AUt9/jKK4BUsjJ+/4+IbR7d9tgvWcckL5T+ofLIpulKP/SltwVA9/OUQlWUVGI7sF wgp/mPlF5nHWJNHkup20mJtabwf3qQX1cy0ux/ZRRf+XmkWO2c7bGFJ0CwkXN/W6xNTcsCP2juI6mm LsGZXzQI/s5lTAIHcYmRwwGxM5SoTUQ== X-MHO-RoutePath: cGVyaGVkZWxhbmQ= X-MHO-User: d739b7ba-ba1a-11e9-a203-f5e3bb5d0a28 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 81.228.157.209 X-Mail-Handler: DuoCircle Outbound SMTP Received: from hedeland.org (unknown [81.228.157.209]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id d739b7ba-ba1a-11e9-a203-f5e3bb5d0a28; Thu, 08 Aug 2019 20:26:46 +0000 (UTC) Received: from pluto.hedeland.org (pluto.hedeland.org [10.1.1.5]) by tellus.hedeland.org (8.15.2/8.15.2) with ESMTPS id x78KQibU013892 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 8 Aug 2019 22:26:45 +0200 (CEST) (envelope-from per@hedeland.org) Subject: Re: Is it a good idea to use a usb-serial adapter for PPS? Yes, it is. To: freebsd-arm@freebsd.org References: From: Per Hedeland Message-ID: <69a9bed3-4d0a-f8f6-91af-a8f7d84ee307@hedeland.org> Date: Thu, 8 Aug 2019 22:26:44 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 464KfK6Q3Gz4pq0 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=outbound.mailhop.org header.s=dkim-high header.b=QjBCyCJv; dmarc=none; spf=none (mx1.freebsd.org: domain of per@hedeland.org has no SPF policy when checking 52.28.59.28) smtp.mailfrom=per@hedeland.org X-Spamd-Result: default: False [-5.51 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_XOIP(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[outbound.mailhop.org:+]; NEURAL_HAM_SHORT(-0.97)[-0.968,0]; RECEIVED_SPAMHAUS_PBL(0.00)[209.157.228.81.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_ALLOW(-1.00)[i=1]; IP_SCORE(-1.25)[ipnet: 52.28.0.0/16(-4.83), asn: 16509(-1.35), country: US(-0.05)]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[outbound.mailhop.org:s=dkim-high]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[hedeland.org]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country:US]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[28.59.28.52.list.dnswl.org : 127.0.20.0]; R_SPF_NA(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2019 20:26:51 -0000 On 2019-08-07 18:53, Ross Alexander wrote: > In Message-ID: , > someone wrote [sorry, attrib trail is a little blurry ed.]: > >>> Most people are not worried about their kernel clock being 200 >>> microseconds off from UTC, even if they're using the PPS signal from a >>> GPS receiver. So I think most people should feel completely at ease >>> using a USB serial adapter as the input device for a PPS signal. > > Some people do worry, although getting PPS to work over USB is a fine > first step and I'm grateful for the breadcrumb trail. For those that do worry, you can of course tell ntpd to correct for a semi-fixed offset (via the 'time1' option to the 'fudge' command) - once you know how large the offset is... More important is a low jitter, and 20-30 microseconds seems quite good. @Ian, maybe it would make sense to post your test report to some NTP forum, e.g. the comp.protocols.time.ntp newsgroup? I guess most readers of freebsd-arm@ have little interest in using a usb-serial adapter if they can simply use a gpio pin, with better results - but for PCs and the like, that no longer have serial ports, it could be very useful. Just last week there was a post or two to the newsgroup re-asserting the oft-repeated claim that using a usb-serial adapter for PPS is completely useless ("USB-to-RS-232 converters generally completely loose the precision timing abilities of traditional serial port circuits..."). --Per From owner-freebsd-arm@freebsd.org Fri Aug 9 15:28:12 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3A69DCB709 for ; Fri, 9 Aug 2019 15:28:12 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 464pzH60p4z3CNr for ; Fri, 9 Aug 2019 15:28:11 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1565364490; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=pU6biDYyd4L1QpflDD2nx84YkdbedditiEixTaS9ipnkKI3MY2vh7dwr1ZAxWir0xd0STDkEXKHrI x715chn6c5FRqON6nEcUuuEBfNbUGJvLAd25+KryQ5lOFfpQzLH98AsJ989D4tlLDI3JVd/MnQDXPa bGpUM1aRHw4plUZrEMc+0D+ICT998EWNiH6sVANyaDKe31B4MeWuJjp3q/fvmizCtvPm5LKsZuldjE 9+fmP2AsHsZGiKd+zzMIYzpbz2K/qHGSUjPGoTAwPvCbp8bY+RPUj5EShtuMVEk+ROnwxGS+Hxsewk mSLjf5G8X/a9in40EwKPoyKL1vQFzqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=2CN8q8oDT9r2pHrWlGwlXx5s1SKjK8GJ4rRa43CCq/Q=; b=OHQtCX43NZ57ZcXEYqH4suG4BiK81opg2gEJJU/JCtUHopzgi+3ssd2e10JkHjbpHYof0yd6nsYfu 3NveVd13UqdGaDmaREuZZnPDnsITAmamRydlUFAgv1eKYHYoXv/czqj1/W8Q3NxWDUU1oJmo1SUOyq c2KKJuNRNBLfNs7lt+M4hRy+5/F4Qp6wUwxzojJzsTMGe0+Ge2z2qG98c9kzk85p3eoabp8AddcSkb lTYC4tlNse1KXCu+D9NqC13K19pzMtH+q5JpueMF4WXmAPBOXYISUxH/EHPgoWLGLPxqDfdwuS0l9R dfA7qLk2/Rjn4k34C9f+SHvzmmxlHcA== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=2CN8q8oDT9r2pHrWlGwlXx5s1SKjK8GJ4rRa43CCq/Q=; b=nDZpEKsEW9QiSk2LSOsKks/PeF40dFoiwbUDP+vT9nwcs+vv4rua4FkY/GazDwOLyAWdymj2W4afY RGQl6cHg2uclJQ8Wjm3N9Hs9gA/qBZLQmP5eYv9Bt9E74AMagI1SrYasTAfBAohOfQiKKTnpOBSTq/ Sq6OD3O6IKE49dJFjxrUlW5jk+wRVo35TbPa6rXwMj3bn7DK4Fn6caahOmTQQdOOhvRsOaHo5MLrqU kHEMkLYW6ByOBQnD6LA7wUlzuV1YZbPZ+dPLq7ehuyJvLTVwqb/Ju8e0VZghh9CDzhebxlLxArlc9Y 8ZwxYFvq6NDrsz2vttg0C1U2mnze2Vg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 4968a9fb-baba-11e9-85ec-13b9aae3a1d2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 4968a9fb-baba-11e9-85ec-13b9aae3a1d2; Fri, 09 Aug 2019 15:28:08 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x79FS6TS034173; Fri, 9 Aug 2019 09:28:06 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <345bae77417c2495f55799b4c7ca2784f4ece9ed.camel@freebsd.org> Subject: Re: Is it a good idea to use a usb-serial adapter for PPS? Yes, it is. From: Ian Lepore To: Per Hedeland , freebsd-arm@freebsd.org Date: Fri, 09 Aug 2019 09:28:06 -0600 In-Reply-To: <69a9bed3-4d0a-f8f6-91af-a8f7d84ee307@hedeland.org> References: <69a9bed3-4d0a-f8f6-91af-a8f7d84ee307@hedeland.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 464pzH60p4z3CNr X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2019 15:28:12 -0000 On Thu, 2019-08-08 at 22:26 +0200, Per Hedeland wrote: > On 2019-08-07 18:53, Ross Alexander wrote: > > In Message-ID: , > > someone wrote [sorry, attrib trail is a little blurry ed.]: > > > > > > Most people are not worried about their kernel clock being 200 > > > > microseconds off from UTC, even if they're using the PPS signal > > > > from a > > > > GPS receiver. So I think most people should feel completely at > > > > ease > > > > using a USB serial adapter as the input device for a PPS > > > > signal. > > > > Some people do worry, although getting PPS to work over USB is a > > fine > > first step and I'm grateful for the breadcrumb trail. > > For those that do worry, you can of course tell ntpd to correct for a > semi-fixed offset (via the 'time1' option to the 'fudge' command) - > once you know how large the offset is... More important is a low > jitter, and 20-30 microseconds seems quite good. > > @Ian, maybe it would make sense to post your test report to some NTP > forum, e.g. the comp.protocols.time.ntp newsgroup? I guess most > readers of freebsd-arm@ have little interest in using a usb-serial > adapter if they can simply use a gpio pin, with better results - but > for PCs and the like, that no longer have serial ports, it could be > very useful. > > Just last week there was a post or two to the newsgroup re-asserting > the oft-repeated claim that using a usb-serial adapter for PPS is > completely useless ("USB-to-RS-232 converters generally completely > loose the precision timing abilities of traditional serial port > circuits..."). > I posted to arm@ because a discussion here recently brought up the usb- serial performance questions, and also because I used arm hardware to craft a somewhat unique measurement apparatus for it. I have resisted joining any timing-geek newsgroups or forums for years, because it's what I do for a living as well as being a hobby, and I've always felt it would just suck another hour a day of my time if I belonged to more groups/forums that might interest me that much. :) -- Ian From owner-freebsd-arm@freebsd.org Fri Aug 9 19:36:17 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C184FCFB32 for ; Fri, 9 Aug 2019 19:36:17 +0000 (UTC) (envelope-from per@hedeland.org) Received: from outbound1f.eu.mailhop.org (outbound1f.eu.mailhop.org [52.28.59.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 464wTX4vkbz3R5y for ; Fri, 9 Aug 2019 19:36:16 +0000 (UTC) (envelope-from per@hedeland.org) ARC-Seal: i=1; a=rsa-sha256; t=1565379375; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=plz/ZL9590Cf8ISbszgPVN79PlaThG94/+B2RTY6ObZY2rZ8vAQ0VKch2nYeI3+uBjYqqPcEmFRqf R0AgBkUwwDE+AQnZuVOH7dNB6sfV66bsuSsPHucSCS1W3/1XkQBt3KMPoynhcWzdSToFKcOFxf7qxA nZEKlg6B9oJsezFKurBP3F6S6yrLgjkdD2FgQGB4XGfRn/ZKEP/QxWrdV8fQIFSebWJd/S3NhINeXk t+zHAfArHqE6pWaMQYY4/b49+zjMpNZrJvSsrDhdOG5YJAplI4Vl640BRYjBeK0R0qkND3HGpa9sie U3T2wx+z6IPUqVLNvQ/fW64pkFDzUPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:content-type:in-reply-to:mime-version:date: message-id:from:cc:references:to:subject:dkim-signature:from; bh=o2/oDp1xxmOYG059mHBzfNx5i2RdVJt1Wu8KYTZD6Qc=; b=dTlOgndXMTF2sUsF2XUoceBwXg9v2k+TV5bLU7Bgsj8zu/dwsezdI2M2I/jYxNCA/Twckg1GNs5WA Fdem4V7B/UA+R7+lwGBjkCKkU14pRPVnlV1MIHxTEpjkaH87X8V+UTOz6QUVvFR2C0lvInDAwLdsdh xjAxsQ84jjduB86wgWkrGtMEcUvP2H2jkZaGLSY+cfmDb+WIvABzJc8ODNjK/FfDjJPmOLfO7cn9OG gb4jEzFfdnNs+omwwLp9wQ/3zg3g9de9Ak6/f7NN2Fyqsn1BmfJqAz2HWhAIa623PrHlmLwm8bWfsS RPdYZchtVTRR/jYcgBUBisiZBo1gMBQ== ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=none smtp.mailfrom=hedeland.org smtp.remote-ip=81.228.157.209; dmarc=none header.from=hedeland.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:content-type:in-reply-to:mime-version:date: message-id:from:cc:references:to:subject:from; bh=o2/oDp1xxmOYG059mHBzfNx5i2RdVJt1Wu8KYTZD6Qc=; b=RrYSnqxmQekQef/UPSgRbGmfprOPGQwMfgzmRA6DsBdlOWkDjYpZ66skkESAmE6E427IJVNZjstz6 FsJfNFPoFSojcXIjljRGA8erqTf7gF+pfNQUaAXosmiIF1Skms4HoViRp53eL9ufau+p1zH3rLw4GV 1UUqwt5uS34OJAT+5NhbBIlaUruWHlTH6xWepFxBxBrNBR6M9pdme1euTR4UB1aGgGPA+AIo95paUT iZiCjHrctDQ13T1kYlzCN4AgigcAkFVK5eQB8du1jtAITm6KxMC2w+ij7MMcawIeTRMldqXPziQ060 XLgy845SEgF8pGyqOolQC+fOIw8ZQXA== X-MHO-RoutePath: cGVyaGVkZWxhbmQ= X-MHO-User: f14e0e13-badc-11e9-a203-f5e3bb5d0a28 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 81.228.157.209 X-Mail-Handler: DuoCircle Outbound SMTP Received: from hedeland.org (unknown [81.228.157.209]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id f14e0e13-badc-11e9-a203-f5e3bb5d0a28; Fri, 09 Aug 2019 19:36:12 +0000 (UTC) Received: from pluto.hedeland.org (pluto.hedeland.org [10.1.1.5]) by tellus.hedeland.org (8.15.2/8.15.2) with ESMTPS id x79JaBi8019079 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 9 Aug 2019 21:36:11 +0200 (CEST) (envelope-from per@hedeland.org) Subject: Re: Is it a good idea to use a usb-serial adapter for PPS? Yes, it is. To: Ian Lepore References: <69a9bed3-4d0a-f8f6-91af-a8f7d84ee307@hedeland.org> <345bae77417c2495f55799b4c7ca2784f4ece9ed.camel@freebsd.org> Cc: freebsd-arm@freebsd.org From: Per Hedeland Message-ID: <7312032d-2908-9414-0445-6b442c3a02e5@hedeland.org> Date: Fri, 9 Aug 2019 21:36:11 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <345bae77417c2495f55799b4c7ca2784f4ece9ed.camel@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 464wTX4vkbz3R5y X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=outbound.mailhop.org header.s=dkim-high header.b=RrYSnqxm; dmarc=none; spf=none (mx1.freebsd.org: domain of per@hedeland.org has no SPF policy when checking 52.28.59.28) smtp.mailfrom=per@hedeland.org X-Spamd-Result: default: False [-5.54 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[outbound.mailhop.org:s=dkim-high]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[hedeland.org]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[outbound.mailhop.org:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[28.59.28.52.list.dnswl.org : 127.0.20.0]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; RECEIVED_SPAMHAUS_PBL(0.00)[209.157.228.81.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-1.25)[ipnet: 52.28.0.0/16(-4.85), asn: 16509(-1.35), country: US(-0.05)]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_ALLOW(-1.00)[i=1] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2019 19:36:17 -0000 On 2019-08-09 17:28, Ian Lepore wrote: > On Thu, 2019-08-08 at 22:26 +0200, Per Hedeland wrote: >> On 2019-08-07 18:53, Ross Alexander wrote: >>> In Message-ID: , >>> someone wrote [sorry, attrib trail is a little blurry ed.]: >>> >>>>> Most people are not worried about their kernel clock being 200 >>>>> microseconds off from UTC, even if they're using the PPS signal >>>>> from a >>>>> GPS receiver. So I think most people should feel completely at >>>>> ease >>>>> using a USB serial adapter as the input device for a PPS >>>>> signal. >>> >>> Some people do worry, although getting PPS to work over USB is a >>> fine >>> first step and I'm grateful for the breadcrumb trail. >> >> For those that do worry, you can of course tell ntpd to correct for a >> semi-fixed offset (via the 'time1' option to the 'fudge' command) - >> once you know how large the offset is... More important is a low >> jitter, and 20-30 microseconds seems quite good. >> >> @Ian, maybe it would make sense to post your test report to some NTP >> forum, e.g. the comp.protocols.time.ntp newsgroup? I guess most >> readers of freebsd-arm@ have little interest in using a usb-serial >> adapter if they can simply use a gpio pin, with better results - but >> for PCs and the like, that no longer have serial ports, it could be >> very useful. >> >> Just last week there was a post or two to the newsgroup re-asserting >> the oft-repeated claim that using a usb-serial adapter for PPS is >> completely useless ("USB-to-RS-232 converters generally completely >> loose the precision timing abilities of traditional serial port >> circuits..."). >> > > I posted to arm@ because a discussion here recently brought up the usb- > serial performance questions, and also because I used arm hardware to > craft a somewhat unique measurement apparatus for it. Oh, I certainly didn't intend to suggest that your message was off-topic, only that it deserved a wider audience. > I have resisted joining any timing-geek newsgroups or forums for years, > because it's what I do for a living as well as being a hobby, and I've > always felt it would just suck another hour a day of my time if I > belonged to more groups/forums that might interest me that much. :) I get your point - in particular posting a "controversial" message to any *-geek forum can be extremely time-consuming if you try to address all the responses it will generate. Personally, although I tinkered a lot with NTP back in the days when computers had serial ports, and even before they had Internet access, I can't say that I've ever qualified as a true timing-geek - I still follow the trickle of posts in the abovementioned newsgroup, but it was probably years since I last posted anything. Would you object to me posting an article with a *link* to your message (i.e. https://lists.freebsd.org/pipermail/freebsd-arm/2019-August/020263.html) in the newsgroup? --Per From owner-freebsd-arm@freebsd.org Fri Aug 9 20:17:24 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DF6F4A8F8F for ; Fri, 9 Aug 2019 20:17:24 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 464xP03P51z40hW for ; Fri, 9 Aug 2019 20:17:24 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1565381842; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=vJ2P53Y6/BG0igrgJSupthAtMdOVALqkwiYUm7QFX3091NUjx0oFc6AUdu+Nhr5ecHdg9N8O34Pq6 cMdzbpmFDc/IcOYctVWZlngB0akID5IldtvskgQTAojJbWji1bIOQI/jbIvUOqnuufyEBoxhydVIwi z5n7LKur1JOndiCoLXOG6RFzKU5JljlQ8dFMCceZV59xvK1V1TeDirFxtrqWsrY1vk6MPZIUApwdKk /M2egcI3VVdVWgjuF65xMaSjHaEun4SWE3MaeoFK3NTirr39qbw8Zbfld0ru6MDlAdH1Ie6Foh2gKF y9cuAEN1sdSGgCfecGlM0yDeihiF9ag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=TDmzXIXSWLx/sRb6rxABNk49ByXSmmAn+KuUsPvP5Cg=; b=ApbWFoe8uwR+blhbboXhaWOCrq0LJ8Dyq6VguEifQH8amykAOGclwnXHT6iN9Vs8pcwO8oLI7O7nl Gz+aBVKRfeSdq0CSRmFCnR5r/JW85bdm5aU2mBo8qmg0tpeXzZy1MI8QJPr8X2dARCqG+sYw812PMF PpBS8eKynAaeSMqlH1LIm2uLVZGzatQo/JqVmrk7VndsnuxiabYljwO/4vKGwjNkTi9WAb2gwINQpD qhpOsituBJCPwsbrkX5bacdMscLBmicW9QCK6MWEmMNbTTUmQ8gDVaGgyyJmiP28QEAa/9Q+jsw5bh 73t7o7HEhSM0A58hfaPNQrg/RbxpOKw== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=TDmzXIXSWLx/sRb6rxABNk49ByXSmmAn+KuUsPvP5Cg=; b=hEri20T7IpTgOT1Vno22VigHVpDCvGp55tgY/UrI3bfPsIcP4kcLfSZSwL1R0XegWWMPdnHRNgcNU hqPHIDo9RZFly1qjYZoO2o2FtmhHRdceNi3WoG9qmm3LnfXvhTOdAp7n95dev+yvlsO8/Cq9Jb1aOC LAC795Xjb5LR5zrnKsgzl5esMp2At0aVF7OpuiuxzfAcR434vBz4Z7lITv2wYstDaqoX2rtq7QRSt0 aAomJE9BLde8ULGa8sZ2k8r8ZJQLoUrvJSBV0/eIIyuNwkOqcuO7s2Y10q4JixKfxLpFtjD6BfQbOi mRJ46DZCzAAU+Ar0YAEjaYqk7Ta6hdA== X-MHO-RoutePath: aGlwcGll X-MHO-User: af1b3206-bae2-11e9-85ec-13b9aae3a1d2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id af1b3206-bae2-11e9-85ec-13b9aae3a1d2; Fri, 09 Aug 2019 20:17:21 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x79KHHK7035232; Fri, 9 Aug 2019 14:17:17 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <523b6f0a0fa5f2aeec298fa74df25d3c4af66acc.camel@freebsd.org> Subject: Re: Is it a good idea to use a usb-serial adapter for PPS? Yes, it is. From: Ian Lepore To: Per Hedeland Cc: freebsd-arm@freebsd.org Date: Fri, 09 Aug 2019 14:17:17 -0600 In-Reply-To: <7312032d-2908-9414-0445-6b442c3a02e5@hedeland.org> References: <69a9bed3-4d0a-f8f6-91af-a8f7d84ee307@hedeland.org> <345bae77417c2495f55799b4c7ca2784f4ece9ed.camel@freebsd.org> <7312032d-2908-9414-0445-6b442c3a02e5@hedeland.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 464xP03P51z40hW X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.986,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2019 20:17:24 -0000 On Fri, 2019-08-09 at 21:36 +0200, Per Hedeland wrote: > On 2019-08-09 17:28, Ian Lepore wrote: > > On Thu, 2019-08-08 at 22:26 +0200, Per Hedeland wrote: > > > On 2019-08-07 18:53, Ross Alexander wrote: > > > > In Message-ID: < > > > > B9EFA4D4-C1AD-4181-B421-F6BD53434FA5@dons.net.au>, > > > > someone wrote [sorry, attrib trail is a little blurry ed.]: > > > > > > > > > > Most people are not worried about their kernel clock being > > > > > > 200 > > > > > > microseconds off from UTC, even if they're using the PPS > > > > > > signal > > > > > > from a > > > > > > GPS receiver. So I think most people should feel > > > > > > completely at > > > > > > ease > > > > > > using a USB serial adapter as the input device for a PPS > > > > > > signal. > > > > > > > > Some people do worry, although getting PPS to work over USB is > > > > a > > > > fine > > > > first step and I'm grateful for the breadcrumb trail. > > > > > > For those that do worry, you can of course tell ntpd to correct > > > for a > > > semi-fixed offset (via the 'time1' option to the 'fudge' command) > > > - > > > once you know how large the offset is... More important is a low > > > jitter, and 20-30 microseconds seems quite good. > > > > > > @Ian, maybe it would make sense to post your test report to some > > > NTP > > > forum, e.g. the comp.protocols.time.ntp newsgroup? I guess most > > > readers of freebsd-arm@ have little interest in using a usb- > > > serial > > > adapter if they can simply use a gpio pin, with better results - > > > but > > > for PCs and the like, that no longer have serial ports, it could > > > be > > > very useful. > > > > > > Just last week there was a post or two to the newsgroup re- > > > asserting > > > the oft-repeated claim that using a usb-serial adapter for PPS is > > > completely useless ("USB-to-RS-232 converters generally > > > completely > > > loose the precision timing abilities of traditional serial port > > > circuits..."). > > > > > > > I posted to arm@ because a discussion here recently brought up the > > usb- > > serial performance questions, and also because I used arm hardware > > to > > craft a somewhat unique measurement apparatus for it. > > Oh, I certainly didn't intend to suggest that your message was > off-topic, only that it deserved a wider audience. > > > I have resisted joining any timing-geek newsgroups or forums for > > years, > > because it's what I do for a living as well as being a hobby, and > > I've > > always felt it would just suck another hour a day of my time if I > > belonged to more groups/forums that might interest me that much. :) > > I get your point - in particular posting a "controversial" message to > any *-geek forum can be extremely time-consuming if you try to > address > all the responses it will generate. > > Personally, although I tinkered a lot with NTP back in the days when > computers had serial ports, and even before they had Internet access, > I can't say that I've ever qualified as a true timing-geek - I still > follow the trickle of posts in the abovementioned newsgroup, but it > was probably years since I last posted anything. Would you object to > me posting an article with a *link* to your message > (i.e. > https://lists.freebsd.org/pipermail/freebsd-arm/2019-August/020263.html > ) > in the newsgroup? > > --Per > It might be better to use the link to the copy I sent to the freebsd- usb list, since it's more directly on-topic: https://lists.freebsd.org/pipermail/freebsd-usb/2019-August/016078.html I also think it would be wise to add a caveat that the results are for FreeBSD. I would expect linux performance to be similar. But for Windows, all bets are off; Windows drivers for usb-serial devices are said to vary wildly in quality depending on the vendor. -- Ian From owner-freebsd-arm@freebsd.org Sat Aug 10 11:19:38 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4260DB9C3E for ; Sat, 10 Aug 2019 11:19:38 +0000 (UTC) (envelope-from johannes@t-beutel.com) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1.freebsd.org (Postfix) with ESMTP id 465KQ13L99z4fCs for ; Sat, 10 Aug 2019 11:19:37 +0000 (UTC) (envelope-from johannes@t-beutel.com) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 6EEE510327CC0 for ; Sat, 10 Aug 2019 04:13:03 -0700 (MST) Date: Sat, 10 Aug 2019 04:13:03 -0700 (MST) From: tscho To: freebsd-arm@freebsd.org Message-ID: <1565435583431-0.post@n6.nabble.com> In-Reply-To: <49A81763-B197-4E66-BA8E-0804C680B842@gmail.com> References: <051F7682-B3EC-49D8-B52A-2A8C75BEE757@gmail.com> <9B48E915-C705-4582-837B-C92B40AD63EB@westryn.net> <7CDBFAF1-C36F-4A2D-8D80-CFF1F03CD2B9@deepcore.dk> <44E733F9-5DEB-4A7C-8369-7F6DF2AE03BE@gmail.com> <49A81763-B197-4E66-BA8E-0804C680B842@gmail.com> Subject: Re: Espressobin anyone ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 465KQ13L99z4fCs X-Spamd-Bar: +++++++++ X-Spamd-Result: default: False [9.99 / 15.00]; ARC_NA(0.00)[]; R_SPF_FAIL(1.00)[-all]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.33)[0.334,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.999,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.16)[ip: (0.59), ipnet: 162.255.20.0/22(0.20), asn: 21624(0.04), country: US(-0.05)]; VIOLATED_DIRECT_SPF(3.50)[]; NEURAL_SPAM_LONG(1.00)[1.000,0]; RCVD_IN_DNSWL_NONE(0.00)[37.23.255.162.list.dnswl.org : 127.0.10.0]; DMARC_POLICY_REJECT(2.00)[t-beutel.com : No valid SPF, No valid DKIM,reject]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:21624, ipnet:162.255.20.0/22, country:US]; MIME_TRACE(0.00)[0:+]; GREYLIST(0.00)[pass,body]; RCVD_COUNT_TWO(0.00)[2] X-Spam: Yes X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2019 11:19:38 -0000 Hi I received my Espressobin yesterday and tried to get FreeBSD running. Unfortunately I'm always stuck at the following: /boot/kernel/kernel text=0x94d3ac data=0x191d50+0x84ae94 syms=[0x8+0x13abb0+0x8+0x1260a6] No valid device tree blob found! WARNING! Trying to fire up the kernel, but no device tree blob found! Is there a chance that I got the wrong dtb file? Where did you get yours from? Johannes -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-arm-f4199244.html From owner-freebsd-arm@freebsd.org Sat Aug 10 15:11:38 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9816DBE99A for ; Sat, 10 Aug 2019 15:11:38 +0000 (UTC) (envelope-from soren.schmidt@gmail.com) Received: from mail-ed1-x543.google.com (mail-ed1-x543.google.com [IPv6:2a00:1450:4864:20::543]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 465QYh6935z3LB7 for ; Sat, 10 Aug 2019 15:11:36 +0000 (UTC) (envelope-from soren.schmidt@gmail.com) Received: by mail-ed1-x543.google.com with SMTP id w13so99033923eds.4 for ; Sat, 10 Aug 2019 08:11:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=qjuHVjniWH3Dxs/pxQC2JpqcBPOrgb3rK4QC+Fo7+h8=; b=lnGvMr2iZZ3MJVT6S4V6GfqAClrEFVD6TFVZ6X7rStXd1V77ITkbKPpB+SxEgMXPQd 04Xvbrws9QVj6+Q5KdlV2qL+sTcBMGeS7XW/hj0J3NG+MYsMBqYtIeLeh4LMUMMfHFDb xERV4pClvD/CGLV0ULYEp5SV13j4wXStrGuROLNKr1Of04p4EQha63LODy/BgxAxnbPg kJSuMzkWnjIfyHBKGH/Gl6OwB5SgeQyxRJGsm5q+1ZYUBaYP0JbkgC2OD4Vt4kWQNvB9 nIPJX5ESUgr076fb8CLUbFMYxC/VA86U4O+ymP5lQCG2Ock0YjUB1buh2wIluSQ5Ub9L Fczg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=qjuHVjniWH3Dxs/pxQC2JpqcBPOrgb3rK4QC+Fo7+h8=; b=MuDczVyIVM1A5JLbTnr0faLEPsAnzrc6pC0xKQFF/4175cFUKzYiqjQhj7LpMaN1o9 /YuamoJG/NDCvCQ3ARkUKe4RbakWon6KPyA3ydN45N2ML0gzLfEc0j11qymH8iDchZqC 5rwusqCfs4zpL9hGtbBd3/XL04vz/DAZXyLJn76Ei/rafp7P5URDyibtxnnxQz0wzpOn Ngr4G42GWJ/TfPOq/ITzPZY1DHkK6kPcsQtcA8i3G70WJ4agTg+8DiQcVQkD1UNSpRKy qbrOdZ9FxViX4pMdQG4jHeh8podtJKGNJlOkHJQl1wdUFyTkxp8iMJJP1YdACDhWEwLU IZxA== X-Gm-Message-State: APjAAAV+axokOIOkFLBwuy89zjXKZwn5chind+kGdKIAkUW6E2ToBtMe X76WCTF9NObGXVt3htx0bRZbCngQfD8= X-Google-Smtp-Source: APXvYqyqh23Z4aYP+PKMWNAzWLa2kOIDFQ3GMJYLfhcNT+5i7DtIRHknPeRGT+fLRv3EvhNcyk3g/g== X-Received: by 2002:a17:906:b345:: with SMTP id cd5mr1595256ejb.239.1565449894100; Sat, 10 Aug 2019 08:11:34 -0700 (PDT) Received: from mac.deepcore.dk ([85.27.186.9]) by smtp.gmail.com with ESMTPSA id se3sm16147339ejb.31.2019.08.10.08.11.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Aug 2019 08:11:33 -0700 (PDT) From: =?utf-8?Q?S=C3=B8ren_Schmidt?= Message-Id: <1F22D8DA-E583-4858-911F-F057EC1A30E0@gmail.com> Content-Type: multipart/signed; boundary="Apple-Mail=_D8CB4250-9FF4-4851-AEB8-F059455B7020"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Espressobin anyone ? Date: Sat, 10 Aug 2019 17:11:32 +0200 In-Reply-To: <1565435583431-0.post@n6.nabble.com> Cc: freebsd-arm@freebsd.org To: tscho References: <051F7682-B3EC-49D8-B52A-2A8C75BEE757@gmail.com> <9B48E915-C705-4582-837B-C92B40AD63EB@westryn.net> <7CDBFAF1-C36F-4A2D-8D80-CFF1F03CD2B9@deepcore.dk> <44E733F9-5DEB-4A7C-8369-7F6DF2AE03BE@gmail.com> <49A81763-B197-4E66-BA8E-0804C680B842@gmail.com> <1565435583431-0.post@n6.nabble.com> X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 465QYh6935z3LB7 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=lnGvMr2i; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of sorenschmidt@gmail.com designates 2a00:1450:4864:20::543 as permitted sender) smtp.mailfrom=sorenschmidt@gmail.com X-Spamd-Result: default: False [-4.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; HAS_ATTACHMENT(0.00)[]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (0.04), ipnet: 2a00:1450::/32(-3.05), asn: 15169(-2.40), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2019 15:11:38 -0000 --Apple-Mail=_D8CB4250-9FF4-4851-AEB8-F059455B7020 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi You need to build the .dtb file from what is in the source tree, not one = obtained from the net. I should work in -current (not tried, I use a heavy modified 12-stable). You should modify your env in the onboard u-boot to load the right = kernel and dtb. Something like: setenv fdt_name 'efi/boot/armada-3720-espressobin.dtb' setenv image_name 'efi/freebsd/loader.efi' setenv bootcmd 'mmc dev 0; fatload mmc 0:1 $kernel_addr = $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $kernel_addr = $fdt_addr' -S=C3=B8ren > On 10 Aug 2019, at 13.13, tscho via freebsd-arm = wrote: >=20 > Hi >=20 > I received my Espressobin yesterday and tried to get FreeBSD running. > Unfortunately I'm always stuck at the following: >=20 > /boot/kernel/kernel text=3D0x94d3ac data=3D0x191d50+0x84ae94 > syms=3D[0x8+0x13abb0+0x8+0x1260a6] > No valid device tree blob found! > WARNING! Trying to fire up the kernel, but no device tree blob found! >=20 > Is there a chance that I got the wrong dtb file? Where did you get = yours > from? >=20 > Johannes >=20 >=20 >=20 > -- > Sent from: = http://freebsd.1045724.x6.nabble.com/freebsd-arm-f4199244.html > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --Apple-Mail=_D8CB4250-9FF4-4851-AEB8-F059455B7020 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkC0kEuD0Me2xEj5EGvRMAY4qbRsFAl1O3qQACgkQGvRMAY4q bRsa9BAAoEJGELX2i7dcIkAnVmB9piT+VKzy2iUUoHfE9qaW+7V3m+j+guuVrNTP hKm8qu1ztM/mkWmDaLfDn203zmxMw/QBhED2hdYTQ4AITVk/K7zMTm06LdcJ8P+G 4bbslhpI+vHz4IRyh9Lz7hiWDJYZSqb23OIyuWzoyTiG4CElNSzzea0nZUHAQuDp V88I84uRdpxcHZCzOxDzq8MGHNs+d0D+VMRfDdH0v54h1L9gYeRPdxRtHo1eBI/4 ojuU59ZljzOZsBehWI9U0NP3o7a9cVk8GNB/CaJGFBcSyg4GCxlpglOhT3c0UmHQ 76Ozpsh103ERJv5Fhw23w8VN0ZeW9c8QbAh8a1VcdwxdEjMy3DxJSbLIOKFuCJCn bedluqQQSiNQUX62df7hB98rMKn5vAQ+u579ERGUWJVPZpiMJeC44FupwHDZvaG8 Pk3FmtzivnnIHDA3T8/LpYklMhrf3NHOTZUJSuj/nS8aqNYu1P9TVjwqXVobCA8i 8Mo8ZG0fkyDZBgTd/FHuvd7xJCK4zsqUcv4teFI1rucjYQOKPWiRKPJyXzJ6uo8R ij9fMHsQAVAZt1X1AJ3zgYglZ5sUnMEXXQnIdPOphQoo0qaaohIe8wSg6J65JAgC l/tf5XCQ6Lebvv4EFgnCqAfG2WQ/M3fFWEcYdobal0zXo2uMnck= =h9GQ -----END PGP SIGNATURE----- --Apple-Mail=_D8CB4250-9FF4-4851-AEB8-F059455B7020--