From: Chen Baozi <baozich@gmail.com>
To: Francesco Gringoli <francesco.gringoli@ing.unibs.it>
Cc: Giancarlo Canales <gcanalesb@me.com>,
List Developer Xen <xen-devel@lists.xen.org>
Subject: Re: Xen OMAP5 Support
Date: Wed, 6 Aug 2014 22:47:22 +0800 [thread overview]
Message-ID: <FB60607B-AF7F-41A3-A8C4-03FAC5575488@gmail.com> (raw)
In-Reply-To: <046E308F-FF31-4470-94F9-5815BE421D82@ing.unibs.it>
[-- Attachment #1.1: Type: text/plain, Size: 1579 bytes --]
Hi Francesco,
On Aug 6, 2014, at 17:02, Francesco Gringoli <francesco.gringoli@ing.unibs.it> wrote:
> On Apr 21, 2014, at 5:08 AM, Chen Baozi <baozich@gmail.com> wrote:
>
>> Hi Giancarlo,
>>
>> On Apr 21, 2014, at 2:10, Giancarlo Canales <gcanalesb@me.com> wrote:
>>
>>> Chen Baozi,
>>>
>>> I’m looking forward to tinkering around with Xen on an OMAP5 board, the OMAP5432 EVM, but I can’t find any documentation or information about the current status of this port. I discovered your threads in the mailing list, and thought that maybe you could help me out.
>>
>> The port of Xen hypervisor on OMAP5 is already uptreamed. You should be able
>> to build it directly from the git repo. The only problem is that the omap
>> kernel has its only data structure for device description. Thus, you need to
>> disable the corresponding UART port that has been used by Xen serial in the
>> kernel tree (only disable it in FDT is not enough).
>>
>> Regards,
>>
>> Baozi
> Hi Chen,
>
> would you mind if I refresh the wiki with other information that could help to setup the boot process for the uEvm?
Never mind. Please just do it.
> I'm making some order in my notes and I would like to share them (e.g., adding CONFIG_ARCH_VIRT for the domU, how to boot domU, the userspace, how to setup u-boot specific for the board, etc).
>
> By the way, another question: did you experience any failure of the FTDI chip on the uEvm? Mine is completely dead and the plug shows evidence of oxidation.
Haven’t noticed that before.
Regards,
Baozi
[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-08-06 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C82421AD-B286-42D4-BCB0-2E5E97E218BF@me.com>
2014-04-21 3:08 ` Xen OMAP5 Support Chen Baozi
2014-08-06 9:02 ` Francesco Gringoli
2014-08-06 14:47 ` Chen Baozi [this message]
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=FB60607B-AF7F-41A3-A8C4-03FAC5575488@gmail.com \
--to=baozich@gmail.com \
--cc=francesco.gringoli@ing.unibs.it \
--cc=gcanalesb@me.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).