From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: meta-ti@yoctoproject.org, lokeshvutla@ti.com
Subject: Re: [master/thud][PATCH v2 3/3] jailhouse: use ramfs for linux-demo
Date: Fri, 30 Aug 2019 12:29:09 -0400 [thread overview]
Message-ID: <20190830162908.GG3307@beryl> (raw)
In-Reply-To: <dc35dc13-5327-6367-a6dd-8c260dbc9e54@ti.com>
On Fri, Aug 30, 2019 at 12:23:43PM -0400, Jacob Stiffler wrote:
>
> On 8/30/2019 12:13 PM, Denys Dmytriyenko wrote:
> >On Tue, Aug 20, 2019 at 02:11:12PM -0400, Jacob Stiffler wrote:
> >>* Configure the linux-demo to use a ramfs for the linux inmate.
> >>* Using JH_RAMFS_IMAGE, this can be set in some global conf.
> >>
> >>Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> >>---
> >> recipes-kernel/jailhouse/jailhouse_git.bb | 21 +++++++++++++++++----
> >> 1 file changed, 17 insertions(+), 4 deletions(-)
> >>
> >>diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>index 5d572d0..ba6772f 100644
> >>--- a/recipes-kernel/jailhouse/jailhouse_git.bb
> >>+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>@@ -58,8 +58,10 @@ JH_SYSCONFIG_CELL ?= ""
> >> JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
> >> JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
> >>+JH_RAMFS_IMAGE ?= "core-image-minimal"
> >Ok, after thinking about it a bit, I will agree to JH_RAMFS_IMAGE variable,
> >but I don't want to loose the default INITRAMFS_IMAGE usage. So, how about
> >changing the default here to something like this:
> >
> >JH_RAMFS_IMAGE ?= "${INITRAMFS_IMAGE}"
> >
> >That way either of the variables can be set my machine config or local.conf
> >and the default use is also preserved. Thoughts?
>
>
> I like that idea better as well.
>
>
> >
> >> JH_CMDLINE ?= ""
> >>-JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait"
> >>+JH_CMDLINE_k3 ?= "console=ttyS1,115200n8"
> >> do_configure() {
> >> if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ];
> >>@@ -101,6 +103,16 @@ do_install() {
> >> install -m 0644 ${B}/inmates/demos/${JH_ARCH}/*.bin ${D}${INMATES_DIR}
> >> install -d ${D}/boot
> >>+ if [ -n "${JH_RAMFS_IMAGE}" ]
> >>+ then
> >>+ if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ]
> >>+ then
> >>+ install -m 0644 ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> >>+ else
> >>+ bbwarn "Could find find JH_RAMFS_IMAGE (${JH_RAMFS_IMAGE}-${MACHINE}.cpio)!"
> >Typo in the message. Also, should it be an error instead of a warning?
>
>
> I did not want this recipe to force the requirement for an ramfs. But
> thinking about it now, making it an error is better in case the linux-demo
> is desired. If it is not, then JH_RAMFS_IMAGE can be unset in some conf.
Thanks. Can you do a v4 of all 3 patches quickly to address the comments in
1/3 and 3/3, so I can merge them in for rc4? Thanks again.
> >>+ bbwarn "Please make sure that \"cpio\" is in IMAGE_FSTYPES."
> >>+ fi
> >>+ fi
> >> if [ -n "${JH_INMATE_DTB}" -a -n "${JH_LINUX_DEMO_CELL}" ]; then
> >> cd ${TOOLS_SRC_DIR}
> >>@@ -110,6 +122,7 @@ do_install() {
> >> ./jailhouse-cell-linux -w ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
> >> -a ${JH_ARCH} -c "${JH_CMDLINE}" \
> >> -d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
> >>+ -i ${D}/boot/${JH_RAMFS_IMAGE}-${MACHINE}.cpio \
> >> ${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
> >> ${DEPLOY_DIR_IMAGE}/Image \
> >> | tr -cd '\11\12\15\40-\176' \
> >>@@ -143,9 +156,9 @@ CELLS = ""
> >> python __anonymous () {
> >> d.appendVarFlag('do_install', 'depends', ' virtual/kernel:do_deploy')
> >>- initrd = d.getVar('INITRAMFS_IMAGE', True)
> >>- if initrd:
> >>- d.appendVarFlag('do_install', 'depends', ' ${INITRAMFS_IMAGE}:do_image_complete')
> >>+ ramfs = d.getVar('JH_RAMFS_IMAGE', True)
> >>+ if ramfs:
> >>+ d.appendVarFlag('do_install', 'depends', ' ${JH_RAMFS_IMAGE}:do_image_complete')
> >> # Setup DEPENDS and RDEPENDS to included cells
> >> cells = d.getVar('CELLS', True) or ""
> >>--
> >>2.7.4
> >>
> >>--
> >>_______________________________________________
> >>meta-ti mailing list
> >>meta-ti@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2019-08-30 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:11 [master/thud][PATCH v2 1/3] jailhouse: update to ti2019.03-rc2 Jacob Stiffler
2019-08-20 18:11 ` [master/thud][PATCH v2 2/3] jailhouse: provide tools package Jacob Stiffler
2019-08-29 8:41 ` Nikhil Devshatwar
2019-08-30 16:05 ` Denys Dmytriyenko
2019-08-30 16:08 ` Jacob Stiffler
2019-08-30 16:03 ` Denys Dmytriyenko
2019-08-30 16:10 ` Jacob Stiffler
2019-08-30 16:16 ` Denys Dmytriyenko
2019-08-20 18:11 ` [master/thud][PATCH v2 3/3] jailhouse: use ramfs for linux-demo Jacob Stiffler
2019-08-29 8:51 ` Nikhil Devshatwar
2019-08-30 16:23 ` Denys Dmytriyenko
2019-08-30 16:26 ` Jacob Stiffler
2019-08-30 16:31 ` Denys Dmytriyenko
2019-08-30 16:42 ` Jacob Stiffler
2019-08-30 16:50 ` Denys Dmytriyenko
2019-08-30 16:53 ` Jacob Stiffler
2019-08-30 16:13 ` Denys Dmytriyenko
2019-08-30 16:23 ` Jacob Stiffler
2019-08-30 16:29 ` Denys Dmytriyenko [this message]
2019-08-30 16:30 ` Jacob Stiffler
2019-08-30 15:57 ` [master/thud][PATCH v2 1/3] jailhouse: update to ti2019.03-rc2 Denys Dmytriyenko
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=20190830162908.GG3307@beryl \
--to=denys@ti.com \
--cc=j-stiffler@ti.com \
--cc=lokeshvutla@ti.com \
--cc=meta-ti@yoctoproject.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.