From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: "L, John Preetham (893)" <john_preetham.l@daimlertruck.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Ruslan Shymkevych <Ruslan_Shymkevych@epam.com>
Subject: Re: Request for Documentation on Bringing Up Xen on R-Car H3e (H3ULCB)
Date: Fri, 24 Jan 2025 05:02:58 +0000 [thread overview]
Message-ID: <87ldv0248u.fsf@epam.com> (raw)
In-Reply-To: <FR2PPF86245AF1B0938F55DAF4FF4E63A31B8E02@FR2PPF86245AF1B.DEUP281.PROD.OUTLOOK.COM> (John Preetham L.'s message of "Thu, 23 Jan 2025 11:44:31 +0000")
"L, John Preetham (893)" <john_preetham.l@daimlertruck.com> writes:
Hi John,
> Hi Volodymyr,
>
> Thank you for the detailed suggestions.
> Since I'm new to XEN hypervisor.
>
> I will approach the recommended method.
Yeah, I think this is the best approach if you want get something
working ASAP.
> Could you please let me know which Yocto version is stable and tested from your end?
As of now we are using Kirkstone. I believe, this is the latest Yocto
version supported by Renesas BSP. And we of course can't jump over
their head. Anyways, if you'll follow instruction in README.md, moulin
tool will fetch all required meta-layers and configure Yocto for you.
If you are interested in exact commit ids, you can check the YAML file
used by moulin tool:
https://github.com/xen-troops/meta-xt-prod-devel-rcar/blob/master/prod-devel-rcar.yaml#L32
--
WBR, Volodymyr
next prev parent reply other threads:[~2025-01-24 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 9:16 Request for Documentation on Bringing Up Xen on R-Car H3e (H3ULCB) L, John Preetham (893)
2025-01-23 0:35 ` Stefano Stabellini
2025-01-24 4:56 ` Volodymyr Babchuk
[not found] ` <8734ha2evr.fsf@epam.com>
[not found] ` <FR2PPF86245AF1B0938F55DAF4FF4E63A31B8E02@FR2PPF86245AF1B.DEUP281.PROD.OUTLOOK.COM>
2025-01-24 5:02 ` Volodymyr Babchuk [this message]
2025-05-05 4:25 ` L, John Preetham (893)
2025-05-06 11:21 ` Volodymyr Babchuk
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=87ldv0248u.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=Ruslan_Shymkevych@epam.com \
--cc=john_preetham.l@daimlertruck.com \
--cc=xen-devel@lists.xenproject.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.