All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org,
	 Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly
Date: Mon, 28 Nov 2022 10:54:16 +0100	[thread overview]
Message-ID: <CANNYZj_pM6M3pBCZDyfcJoq9WbkZSX3bRtHoATeWCNCsUzeWzw@mail.gmail.com> (raw)
In-Reply-To: <458025bf556060dc1e3ef56bafd564d4b998c2fb.camel@linuxfoundation.org>

On Mon, 28 Nov 2022 at 00:58, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> NFS isn't really a dependency of qemu though. The thinking here was
> that you could boot a real board onto an NFS mount from your local
> system for development purposes. That is why it was being included as
> an SDK tool.
>
> Perhaps we should just add it to qemu helper as well to simplify the
> runqemu case?

I'm fine with that, just want to point out that commit history does
not have this justification - meta-* additions of nfs server
dependency specifically talk about qemu only, and sdk packagegroup
commit [1] does not describe the use case. I don't think there's a BSP
where this way of booting is officially supported and documented.

[1] https://git.yoctoproject.org/poky/commit/?h=master-next&id=b5b3825ce6df45b16e1f3e15001da213bc8b0a55

Alex


  reply	other threads:[~2022-11-28  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 21:15 [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly Alexander Kanavin
2022-11-25 21:15 ` [PATCH 2/3] runqemu: do not hardcode the ip address of the nfs server when using tap Alexander Kanavin
2022-11-25 21:15 ` [PATCH 3/3] selftest/runqemu: reenable the nfs rootfs test Alexander Kanavin
2022-11-27 23:58 ` [OE-core] [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly Richard Purdie
2022-11-28  9:54   ` Alexander Kanavin [this message]
2022-11-28 10:15     ` Richard Purdie

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=CANNYZj_pM6M3pBCZDyfcJoq9WbkZSX3bRtHoATeWCNCsUzeWzw@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.