From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Problems when using latest git tree to boot xen on OMAP5 Date: Wed, 9 Oct 2013 12:19:19 +0100 Message-ID: <1381317559.7600.3.camel@kazak.uk.xensource.com> References: <936C837B-7005-4CE0-8265-7B7ACA7C78FD@gmail.com> <91879A6F-B459-4D10-A691-4A04915D82AA@gmail.com> <1381135195.21562.56.camel@kazak.uk.xensource.com> <525285B3.8010902@gmail.com> <52529404.8030909@linaro.org> <20131009074627.GA6342@cbz-workstation> <1381306276.9920.21.camel@kazak.uk.xensource.com> <52553AE2.6070806@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <52553AE2.6070806@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: Chen Baozi , List Xen Developer List-Id: xen-devel@lists.xenproject.org On Wed, 2013-10-09 at 12:15 +0100, Julien Grall wrote: > On 10/09/2013 09:11 AM, Ian Campbell wrote: > > Rather than whitelisting and mapping disabled devices through perhaps we > > should implement them as read 0xf (or 0x0) and write ignore? > > We can't assume that these values (0x0 or 0xf) won't affect dom0 behaviour. 0xff is what you would typically get back if there was no actual hardware present. > What about a new quirk to map all disabled device in dom0 > (PLATFORM_QUIRK_DOM0_MAP_DISABLED_DEVICE)? Why is this not the default behaviour?