Re: [Xen-devel] Problems when using latest git tree to boot xen on OMAP5

[Julien Grall <julien.grall@xxxxxxxxxx>]

On 10/09/2013 12:19 PM, Ian Campbell wrote:
> 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?

From our discussion a months a ago (http://patches.linaro.org/19590/),
status = "disabled" means : "not present/wired-up on this variant of
the platform".

As Linux should cope with this status, why do we need to map these
devices in DOM0?

If we go further, with passthrough we may want remove device from the
device tree. If Linux has hardcoded device (but also in the device tree)
it will likely fail.

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel