From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: PCI Pass-through in Xen ARM: Draft 4 Date: Mon, 21 Sep 2015 11:17:52 +0100 Message-ID: <55FFD950.1090206@citrix.com> References: <55CC668F.80104@caviumnetworks.com> <55F0D8FC.7050606@citrix.com> <55F8694B.6070904@cavium.com> <55F9675C.6070502@citrix.com> <55FDC464.70003@caviumnetworks.com>,<55FDCA2B.80309@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Daney, David" , "Jaggi, Manish" , Xen Devel Cc: "Prasun.kapoor@cavium.com" , "Kumar, Vijaya" , Ian Campbell , =?UTF-8?B?4piFIFN0ZWZhbm8gU3RhYmVsbGluaQ==?= List-Id: xen-devel@lists.xenproject.org Hi David, On 19/09/15 22:51, Daney, David wrote: > I apologize for the top post, but for the record; > > The Thunder Linux implementation will be obtaining the PCI requester id from the OF device tree, or ACPI IORT table. It will *not* be derived from any hardware address. I'm aware about the ACPI IORT table but haven't see anything around a device tree bindings for the requester ID. Do you have a link/draft explaining this binding? Regards, -- Julien Grall