From owner-freebsd-arm@freebsd.org Thu Mar 18 21:34:14 2021 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 C2F665AE254 for ; Thu, 18 Mar 2021 21:34:14 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1gJj4vwdz4pQP for ; Thu, 18 Mar 2021 21:34:13 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 12ILYIkx027445 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 18 Mar 2021 14:34:19 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 12ILYI9c027444; Thu, 18 Mar 2021 14:34:18 -0700 (PDT) (envelope-from fbsd) Date: Thu, 18 Mar 2021 14:34:18 -0700 From: bob prohaska To: bob prohaska Cc: freebsd-arm@freebsd.org Subject: Re: RPI4 clock speeds and serial port Message-ID: <20210318213418.GC26853@www.zefox.net> References: <20210318170053.GA26688@www.zefox.net> <20210318180736.GA26853@www.zefox.net> <5F3752C0-F984-48CE-BA05-526A0C37C1FF@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5F3752C0-F984-48CE-BA05-526A0C37C1FF@yahoo.com> X-Rspamd-Queue-Id: 4F1gJj4vwdz4pQP 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 [-0.97 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.87)[-0.874]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; 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]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2021 21:34:14 -0000 On Thu, Mar 18, 2021 at 12:14:07PM -0700, Mark Millard wrote: > > You are correct that the mini-UART has the dependencies. > But use of: > > dtoverlay=disable-bt > > avoids use of the mini-UART. The same is true > of instead using: > > dtoverlay=miniuart-bt > > but, then, Bluetooth suffers the variability. > (I just do not try to use Bluetooth.) > This clears up my confusion. Bluetooth is of no immediate use to me, is there any prospect FreeBSD will ever support it? DB's suggestion to speed-correct the mini-uart seems like a good idea unless there are some bad side effects. Thank you! bob prohaska