From owner-freebsd-arm@freebsd.org  Wed Mar 30 15:54:53 2016
Return-Path: <owner-freebsd-arm@freebsd.org>
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 023B8AE36DD
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Wed, 30 Mar 2016 15:54:53 +0000 (UTC)
 (envelope-from fbsd@www.zefox.net)
Received: from www.zefox.net (www.zefox.net [69.239.235.194])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C0BB7104B
 for <freebsd-arm@freebsd.org>; Wed, 30 Mar 2016 15:54:52 +0000 (UTC)
 (envelope-from fbsd@www.zefox.net)
Received: from www.zefox.net (localhost [127.0.0.1])
 by www.zefox.net (8.14.9/8.14.5) with ESMTP id u2UFso2Y032601;
 Wed, 30 Mar 2016 08:54:50 -0700 (PDT)
 (envelope-from fbsd@www.zefox.net)
Received: (from fbsd@localhost)
 by www.zefox.net (8.14.9/8.14.5/Submit) id u2UFsnsx032600;
 Wed, 30 Mar 2016 08:54:49 -0700 (PDT) (envelope-from fbsd)
Date: Wed, 30 Mar 2016 08:54:49 -0700
From: bob prohaska <fbsd@www.zefox.net>
To: Jia-Shiun Li <jiashiun@gmail.com>
Cc: Hans Petter Selasky <hps@selasky.org>,
 "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject: Re: Confusing RPI2 kernel options
Message-ID: <20160330155449.GA32545@www.zefox.net>
References: <20160328225715.GA7705@www.zefox.net>
 <56FB80B1.9090903@selasky.org>
 <CAHNYxxMiLQcvjpkfvkmkfHOQkuebuATp+bUO1LehwVvvFxW3-A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHNYxxMiLQcvjpkfvkmkfHOQkuebuATp+bUO1LehwVvvFxW3-A@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2016 15:54:53 -0000

On Wed, Mar 30, 2016 at 07:01:55PM +0800, Jia-Shiun Li wrote:
> On Wed, Mar 30, 2016 at 3:30 PM, Hans Petter Selasky <hps@selasky.org>
> wrote:
> 
> That's not about keyboard but "boot console",
> or more formally "system console",
> to which kernel messages is output.
> 
> At booting kernel,
> 
> - with vt, kernel boot messages go to HDMI display.
>   Serial port shows nothing until getty is up for it to
>   bring login prompt.
> - without vt, kernel boot messages go to serial port.
> 
> 
> -Jia-Shiun.

That's not what I'm observing. Using a kernel config containing
# Comment following lines for boot console on serial port
device          vt
device          kbdmux
device          ukbd

the serial console gets a complete transcript of the boot process,
but the HDMI display stops updating somewhere around the ethernet
probe and does not resume until a login prompt appears.  Thats the 
reverse of the indicated behavior. 

Has anybody tried commenting out those lines to see what happens?
It would be a pleasant surprise if the USB keyboard started to work
in single-user mode.

Thanks for reading,

bob prohaska