From owner-freebsd-arm@freebsd.org Mon Jan 23 06:24:19 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 3E96BCBD7A1 for ; Mon, 23 Jan 2017 06:24:19 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 066338E9 for ; Mon, 23 Jan 2017 06:24:18 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-yw0-x22c.google.com with SMTP id u68so90345421ywg.0 for ; Sun, 22 Jan 2017 22:24:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qRbefxMreaKZvyan4RY+dSYn/aa0G5umzYr+/v4U0/E=; b=Ij/bHncqb6iz6yFB8V5uDs69Bh54lzz6hIhv9X6p5qA0fA37KUxGRb93HE+JL2b+0t 1KMGzTlFqMW5DTfEcQUewuAYPGjiKbNt8N1pEaduNRu6P/s2YtbBzctRpiGpPETCcbfv 1mh/s/CTCwJ0bwLaHg7E17nVyjK8tSCUVFPpTMr+yMhABekvxQkelbnufGQnvCbEgFNs HeU5Km4Ao0WLp/E/rXew0gQjJXtfB6+gKRFpwGKAFi+d8TRA3L8DbuDDSOV9Ub3i9510 JV1bnmNfykB8ScXg0MZNQaYr4O3aEsgEYeOukOC/pzBxpFhJUN8obYiYh48jSeaGlm1Q FjGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qRbefxMreaKZvyan4RY+dSYn/aa0G5umzYr+/v4U0/E=; b=UGXUXbhjVjtK2UcVwcUsHNeR0e6NWAS63JJk69qOtNfBhi09o6TfOxFJMZJBvPCLkC tN9RmN/6x58klCGYPFspnSDnbusC3xvRggJMyPoeQxL3aX8efE3m9hYGx8K4E7TqtN9q MjEkGszImRCUb3LCQipfdLU9S4mfDjkU6ETxmXf40MYM2P1FHq6jWQ3S8rqlcnO9no3B k0Rn0dQzlP5tRlOmM8fL7zNy1WDpqXQ6uNVBmFcRpztWmziVTu8vfwo8ctm2mxOTueM0 JfuayJARwIdlNXerMrfRWSW1WxPtMkQ3Wtzap1i2WtwnQe+cBcKmADzb0+eDG+wvWzLU I5wg== X-Gm-Message-State: AIkVDXJs5rbTnjibHRtzNfNQq5OT+xj5ZtKl3ziCsVOFk9+qAuBVkvNvna6D3gn3Cy+i0lzTWHWi7SCUqW6Wiw== X-Received: by 10.129.75.147 with SMTP id y141mr19970814ywa.86.1485152658147; Sun, 22 Jan 2017 22:24:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.13.231.135 with HTTP; Sun, 22 Jan 2017 22:24:17 -0800 (PST) In-Reply-To: <20170122190659.GA62786@bluezbox.com> References: <48f8cbc1-3814-b9f6-0e3a-ebe97466d1df@selasky.org> <20170122190659.GA62786@bluezbox.com> From: Dustin Marquess Date: Mon, 23 Jan 2017 00:24:17 -0600 Message-ID: Subject: Re: Getting the kernel to let go of my UART! To: Oleksandr Tymoshenko Cc: Hans Petter Selasky , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 06:24:19 -0000 On Sun, Jan 22, 2017 at 1:06 PM, Oleksandr Tymoshenko wrote: > Dustin Marquess (dmarquess@gmail.com) wrote: >> On Sunday, January 22, 2017, Hans Petter Selasky wrote: >> >> > On 01/22/17 06:07, Dustin Marquess wrote: >> > >> >> [Sorry if this is somewhat of a dupe, I have yet to find a solution] >> >> >> >> I've been running FreeBSD on my Pi 3s for a little over a month now, >> >> first using gonzo's SMP code + a home cross-compiled kernel, and then >> >> I moved to the HardenedBSD images. All of them work great except one >> >> issue that's driving me nuts... >> >> >> >> The downside to the Pi 3 vs some other boards is that there's really >> >> only one UART tied to the GPIO pins. I'm trying to feed my Pi 3 with >> >> a GPS board. >> >> >> >> 1st issue: The NMEA stream upsets U-boot. Fine, compiled my own and >> >> that's "fixed". >> >> >> >> 2nd issue: Even with a USB keyboard attached and HDMI output >> >> connected, FreeBSD still wants to steal the first uart (ttyu0) as a >> >> console port. I thought that would be fine as long as I use "-m -n >> >> -q" in the boot config to disable kernel output and then "conscontrol >> >> delete ttyu0". Well, that KIND of works. It seems to work fine when >> >> using 115200bps, but trying to change the baud rate to match the GPS >> >> unit doesn't seem to work at all, I'm guessing because it's still set >> >> as an available console? >> >> >> >> hint.uart.0.flags="0x0" doesn't work, as it still marks it as a >> >> console. console="efi" seems to be the only setting that works, >> >> "vidconsole" and "nullconsole" both don't work. >> >> >> >> Is there a way to stop the kernel from trying to claim the UART as a >> >> console? >> >> >> > >> > I think so, have a look in /etc/ttys and comment out the ttyu0 line. >> > >> > Sadly, I already did that. There's no getty running, but dmesg still shows >> the kernel marking it as a console. > > Just a random idea, try adding hw.fdt.console=foo0 to /boot/loader.conf > This should force uart_cpu_fdt_probe to fail. Wow, I think that actually did the trick! Thank you so very much, I've been pulling my hair out of this for probably 2 weeks now! -Dustin