From: Julien Grall <julien.grall@linaro.org>
To: Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Campbell <ian.campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen/tools: Introduce QNX IFS loader
Date: Wed, 20 Aug 2014 09:55:12 -0500 [thread overview]
Message-ID: <53F4B6D0.7020307@linaro.org> (raw)
In-Reply-To: <CAJEb2DGao7jKntmMgPoTtBKoQi56u9bxZW3FEe9=a1kF4T0E+Q@mail.gmail.com>
On 20/08/14 08:00, Oleksandr Tyshchenko wrote:
> Julien, can I introduce QNX loader as a loader for ARM32 only
> (I mean, just add prefix 32 to callbacks and so on)?
> Or should I make 2 separate loaders:
> - qnx_ifs_loader32;
> - qnx_ifs_loader64;
> as it was done in armzimageloader?
I'm not sure to understand why you would introduce 2 different loaders.
The code will be built for both 32 bits and 64 bits toolstack because
people may want to run QNX 32 bits guest on a 64 bits hardware.
For instance armzimageloader{32,64} don't do the same things, the former
is loading a zImage while the latter loads an Image.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-08-20 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 15:51 [PATCH] xen/tools: Introduce QNX IFS loader Oleksandr Tyshchenko
2014-08-19 16:13 ` Andrew Cooper
2014-08-19 16:26 ` Dario Faggioli
2014-08-20 4:09 ` Lars Kurth
2014-08-20 10:07 ` Artem Mygaiev
2014-08-20 10:11 ` Dario Faggioli
2014-08-20 13:56 ` Artem Mygaiev
2014-08-20 14:00 ` Dario Faggioli
2014-08-26 21:09 ` Ian Campbell
2014-08-27 7:53 ` Andrii Tseglytskyi
2014-08-20 10:20 ` Oleksandr Tyshchenko
2014-08-19 16:41 ` Julien Grall
2014-08-20 11:10 ` Oleksandr Tyshchenko
2014-08-20 13:00 ` Oleksandr Tyshchenko
2014-08-20 14:55 ` Julien Grall [this message]
2014-08-20 16:35 ` Oleksandr Tyshchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F4B6D0.7020307@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=oleksandr.tyshchenko@globallogic.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.