From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] mx6: add support of multi-processor command
Date: Sun, 22 Jun 2014 18:41:24 +0300 [thread overview]
Message-ID: <53A6F924.9020806@mail.bg> (raw)
In-Reply-To: <53A6E729.9030302@huau-gabriel.fr>
Hi Gabriel,
On 6/22/2014 5:24 PM, gabriel huau wrote:
> Hi Nikolay,
>
> I agree that you have to modify those OS to support 'multi-OS' on
> different core but this customization is not part of u-boot in my
> sense. For the second point, I have to disagree, the imx6 is totally
> appropriate for AMP/multi-OS, in my case, I wasn't thinking about
> virtualization which is something different but really about
> multi-OS/Bare Metal application. The interrupt controller (GIC) can be
> configured to distribute any interrupt on any core, for example, you
> can have UART1 interrupt on core0 and UART2 interrupt on core1.
> The only problem is the resource partitioning but as I said this is
> another subject which is not really part of u-boot and I already did
> some test by running Android on core0 and QNX on core1 without any
> problem as a proof of concept.
>
> A good example may be the support on this kind of application on the
> Zynq:
> http://www.wiki.xilinx.com/Multi-OS+Support+%28AMP+%26+Hypervisor%29
> This is also a Cortex A9 without the support of virtualization
> extensions.
Thanks for sharing this info, I'll check it out. I come from the
automotive industry where no one will allow running 2 OSes without
hardware isolation, so this is how my opinion about AMP on imx6 was
formed. And I agree that this actually isn't related with U-Boot itself
other than just loading the payload and starting the extra cores.
Kind regards,
Nikolay
next prev parent reply other threads:[~2014-06-22 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1403431201.10945.u-boot@lists.denx.de>
2014-06-22 14:09 ` [U-Boot] [PATCH v2] mx6: add support of multi-processor command Nikolay Dimitrov
2014-06-22 14:24 ` gabriel huau
2014-06-22 15:41 ` Nikolay Dimitrov [this message]
2014-07-08 11:24 ` Pavel Machek
2014-06-21 18:29 [U-Boot] [PATCH] " Gabriel Huau
2014-06-21 23:55 ` [U-Boot] [PATCH v2] " Gabriel Huau
2014-06-22 9:14 ` Jeroen Hofstee
2014-06-22 16:56 ` gabriel huau
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=53A6F924.9020806@mail.bg \
--to=picmaster@mail.bg \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox