From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH v2] xen/tools: Introduce QNX IFS loader Date: Thu, 18 Sep 2014 12:11:06 -0700 Message-ID: <541B2E4A.60502@linaro.org> References: <1410971686-28977-1-git-send-email-oleksandr.tyshchenko@globallogic.com> <1410971686-28977-2-git-send-email-oleksandr.tyshchenko@globallogic.com> <5419CBE5.2030205@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" 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: Oleksandr Tyshchenko Cc: Stefano Stabellini , Tim Deegan , Ian Campbell , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org Hi Oleksandr, On 18/09/14 03:55, Oleksandr Tyshchenko wrote: >> Also, it looks like that with this solution, the QNX image will be tight to >> a specific version of Xen. Indeed, you have to specify the physical address >> in the QNX image. > > I just specify the starting address in buildfile which shiped with > BSP. The starting address is the base address of the image. > In our case we have next image attribute: > [image=0x80008000] This RAM base address has changed in Xen 4.5. I suspect you are trying this patch on top of Xen 4.4, right? If so, it would be nice if you can try this patch also on Xen 4.5. > This is one of the required actions for QNX to load on top of XEN. > Yes, if the rambase addr changes in XEN, I will need to change the > image attr in QNX. Is it possible to make QNX position independent? If not, I would add a check that the load address is effectively part of the RAM and throw an error if it's not the case. Regards, -- Julien Grall