From owner-freebsd-arm@freebsd.org Wed Jul 17 22:02:49 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 BA3CAB689F for ; Wed, 17 Jul 2019 22:02:49 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (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 "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F06595B28 for ; Wed, 17 Jul 2019 22:02:48 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.164] (82-203-143-70.bb.dnainternet.fi [82.203.143.70]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id x6HM2kxJ027740 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 17 Jul 2019 22:02:47 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 82-203-143-70.bb.dnainternet.fi [82.203.143.70] claimed to be [192.168.1.164] From: Stefan Parvu Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0 Date: Thu, 18 Jul 2019 01:02:41 +0300 References: <41A4CA5C-B487-490F-8A19-2D51F43E1004@kronometrix.org> <95616620-bbaf-dbc3-49eb-3e2562638d49@bunyatech.com.au> <74E3E782-8481-4B5B-A0AF-A04590C27D6D@kronometrix.org> <790afcb5f0809a89b45982958a85f1539fec05c7.camel@freebsd.org> <36088812-2135-4433-BC49-0BC433EC6767@kronometrix.org> <86CC4711-47AC-45C6-B6D3-71C9FFDD4A91@kronometrix.org> <2ec7d7f63de31065b9cab396c662fe24f0107078.camel@freebsd.org> <2AC05799-7D11-4200-8D16-38E3718470BB@kronometrix.org> <91E26684-07A0-4F03-92BC-8D49359B1358@kronometrix.org> <4707336cb7d4cdd8dbd2070a9e799f12bff59fcc.camel@freebsd.org> To: freebsd-arm@freebsd.org In-Reply-To: <4707336cb7d4cdd8dbd2070a9e799f12bff59fcc.camel@freebsd.org> Message-Id: X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 0F06595B28 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of sparvu@kronometrix.org designates 95.85.46.90 as permitted sender) smtp.mailfrom=sparvu@kronometrix.org X-Spamd-Result: default: False [3.93 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; NEURAL_SPAM_MEDIUM(0.98)[0.982,0]; URI_COUNT_ODD(1.00)[3]; RCPT_COUNT_ONE(0.00)[1]; HAS_XAW(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mail.kronometrix.org]; NEURAL_SPAM_LONG(0.96)[0.961,0]; DMARC_NA(0.00)[kronometrix.org]; NEURAL_SPAM_SHORT(0.26)[0.259,0]; IP_SCORE(0.54)[ip: (0.43), ipnet: 95.85.0.0/18(1.24), asn: 14061(1.08), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:14061, ipnet:95.85.0.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=us-ascii 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, 17 Jul 2019 22:02:49 -0000 >=20 > The spurious interrupt problems are fixed with this patch (it isn't > really a problem, the patch just disables the messages): > = https://svnweb.freebsd.org/base/head/sys/arm/broadcom/bcm2835/bcm2835_intr= .c?r1=3D332262&r2=3D346489&view=3Dpatch = Thanks. I can live with these.=20 > My RasClock battery had gone dead too. It was no more than 2 years = old > at the most, but the rasclock was running on battery all that time > (until it died), because I almost never power on the rpi boards. I > think the rasclock may use more battery power than some other rtc > boards because the chip it uses is more accurate than most. Part of > how it does that is to use a temperature-compensated oscillator, but > that means it uses extra power to measure the temperature. Right. Now it makes sense. I was wondering is this chip using more = battery than others ? Looks like. And maybe my batteries I bought might not have = been very good. I need to test other models.=20 Thanks a lot for help. Stefan=