From owner-freebsd-arm@freebsd.org Fri Oct 26 04:03:35 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 5D54F10D4EB4 for ; Fri, 26 Oct 2018 04:03:35 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CBD8E8196F for ; Fri, 26 Oct 2018 04:03:34 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.101] (82-203-189-118.bb.dnainternet.fi [82.203.189.118]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w9Q43WZR025026 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 26 Oct 2018 04:03:33 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 82-203-189-118.bb.dnainternet.fi [82.203.189.118] claimed to be [192.168.1.101] From: Stefan Parvu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: RBPI3B+ clock speed Message-Id: Date: Fri, 26 Oct 2018 07:03:26 +0300 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3445.100.39) 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, 26 Oct 2018 04:03:35 -0000 Hi, Coming back to the clock speed of the RBPI3B+ I have some questions: - How can I see the current clock speed my RBPI is using at any moment ? - How would you change the frequency of the clock speed which by default = seems=20 set to 600MHz ?=20 I hope changing the cpu frequency speed would not affect how the uart is = operating. I do recall they were issues on a previous RBPI3B+ version regarding = this. Thanks, Stefan=