summaryrefslogtreecommitdiffstats
path: root/bitbake/doc
diff options
context:
space:
mode:
authorAntonin Godard <antonin.godard@bootlin.com>2025-06-30 14:44:59 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-07-31 10:07:21 +0100
commit16dcfbca428ad3a1c184b2deb6f5b50014c4e14c (patch)
tree81154f495810978ecd7483ac1bf32ef9c533e89f /bitbake/doc
parent3475f39be4e60389d8cd81bda9e03c27cc6e956c (diff)
downloadpoky-16dcfbca428ad3a1c184b2deb6f5b50014c4e14c.tar.gz
bitbake: doc/bitbake-user-manual-ref-variables: fixups
Fix typos reported by Quentin here: https://lore.kernel.org/r/cee995db-4c3d-4bf0-813d-ce3f5f8f92e3@cherry.de https://lore.kernel.org/r/73497b5e-721e-4e5f-beb4-c56ab9178c9f@cherry.de Cc: Quentin Schulz <quentin.schulz@cherry.de> (Bitbake rev: add8a7ac093d60e731a638c25ec15efcc3988781) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc')
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst22
1 files changed, 11 insertions, 11 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
index 6be8dbbf63..4ff95ea7ac 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -311,9 +311,9 @@ overview of their function and contents.
311 For example usage, see :term:`BB_GIT_SHALLOW`. 311 For example usage, see :term:`BB_GIT_SHALLOW`.
312 312
313 :term:`BB_GIT_DEFAULT_DESTSUFFIX` 313 :term:`BB_GIT_DEFAULT_DESTSUFFIX`
314 The default destination directory where the Git fetcher unpacks the 314 The default destination directory where the :ref:`Git fetcher
315 source code. If this variable is not set, the source code is unpacked in a 315 <git-fetcher>` unpacks the source code. If this variable is not set, the
316 directory named "git". 316 source code is unpacked in a directory named "git".
317 317
318 :term:`BB_GIT_SHALLOW` 318 :term:`BB_GIT_SHALLOW`
319 Setting this variable to "1" enables the support for fetching, using and 319 Setting this variable to "1" enables the support for fetching, using and
@@ -547,19 +547,19 @@ overview of their function and contents.
547 BB_PRESSURE_MAX_CPU = "15000" 547 BB_PRESSURE_MAX_CPU = "15000"
548 548
549 Multiple values should be tested on the build host to determine what suits 549 Multiple values should be tested on the build host to determine what suits
550 best, depending on the need for performances versus load average during 550 best, depending on the need for performance versus load average during
551 the build. 551 the build.
552 552
553 .. note:: 553 .. note::
554 554
555 You may see numerous messages printed by BitBake in the case the 555 You may see numerous messages printed by BitBake in case the
556 :term:`BB_PRESSURE_MAX_CPU` is too low: 556 :term:`BB_PRESSURE_MAX_CPU` is too low::
557 557
558 Pressure status changed to CPU: True, IO: False, Mem: False (CPU: 1105.9/2.0, IO: 0.0/2.0, Mem: 0.0/2.0) - using 1/64 bitbake threads 558 Pressure status changed to CPU: True, IO: False, Mem: False (CPU: 1105.9/2.0, IO: 0.0/2.0, Mem: 0.0/2.0) - using 1/64 bitbake threads
559 559
560 This means that the :term:`BB_PRESSURE_MAX_CPU` should be increased to 560 This means that the :term:`BB_PRESSURE_MAX_CPU` should be increased to
561 a reasonable value for limiting the CPU pressure on the system. 561 a reasonable value for limiting the CPU pressure on the system.
562 Monitor the varying value after ``IO:`` above to set a sensible value. 562 Monitor the varying value after ``CPU:`` above to set a sensible value.
563 563
564 :term:`BB_PRESSURE_MAX_IO` 564 :term:`BB_PRESSURE_MAX_IO`
565 Specifies a maximum I/O pressure threshold, above which BitBake's 565 Specifies a maximum I/O pressure threshold, above which BitBake's
@@ -584,12 +584,12 @@ overview of their function and contents.
584 BB_PRESSURE_MAX_IO = "15000" 584 BB_PRESSURE_MAX_IO = "15000"
585 585
586 Multiple values should be tested on the build host to determine what suits 586 Multiple values should be tested on the build host to determine what suits
587 best, depending on the need for performances versus I/O usage during the 587 best, depending on the need for performance versus I/O usage during the
588 build. 588 build.
589 589
590 .. note:: 590 .. note::
591 591
592 You may see numerous messages printed by BitBake in the case the 592 You may see numerous messages printed by BitBake in case the
593 :term:`BB_PRESSURE_MAX_IO` is too low:: 593 :term:`BB_PRESSURE_MAX_IO` is too low::
594 594
595 Pressure status changed to CPU: None, IO: True, Mem: False (CPU: 2236.0/None, IO: 153.6/2.0, Mem: 0.0/2.0) - using 19/64 bitbake threads 595 Pressure status changed to CPU: None, IO: True, Mem: False (CPU: 2236.0/None, IO: 153.6/2.0, Mem: 0.0/2.0) - using 19/64 bitbake threads
@@ -623,12 +623,12 @@ overview of their function and contents.
623 BB_PRESSURE_MAX_MEMORY = "15000" 623 BB_PRESSURE_MAX_MEMORY = "15000"
624 624
625 Multiple values should be tested on the build host to determine what suits 625 Multiple values should be tested on the build host to determine what suits
626 best, depending on the need for performances versus memory consumption 626 best, depending on the need for performance versus memory consumption
627 during the build. 627 during the build.
628 628
629 .. note:: 629 .. note::
630 630
631 You may see numerous messages printed by BitBake in the case the 631 You may see numerous messages printed by BitBake in case the
632 :term:`BB_PRESSURE_MAX_MEMORY` is too low:: 632 :term:`BB_PRESSURE_MAX_MEMORY` is too low::
633 633
634 Pressure status changed to CPU: None, IO: False, Mem: True (CPU: 29.5/None, IO: 0.0/2.0, Mem: 2553.3/2.0) - using 17/64 bitbake threads 634 Pressure status changed to CPU: None, IO: False, Mem: True (CPU: 29.5/None, IO: 0.0/2.0, Mem: 2553.3/2.0) - using 17/64 bitbake threads