From owner-freebsd-arm@freebsd.org Sun Jan 22 18:54:18 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 D1E11CBD23F for ; Sun, 22 Jan 2017 18:54:18 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-yb0-x232.google.com (mail-yb0-x232.google.com [IPv6:2607:f8b0:4002:c09::232]) (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 85BB8D7 for ; Sun, 22 Jan 2017 18:54:18 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-yb0-x232.google.com with SMTP id l23so81575275ybj.2 for ; Sun, 22 Jan 2017 10:54: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=HEzL6mdYKs7bAhoRikCBR4TF23oeCadpt+On7ISKZpc=; b=K9FKEYHWIQalQsVjJThl7VGjsee9ZFu0dmSPdhydLVWEN9oqLeTlQYsOBx5yikmfDa wkQF/5fT/Z0t7et2By/IKY5gs+4olEBnc4cMmWpptGukX3XmNYtEOs+w8paX+TsdE4z9 vYkzxxmHuEZFPnV55g2rio89dsuw+H/oB9uq31eRxH+vRZuitFuD9Onv6UhbPCZ9a06F jQD6oRrbf4Jx0+wsYn0wZnfs8ch3JxkQOiqx4KinhlYYSA2nZHGAjjZsV+uj8zsycbno qnKK+wWE6MSDbCbjztFZ7usz1/Btj+NPIPN3N/8yF6XIxrD/QWZDDtMgqkUchcRXvMZZ uyQQ== 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=HEzL6mdYKs7bAhoRikCBR4TF23oeCadpt+On7ISKZpc=; b=K2jAv1l8LIS5wlFFJD7EpSsJq+PBiSospbRKOoX5XwSNROzaA+Xk0nrPQ/IidIwqj5 GKBsBXIs7wiLvfjhv4sVNrLlBauVysDZAbdNFGVSsTrJwGEK4hkLtC07d+Jor7iuKzlU 4/tVbgfLX5puU35b7GjeR+RdMdOw+nuZXd0uMEGUvAoTW+sgkcceWEoX4PrP7h6O36P6 gvyy9X5T+NUcFcW+pxCLiLbjKOa20j9P/tRBB4aAuIEMTdT9nDsDiXwj5Bjrx/ZWj0I8 k/9yu72XDqhJCk4voWtIZal0ytNr5cRgf1QiYEnQHcEZwqUkK51cpF1hF3pV4KMKL7fp aVYg== X-Gm-Message-State: AIkVDXJyYFqSqZI/YBfyRTzBW7VgRU1NTNWs9K5MPKrC36c1VdhL1A5cj8Nc8twMOk9CWt5AeVqGYs1Bs11G6g== X-Received: by 10.37.224.77 with SMTP id x74mr17172237ybg.80.1485111257587; Sun, 22 Jan 2017 10:54:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.13.231.135 with HTTP; Sun, 22 Jan 2017 10:54:17 -0800 (PST) In-Reply-To: <48f8cbc1-3814-b9f6-0e3a-ebe97466d1df@selasky.org> References: <48f8cbc1-3814-b9f6-0e3a-ebe97466d1df@selasky.org> From: Dustin Marquess Date: Sun, 22 Jan 2017 12:54:17 -0600 Message-ID: Subject: Re: Getting the kernel to let go of my UART! To: Hans Petter Selasky Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Sun, 22 Jan 2017 18:54:18 -0000 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. -Dustin