From owner-freebsd-arm@freebsd.org Wed Oct 3 19:59:19 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA25D10ABBAB for ; Wed, 3 Oct 2018 19:59:19 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-12.consmr.mail.bf2.yahoo.com (sonic304-12.consmr.mail.bf2.yahoo.com [74.6.128.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 596A78CF6B for ; Wed, 3 Oct 2018 19:59:19 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Y4MyGl0VM1kQ_y7Yg1GdgL5dm1bPwYCHikvKRpdLBQZ_qSy7wddHw3GirRchc1L b_Rq_A.WVPSTtWyuuIgu.mUxbUwdjDvsOA7j9haKBHrUopZCsLZy.BFISZAEnEUbU4V5O_GvJNiO GS8bJySJrDDrXqMku4vdnrBfjsmm0XaR377YiMIzupIO5IwNanNBK8sRcT19_iSjzW7UmfeqUh9T 9NOVqIIBC36ziR.29uYbK2SWqA2ymLkM8xfOceVqMgpaedUPAEEwfXanPc.TGGEbnVZQ2DxjOXts lOIrAtzFeo2G0k45WkjJG51YUt2Fr1Y7y3xyZBsdcDHSPABCqw3WU55gzdnjuyxNRjhzqzz0ih2T Wtu2t4JI.coqSuBgs9fQbLoHs8Tr8v4ndX78xXQDAsGTEn8P2XuInJAHQuabvpwOmAcMMons5G4o ak8ORgvTiqxW.gXTccXcAUjkAKjt.aQ3RzGfsRvQzElvk9OtHyYL85D0TPL6IaaOdN08W90TM3f7 a8WGr_8vBhWE1WdC.RMFVYjw6hOwD42hbyfJ7DATx1Jh.Z2r1l7igmaFX_1a741im8YlEAZuCalD IHed1l.MpVRfcxmf3HS9evQflr29AFLgBGFdK94yEGS.CyRSib3IN1yUJ6w6xT1zN1irdGKke1tC 3nmH9cCsdegRs_HnemXo2lc7U3vgisW9O3MnA3NKCcz52KmPBJ.hedOUaS2yf.Y.4Camzs2byXTY .X5NFCQP4g0KHNAJr9k31tAbLx1YSyJvUQAH_EAdTScd5p7_BpNj7cqT38xi.PJukdnro3aIuTcH 7HQmQix3EICy8u3rELjodp8eUeis1yvqKIVeX2Ek3q8VJq2BR65frveHrpuN8VuBv8Tae3c4axGJ aIMLLaShD5oLQIe1Im9wIWkfQCZF8hkcAaClkfXsb_ENvoFBbGTEm7HZoo7WgEatOIHqaBxKf8Ob dtnChfnM08REEAi1hJCaj236JcM3s5B7Vgeq2Y0abri2HJc8jC5SNZDLSyWZ9RP1iqCvPTUCravY nI4X8HGyKH4IYuup.5G4rCS8TGYuyGlMnyFG.Cg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Wed, 3 Oct 2018 19:59:18 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.101]) ([76.115.7.162]) by smtp427.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e667ad6857431554f960311e67e00465 for ; Wed, 03 Oct 2018 19:59:16 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Banana Pi M3 (armv7/CortexA7) with head -339076 and u-boot 2018.09_3 from ports: what CPU clock speed is it using? More. . . Message-Id: <5B9D79C7-306E-45E0-9311-DDA0CC70C4A5@yahoo.com> Date: Wed, 3 Oct 2018 12:59:13 -0700 To: freebsd-arm X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 19:59:20 -0000 The following leaves me wondering if the switch to linux based .dts files and related changes have also invalidated some "Supported devices" table entries in https://wiki.freebsd.org/FreeBSD/arm/Allwinner . For example: cpufreq / DVFS and/or Thermal for some columns. With -r308125 the BPi-M3 would -j4 or -j5 buildworld buildkernel for the src.conf settings that I use in about 9.5 hours. (From my 2016-Nov-05 list E-mail.) [The BPi-M3 has heat sinks, a case, and a fan.] I've not done such builds in a long time and I've not recorded times when I have. But having updated to -r339076 based and the modern 2018.09 u-boot context has the BPi-M3 just finished building lib/clang/libclang/AST/ materials after about 19 hours. top indicates swap has 1740M Total and Free. (My top modifications indicate the Max Observed Active Mem as 922M so far.) There is a big difference in clang between the two and that contributes to taking more time. But, by contrast, the (aarch64 A64 based) Pine64+ 2GB -j4 buildworld buildkernel for -r338860 built completely in about 13.75 hours, although it had faster media in the microsd card slot (e.MMC on an adapter and used in DDR52 mode via experimental changes to allow e.MMC use). This leaves me wondering if the BPi-M3 clock rate(s) for the CPU and/or RAM are set avoiding the upper end of the range compared to -r308125's time frame. (This may well be reasonable currently.) Taking a guess at relevant figures from the modern BPi-M3 configuration via sysctl -a output: hw.clock.c1cpux.frequency: 1008000000 hw.clock.c0cpux.frequency: 1008000000 . . . hw.clock.pll_c1cpux.frequency: 1008000000 hw.clock.pll_c0cpux.frequency: 1008000000 (I've not figured out anything for DRAM: I ignored anything reported as 0 and bus-*.frequency figures.) If the current context is without throttling or some such, it may be that 1 GHz or so is used to just keep things in a safe range: I see no evidence of cpu or such temperatures in the sysctl -a output so a feedback loop controlling the frequency (and voltages) may not be an option currently for the BPi-M3. However, it is possible the frequency or other behavior is unexpected. I can not tell. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)