From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viktor Kleinik Subject: ARM: access to iomem and HW IRQ Date: Wed, 26 Feb 2014 15:43:48 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8785435034796965010==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============8785435034796965010== Content-Type: multipart/alternative; boundary=001a11c225901cd0c904f3511229 --001a11c225901cd0c904f3511229 Content-Type: text/plain; charset=ISO-8859-1 Hi all, Does anyone knows something about future plans to implement xc_domain_memory_mapping/XEN_DOMCTL_memory_mapping and xc_physdev_map_pirq/PHYSDEVOP_map_pirq calls for ARM? Is their implementation expected in the near future? Regards, Victor --001a11c225901cd0c904f3511229 Content-Type: text/html; charset=ISO-8859-1
Hi all,

Does anyone knows something about future plans to implement
xc_domain_memory_mapping/XEN_DOMCTL_memory_mapping and
xc_physdev_map_pirq/PHYSDEVOP_map_pirq calls for ARM?

Is their implementation expected in the near future?

Regards,
Victor
--001a11c225901cd0c904f3511229-- --===============8785435034796965010== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============8785435034796965010==--