From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Design doc of adding ACPI support for arm64 on Xen - version 2 Date: Wed, 12 Aug 2015 13:20:57 +0100 Message-ID: <55CB3A29.3090803@citrix.com> References: <55C413D5.7000709@huawei.com> <55CA2077.2000706@citrix.com> <55CAB7D3.5050504@huawei.com> <1439369520.9747.311.camel@citrix.com> <55CB1033.4040509@citrix.com> <20150812113655.274e4fa9@bender> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150812113655.274e4fa9@bender> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Turner Cc: Hangaohuai , Ian Campbell , "Huangpeng (Peter)" , xen-devel , Stefano Stabellini , Shannon Zhao , Jan Beulich , Shannon Zhao , Parth Dixit , Christoffer Dall List-Id: xen-devel@lists.xenproject.org On 12/08/15 11:36, Andrew Turner wrote: > Would it be possible to add a stdout property and node for the hvc0 > device? It would help FreeBSD as we use this to find the kernel > console. We check for the stdout-path, linux,stdout-path, stdout, > stdin-path, and stdin properties, in that order, with the first > property selected as the console. If none are found we fall back to > searching for a serial0 device. You can see how we find the device at > [1]. the stdout-path property is used by Xen in order to get the UART. The property will be removed from the device tree passed to DOM0. The Xen console is not UART a driver so having a property with "hvc" wouldn't help here. Although, when running on Xen, FreeBSD is creating a Xen console by default with the higher priority. It will be grabbed by FreeBSD as the default one. Regards, -- Julien Grall