Age | Commit message (Collapse) | Author |
|
Integrating Paul Gortmaker's stable update to 4.12, this includes CVE
fixes for meltdown and spectre:
3bb926457832 Linux 4.12.21
76781f72ce64 lguest: disable it vs. removing it.
6ab3176bb365 x86/speculation: Fix typo IBRS_ATT, which should be IBRS_ALL
efa97ecdf026 x86/pti: Mark constant arrays as __initconst
a4d9aaf35e28 x86/spectre: Simplify spectre_v2 command line parsing
1dbde4da259a x86/retpoline: Avoid retpolines for built-in __init functions
7f3a7b69b0f7 x86/paravirt: Remove 'noreplace-paravirt' cmdline option
ebeddfbee13f x86/speculation: Use Indirect Branch Prediction Barrier in context switch
7e0a7c84eb35 x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel
bf0c4c3f38f6 x86/spectre: Fix spelling mistake: "vunerable"-> "vulnerable"
f4d4ccfdf361 x86/spectre: Report get_user mitigation for spectre_v1
12f20abacd8b nl80211: Sanitize array index in parse_txq_params
7686c72bfd9c vfs, fdtable: Prevent bounds-check bypass via speculative execution
a3d62741fc9b x86/syscall: Sanitize syscall table de-references under speculation
0b99c598274c x86/get_user: Use pointer masking to limit speculation
bf532304a22f x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
04584b001618 x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
5a64c3ccd99d x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
9bbc24f34f03 x86: Introduce barrier_nospec
b55fd06d6fe0 x86: Implement array_index_mask_nospec
79a2efa3e0f5 array_index_nospec: Sanitize speculative array de-references
e9046d054bb9 Documentation: Document array_index_nospec
0078d6b103f9 x86/asm: Move 'status' from thread_struct to thread_info
46afe23798a3 x86/entry/64: Push extra regs right away
4213246ab7a8 x86/entry/64: Remove the SYSCALL64 fast path
026a59b9de37 x86/spectre: Check CONFIG_RETPOLINE in command line parser
a345c5f7a1b6 x86/mm: Fix overlap of i386 CPU_ENTRY_AREA with FIX_BTMAP
999e3eca6861 x86/speculation: Simplify indirect_branch_prediction_barrier()
c7acab78a24c x86/retpoline: Simplify vmexit_fill_RSB()
be5c3f1101f7 x86/cpufeatures: Clean up Spectre v2 related CPUID flags
7addf309d0e0 x86/cpu/bugs: Make retpoline module warning conditional
b7c17f71e9cc x86/bugs: Drop one "mitigation" from dmesg
af16629cc1da x86/nospec: Fix header guards names
ebfadec0c9dc x86/alternative: Print unadorned pointers
2e4bcf1ccaa9 x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support
332de1ac4373 x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early Spectre v2 microcodes
79a2a1ba23e7 x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown
d29069565618 x86/msr: Add definitions for new speculation control MSRs
114a7b0f431c x86/cpufeatures: Add AMD feature bits for Speculation Control
2d5755e9daac x86/cpufeatures: Add Intel feature bits for Speculation Control
3f5d9b428f05 x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
2f1b883356ca module/retpoline: Warn about missing retpoline in module
8c935f65cf6a KVM: VMX: Make indirect call speculation safe
79c0d980e610 KVM: x86: Make indirect calls in emulator speculation safe
956ca31407ab x86/retpoline: Remove the esp/rsp thunk
de8cd92003c6 x86/mm/64: Fix vmapped stack syncing on very-large-memory 4-level systems
f2846896cd75 x86/microcode: Fix again accessing initrd after having been freed
badb7498ab69 x86/retpoline: Optimize inline assembler for vmexit_fill_RSB
750d9c97cede x86/pti: Document fix wrong index
8d759c94307d kprobes/x86: Disable optimizing on the function jumps to indirect thunk
59a3c4dc0ab9 kprobes/x86: Blacklist indirect thunk functions for kprobes
2eef7eab7aea retpoline: Introduce start/end markers of indirect thunk
a37c55916910 x86/mce: Make machine check speculation protected
3aab76cd9d88 x86/tsc: Fix erroneous TSC rate on Skylake Xeon
b129f5955cd5 x86/tsc: Future-proof native_calibrate_tsc()
7639b8268579 x86/mm/pkeys: Fix fill_sig_info_pkey
b19a92bb0f18 x86/cpufeature: Move processor tracing out of scattered features
eb5a1177e60b x86/retpoline: Add LFENCE to the retpoline/RSB filling RSB macros
ed114eb7be88 x86/retpoline: Fill RSB on context switch for affected CPUs
70d519c9f97c x86/kasan: Panic if there is not enough memory to boot
01e21b5f7c9c x86/retpoline: Remove compile time warning
8ca1b5f8a9f4 x86,perf: Disable intel_bts when PTI
6f037d7eaeaa security/Kconfig: Correct the Documentation reference for PTI
b8c74586d251 x86/pti: Fix !PCID and sanitize defines
8e24a4722756 selftests/x86: Add test_vsyscall
c3d9420f23cf x86/retpoline: Fill return stack buffer on vmexit
dd182d455654 x86/retpoline/irq32: Convert assembler indirect jumps
d592a8a2c5f5 x86/retpoline/checksum32: Convert assembler indirect jumps
0f3df59f16d3 x86/retpoline/xen: Convert Xen hypercall indirect jumps
c0459b479a22 x86/retpoline/ftrace: Convert ftrace assembler indirect jumps
11edfaeadbd1 x86/retpoline/entry: Convert entry assembler indirect jumps
bf4c91a3b74f x86/retpoline/crypto: Convert crypto assembler indirect jumps
2b243b8623a5 x86/spectre: Add boot time option to select Spectre v2 mitigation
8ab0d792e81c x86/retpoline: Add initial retpoline support
f2f4c0853dba x86/pti: Make unpoison of pgd for trusted boot work for real
7495fd5400e6 x86/alternatives: Fix optimize_nops() checking
8b932f131e26 sysfs/cpu: Fix typos in vulnerability documentation
299b4adfed2e x86/cpu/AMD: Use LFENCE_RDTSC in preference to MFENCE_RDTSC
32996f3a0a81 x86/cpu/AMD: Make LFENCE a serializing instruction
10ffc3c2b2f7 x86/mm/pti: Remove dead logic in pti_user_pagetable_walk*()
9e1201731d4b x86/tboot: Unbreak tboot with PTI enabled
728d879e5c6b x86/cpu: Implement CPU vulnerabilites sysfs functions
aeba317a23de sysfs/cpu: Add vulnerability folder
83e59b5d52bf x86/cpufeatures: Add X86_BUG_SPECTRE_V[12]
f7845c2cbd6e x86/Documentation: Add PTI description
16331e2c3b06 x86/pti: Unbreak EFI old_memmap
5723b0260415 kdump: Write the correct address of mem_section into vmcoreinfo
50d02826dfc0 mm/sparse.c: wrong allocation for mem_section
d3cbfb481af2 mm/sparsemem: Fix ARM64 boot crash when CONFIG_SPARSEMEM_EXTREME=y
(From OE-Core rev: 607b443f2abb915d4d12d6483b26030734983288)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This was removed in the bitbake repository back in 2010 (bitbake
revision 24857e2ceb405916b0b0b3e75c6c2375a909b9ba) - it's not clear
to me what happened, but for some reason the file remained in the poky
repository. However it does not appear that it has been used since then
and the reasons for removing even more valid now than they were then -
the code has moved on even further, we have memory resident bitbake
server, and if we were to re-implement this we would do it in a
different way. Drop the file and bring us back in sync with the bitbake
repo.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Fix typo in shutdown code to kill threads when "kill -0" is not enough.
Use the '--noreload' flag for 'runserver' so that there are no extra
and unaccounted threads.
[YOCTO #12555]
(Bitbake rev: 256990943075e89cb9aee2bc6488344b6783e07b)
Signed-off-by: David Reyna <David.Reyna@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Explicitly capture and ignore errors when trying to load the optional
'custom.xml' fixture file.
[YOCTO #12554]
(Bitbake rev: 132458939d3987ebc58685397714af3d6d5cd8fd)
Signed-off-by: David Reyna <David.Reyna@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(Bitbake rev: 8212446de11c0e370c55f88cde86334b760cd939)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(Bitbake rev: 21098de09ee2f7a9f0b3f895bf2ffbdeb8c9ded5)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Missed the bitbake manual the last time around because it's in a
different directory.
Signed-off-by: Sascha Silbe <x-yo17@se-silbe.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: af7ca3e3596784c5837e9bd339cc7114883ce67a)
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 257a61425075aaace928ce1e2303cd0de2127203)
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
ps: invalid option -- 'e'
BusyBox v1.27.2 (2018-03-17 09:07:25 PDT) multi-call binary.
Usage: ps
(From OE-Core rev: 4bf2d47f7773ffec278192eb337c14953f85e858)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Debian anonscm service in Alioth is shutdown and thus
fetching sources fails.
https://wiki.debian.org/Alioth
"Alioth is broken, and there is nobody around to fix it. Don't ask the remaining people who give it life support to implement fixes and changes. It is being replaced by a cocktail of ?GitLab (see Salsa), read-only repos and keep-alive mechanisms. See below for more information."
https://wiki.debian.org/Salsa
"What is Salsa?
Salsa is the name of a collaborative development server for Debian based on the gitlab software. Salsa is supposed to provide the necessary tools for package maintainers, packaging teams and other Debian related individuals and groups for collaborative development.
What is the status of Salsa?
After various discussions about the future of Alioth, the Alioth Sprint in August 2017 gave birth to the initial setup of the the upcoming Salsa service. The productive weekend resulted in a working prototype and was launched as a beta in December 2017. It left its beta status in January 2018."
(From OE-Core rev: 08ff7b42d8b7d06ef61255185c95e900ada8769b)
Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Debian anonscm service in Alioth is shutdown and thus
fetching ca-certificates sources fails.
https://wiki.debian.org/Alioth
"Alioth is broken, and there is nobody around to fix it. Don't ask the remaining people who give it life support to implement fixes and changes. It is being replaced by a cocktail of ?GitLab (see Salsa), read-only repos and keep-alive mechanisms. See below for more information."
(From OE-Core rev: fc20ff2003cee7ee3b78ba3bc236a60a8caabc35)
Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Debian anonscm service in Alioth is shutdown and thus
fetching ncurses sources fails.
https://wiki.debian.org/Alioth
"Alioth is broken, and there is nobody around to fix it. Don't ask the remaining people who give it life support to implement fixes and changes. It is being replaced by a cocktail of ?GitLab (see Salsa), read-only repos and keep-alive mechanisms. See below for more information."
(From OE-Core rev: 8fab5794218445ddb3e8f73a74fa3f130e7c42f6)
Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Backport fix from qemu mainline for intermediate qemuarm64 hang
issue. Root caused in OE environment, issue with aarch64 qemu
logic of executing instructions that reenabe interrupts. See patch
commit message for more details.
Upstream-Status: Backport
(From OE-Core rev: aa33945fc7cf7bfa859c4091bcfa2695c422849b)
Signed-off-by: Victor Kamensky <kamensky@cisco.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Apparently there are recipes in the wild which generate files with
filenames containing '$' characters - which cause errors during
packaging.
Instead of adding another special case to escape '$' characters when
constructing the command passed to oe.utils.getstatusoutput(), switch
to using single quotes to quote the path - and therefore make isELF()
consistent with the way filenames and paths are quoted by every other
caller of oe.utils.getstatusoutput() in oe-core.
(From OE-Core rev: 7877761534b0c2492da6289e9f2269d41b6ed464)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Although get_filesystem_id() is a private API and never gets passed
a path containing spaces or other special characters, etc, quote the
path anyway for consistency.
(From OE-Core rev: 1a9878cdb1cdb807c47e852b780c8ef9b93a214e)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 1c8887ec629516333cbe3736bc0f9d24fb08dffe)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Here is full list of fixes
https://sourceware.org/git/?p=glibc.git;a=shortlog;h=df3ff4e49d4ee3cbbdaeb0b1cb5dc2344c08be98;hp=23158b08a0908f381459f273a984c6fd328363cb
(From OE-Core rev: 48cbc4d7f671af3787835cfd491bbe99169b5924)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Fix non-void function 'fix_options' should return a value.
Add function prototype to tcpd.c and miscd.c.
(From OE-Core rev: 01590c04e875968a7137a67d1683c503a6bad396)
Signed-off-by: Oleksiy Obitotskyy <oobitots@cisco.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
With 4.15 kernel systemtap needs update to address systemtap module
compilation issues. It is fixed in later version of systemtap by
PR22551.
Upstream-Status: Backport
(From OE-Core rev: 7425d03729507ac5aff3c75ba20e749beaf3a3d5)
Signed-off-by: Victor Kamensky <kamensky@cisco.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 3e098ef3424e1126aa4b0ecc29e1941efba687b7)
Signed-off-by: Victor Kamensky <kamensky@cisco.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Allow devtool to organize the SRC_URI
(From OE-Core rev: 49aae1d75ff1c6a9643c30a8cc5776a2ffa83dd3)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Use ext4 filesystem instead of ext3 when using the live image to install
on target. wic defaults to ext4 as well.
(From OE-Core rev: db6c3d681807cfef098ead1db098f5268e1eb055)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
* Fix RDEPENDS
* Upstream v1.12_9 is a development version, not a stable release
* Add UPSTREAM_CHECK_REGEX skip development releases
* Drop anonymous python function to "fix" version, which breaks
auto-upgrade-helper (AUH)
* Use LICENSE file for checksum rather than ephemeral META.yml
* License remains the same
Fixes: [YOCTO #12581]
License-Update: use LICENSE file for checksum
(From OE-Core rev: 613fa79adff798e29ec7f72bff6f060a1832bc89)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Pseudo is using a custom configure script that detects if it shall build with
extended file attribute support or not. The check is done by simply calling
'getfattr' provided by attr-native which is not part of the dependency list.
Due to the recent changes (recipe specific sysroot & cleanup of $PATH) this
call fails now when the recipe is being build for the first time (at least
when being build for nativesdk case). Explicitly setting up a dependency to
attr-native just to satisfy configure would be wrong also since the real
dependency is to attr/nativesdk-attr which are already part of the dependency
list (see DEPENDS). Therefore bypass the test in the configure by explicitly
enabling xattr using a configure option available in any case.
(From OE-Core rev: a7381eb16ba2183ed990a009bb8e82b4702f3d98)
Signed-off-by: Andreas Kaufmann <andreas.kaufmann.79@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The 'glamor' PACKAGECONFIG in xserver-xorg creates a dependency on libgbm
which can be satisfied in some cases by mesa, in others by blobs such as mali.
(From OE-Core rev: 5f8050722169a931b8e9078b8757216ba7a84506)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Mesa only PROVIDES these features if they are enabled via PACKAGECONFIG.
Therefore make the PROVIDES conditional depending on whether or not these
features have been enabled.
(From OE-Core rev: 8b1e57eb8c959c0f0a5d9a7e0c2e0811c515ea08)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
replace_glibc_check_with_linux.patch was accepted upstream with
modifications.
(From OE-Core rev: 94cf27ebc5d3e3fafa85f3bb1ca54f606bb411ad)
Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This version has been published at March 21, 2018, and it is a bugfix
only release. It includes several important fixes that were made as
part of 18.0.0 development cycle.
Full list of bug fixes can be see online at:
https://www.mesa3d.org/relnotes/17.3.7.html
(From OE-Core rev: 3601c079e15f3570b9b90cd8775e4e90175d1bb5)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This string is now being presented as "bsp_root_name" in the YP
manual set. A BSP name is essentially "meta-bsp_root_name".
It was being presented in the manual set as "meta-bsp_name",
which is not technically correct.
(From yocto-docs rev: 9ad25836b2b3ca79aa3430be014871f50205cf9e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Fixed the way we refer to a BSP name. It is really
"meta-<bsp_root_name>" rather than "meta-<bsp_name>". The
name is the whole string and not just the root name.
Also added a tip on ordering the layers in the BBLAYERS
variable in the bblayers.conf file. Order is important.
(From yocto-docs rev: 9c56238295f5631c496377616ea98b860253e6f7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This is a layer that contains other layers
(From yocto-docs rev: 0cd1881c18e8a63d5f2f078b03fe4e89fd9c75b5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Reality dictates that the YP does not treat layer naming consistently.
Layers are talked about as the "meta-whatever" layer and never the
"whatever" layer. However, the tooling sometimes appends or uses
just the "whatever" part of the layer name. A good example is the
meta-yocto-bsp configuration file. All the variables in there use
just the root name of a layer's name. In the manuals, I had been
distinguishing the layer name as just the "whatever" part sans
"meta-". I talked about the convention of using "meta-" in front
of layer names, etc. Well, this is confusing in light of how everyone
says a layer's name is "meta-whatever". So, I fixed all this up.
(From yocto-docs rev: 79e52f6ccf4246fc69a460ce9d3a4a18720a9442)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Split this section into two sections: one for creating the layer
using bitbake-layers create-layer and one for adding the layer
to bblayers.conf using bitbake-layers add-layer.
Needed to update some references in the yocto-project-qs and
kernel-dev manuals.
(From yocto-docs rev: 741a29b0cbeaaeaa0ac9155036ace2623938aee3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Fixes [YOCTO #12419]
In the section on runtime package management, I created a "Tip"
box to tell the user about using a location for the package
index information outside of the "deploy" area of the hosts
build directory.
(From yocto-docs rev: 2aee814d3d3ed4052fca332693d5416907ae640e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Provided some key links to help clarify content.
(From yocto-docs rev: 8d27b9946dad89729d30497bcc4de26b9a5c87d9)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From yocto-docs rev: 91cda82ca148c56c18f059eeaa656d3561aed26d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Fixes [YOCTO #12419]
This section was unclear and needed some work. I added text to
help clear things up.
(From yocto-docs rev: 54358a39a5710dbd0cbcfe8dafd2f641ec3863ef)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Added the fact that this variable is really optional. If you
don't use it then you are setting up a package feed URI that
will include all supported arcchitectures for the package.
Using it means you are setting up specific URIs for specific
architectures.
Added a "Tip" note box to show how you can use the variable
to whitelist architectures.
(From yocto-docs rev: 009f3551aa61aaf6459fd24105a2e06511b59da3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
I created a two-bullet "Caution" note to highlight the stuff a
user needs to be aware of that can cause problems.
(From yocto-docs rev: 553bc13e5fd350adb15400afe170e587965929db)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Minor corrections.
(From yocto-docs rev: f7fa509b461d4b187f7f91c184b2de3c619de5a3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From yocto-docs rev: 3a05201aabc4633ffead17a01ed36cd25529595e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From yocto-docs rev: 51dc5dd5362a8e6d6d558a566554bec34764227f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
I took out the sections at the end of the manual that talked
about the yocto-kernel tool. This tool is no longer maintained
and there is no equivalent tool. I also fixed the yocto-bsp
tool to be the bitbake-layers tool. This involved some
consolidation of sections.
I fixed some links in the kernel-dev and toaster-manual.
(From yocto-docs rev: 20cda99b301b6327d816c4a4cfb3511ad25c987c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From yocto-docs rev: a7d13e2e9f9a947e65f969422202f04784724063)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updated this section with minor edits.
(From yocto-docs rev: 1bc1dcda5fbab4a66737653164222f4fc5a7289c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This section had several out-of-date items. They are all up
to date now.
(From yocto-docs rev: 247f3eceeccc645a1b556aea433d4cf66399e962)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Wrong title used in link.
(From yocto-docs rev: aa42a8752af97aaa4f16c89059eef63700ea48f4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This figure was out of date.
(From yocto-docs rev: 8b649ab3c4667a45f263818c2532b18f2dae9464)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Made changes to sync the raspberrypi BSP example to what is
really in the source directories. It was pretty out of date.
Made some minor edits to the sections describing the framework
of the BSP.
(From yocto-docs rev: b222d0988cb365cb1943ee1857e5cfd6b9fe173a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|