From owner-freebsd-arm@freebsd.org Mon Jan 23 20:42:14 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 006A4CBE22C for ; Mon, 23 Jan 2017 20:42:14 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 D27B2682 for ; Mon, 23 Jan 2017 20:42:13 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cVlRH-000JDs-Bq; Mon, 23 Jan 2017 12:42:08 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v0NKg63p073895; Mon, 23 Jan 2017 12:42:06 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Mon, 23 Jan 2017 12:42:06 -0800 From: Oleksandr Tymoshenko To: Dustin Marquess Cc: Hans Petter Selasky , "freebsd-arm@freebsd.org" Subject: Re: Getting the kernel to let go of my UART! Message-ID: <20170123204206.GA73799@bluezbox.com> References: <48f8cbc1-3814-b9f6-0e3a-ebe97466d1df@selasky.org> <20170122190659.GA62786@bluezbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Dustin Marquess (dmarquess@gmail.com) wrote: > Okay, maybe the console thing was a red herring then. > > It's not marking it as a console at all anymore, but something is > still locking the baud rate to 115200. Even though stty and minicom > are both set to 9600, anything set/received at 9600 doesn't work/is > garbled. If I set it to 115200, it works fine. I had wrongly assumed > it was because of it marking it as a console (since the console line > in dmesg said 115200). > > Device map? enable_uart=1 aka core_freq= maybe? I'll try tinkering.. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: elinux.org] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 20:42:14 -0000 Dustin Marquess (dmarquess@gmail.com) wrote: > Okay, maybe the console thing was a red herring then. > > It's not marking it as a console at all anymore, but something is > still locking the baud rate to 115200. Even though stty and minicom > are both set to 9600, anything set/received at 9600 doesn't work/is > garbled. If I set it to 115200, it works fine. I had wrongly assumed > it was because of it marking it as a console (since the console line > in dmesg said 115200). > > Device map? enable_uart=1 aka core_freq= maybe? I'll try tinkering.. It might be a problem with the driver itself. From a quick glance, PL011 driver sets baudrate only if it has reference clock frequency which doesn't seem to be the case for RPi. If reference clock frequency is unknown divider register is left untouched. According to this document: http://elinux.org/RPiconfig you can set initial baudrate in config.txt using init_uart_baud variable -- gonzo