All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] would anyone object to my updating "Adding a New Machine"?
Date: Wed, 10 Jun 2026 14:54:11 +0200	[thread overview]
Message-ID: <DJ5DUUBC0P89.TN9DME41TLHV@bootlin.com> (raw)
In-Reply-To: <f9054c50-f201-80c3-3338-3003a5748d06@crashcourse.ca>

Hi,

On Tue Jun 9, 2026 at 7:19 PM CEST, Robert P. J. Day wrote:
>
> this section:
>
> https://docs.yoctoproject.org/dev-manual/new-machine.html
>
> is pretty out of date, using the "crownbay" as an example. any
> interest in me updating it to refer to something current, perhaps
> something rockchip like the orangepi-5-plus, which would show how a
> top-level machine definition file recursively includes more and more
> low-level files to fully define a machine?

I don't see how it is out-of-date, the important variables to set are still
valid.

>   or is there some other modern machine definition that would be
> a better example? or is it not worth the trouble?

This document does not seem to make use of an existing machine at the moment,
and points to meta-yocto to find examples. I think it's fine as it is, unless
you think of other variables that should be part of the important ones.

Antonin


      reply	other threads:[~2026-06-10 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 17:19 would anyone object to my updating "Adding a New Machine"? Robert P. J. Day
2026-06-10 12:54 ` Antonin Godard [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=DJ5DUUBC0P89.TN9DME41TLHV@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=rpjday@crashcourse.ca \
    /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.