Yocto Project Documentation
 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] [PATCH] bsp-guide: simplify example of structure of BSP layer
Date: Fri, 22 May 2026 16:42:33 +0200	[thread overview]
Message-ID: <DIPA9GR9CJJ9.C4CB3DR9RSC9@bootlin.com> (raw)
In-Reply-To: <ea426fa3-2f18-891b-4e9d-c85ff1f0bcd3@crashcourse.ca>

Hi,

On Thu May 21, 2026 at 1:50 PM CEST, Robert P. J. Day wrote:
>
> Rather than introduce a generic example of a BSP layer and follow that
> with a link to meta-yocto-bsp, eliminate the middleman and just show a
> clear hierarchical view of the meta-yocto-bsp layer where readers can
> immediately see the point being made.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst
> index a3b57d29f..1ae9d3353 100644
> --- a/documentation/bsp-guide/bsp.rst
> +++ b/documentation/bsp-guide/bsp.rst
> @@ -1222,22 +1222,28 @@ Project Development Tasks Manual.
>  BSP Machine Configuration Example
>  ---------------------------------
>
> -As mentioned earlier in this section, the existence of a machine
> +As mentioned earlier in this section, the existence of at least one machine
>  configuration file is what makes a layer a BSP layer as compared to a
>  general or kernel layer.
>
> -There are one or more machine configuration files in the
> -``bsp_layer/conf/machine/`` directory of the layer::
> -
> -   bsp_layer/conf/machine/machine1\.conf
> -   bsp_layer/conf/machine/machine2\.conf
> -   bsp_layer/conf/machine/machine3\.conf
> -   ... more ...
> -
> -For example, the machine configuration file for the `BeagleBone and
> -BeagleBone Black development boards <https://beagleboard.org/bone>`__ is
> -located in :yocto_git:`/meta-yocto/tree/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> -</meta-yocto/tree/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf>`.
> +As an actual example, consider the relevant content from the
> +:yocto_git:`/meta-yocto/tree/meta-yocto-bsp/conf/
> +</meta-yocto/tree/meta-yocto-bsp/conf/>` directory of the
> +``meta-yocto-bsp`` BSP layer::
> +

You could use '.. code-block:: console' here (without the :: above).

> +   $ tree -F conf
> +   conf/
> +   ├── layer.conf
> +   └── machine/
> +       ├── beaglebone-yocto.conf
> +       ├── genericarm64.conf
> +       ├── genericx86-64.conf
> +       ├── genericx86.conf
> +       └── include/
> +           └── genericx86-common.inc
> +
> +showing four machine configuration files along with a lower-level
> +tuning configuration file.
>
>  The variables used to configure the machine define machine-specific properties; for
>  example, machine-dependent packages, machine tunings, the type of kernel


Antonin


      reply	other threads:[~2026-05-22 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 11:54 [PATCH] bsp-guide: simplify example of structure of BSP layer Robert P. J. Day
2026-05-22 14:42 ` 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=DIPA9GR9CJJ9.C4CB3DR9RSC9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox