summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* sdk-manual: Updated section on changing SDK installer title.Scott Rifenbark2018-08-151-3/+9
| | | | | | | | | I added more detail to this section. (From yocto-docs rev: 15beb33eadd03391a1af0c9bad0620cefad2a0e2) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the SDK_TITLE variable descriptionScott Rifenbark2018-08-151-9/+20
| | | | | | | | | | Provided more detail and a cross-reference into the SDK manual where you can change the title through the variable. (From yocto-docs rev: 9617fa70caef48328455a02d5260e536fac19c53) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Added section on changing the default ext. SDK install directoryScott Rifenbark2018-08-151-0/+45
| | | | | | | (From yocto-docs rev: d3f0c7b9e2ddea3fec6f42fc9a3c8806b02119f3) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added SDKEXTPATH variable description.Scott Rifenbark2018-08-151-0/+30
| | | | | | | | | | | | This variable is the default installation directory for the Extensible SDK. By default, it is "poky_sdk". You can override this variable so it needed to be documented. The ideal place to override it is in the distribution configuration file. (From yocto-docs rev: 67eca50fa973073ce6e7975ab66b89b9706c25c0) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Updates to sections for updating installed Ext SDKsScott Rifenbark2018-08-152-20/+29
| | | | | | | | | | | | | | | | There are two sections that deal with this topic. One is from the standpoint of a user using a 3rd party published and installed extensible SDK ("Applying Updates to an Installed Extensible SDK"). The other is from the standpoint of a person providing Extensible SDKs for consumption ("Providing Updates to the Extensible SDK After Installation"). These sections needed some closer examination regarding fully describing what was going on. I provided some re-writes to both. (From yocto-docs rev: 1c60b13b5f1813d6e3688e1efce32b7f31422e86) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Changed title to updating the SDK after installScott Rifenbark2018-08-151-3/+3
| | | | | | | | | | | The title for the section on how to effect changes to an installed extensible SDK is better suited as "Providing Updates to the Extensible SDK AFter Installation." (From yocto-docs rev: 2120ba194abada1769be28ae2737ac12a16adebc) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Fixed grammar errorScott Rifenbark2018-08-151-2/+1
| | | | | | | | | | | In "Providing Updates After Installing the Extensible SDK" section, Step 1 had a bit of a grammar error. Not technically, but it could have been written better. I fixed that. (From yocto-docs rev: 20f1cad5a813697afd99837699bf52a6586893bb) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Updated section on changing title of extensible SDK installerScott Rifenbark2018-08-151-3/+14
| | | | | | | | | | I added more information on how this is done. Still could use a bit of detail on how you actually do it. (From yocto-docs rev: 007bbe40fd11a5f880adf7ad8137d1535f08c815) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated DISTRO_NAME variable description.Scott Rifenbark2018-08-151-0/+40
| | | | | | | | | I provided some real detail on this variable. It was woefully brief. (From yocto-docs rev: 4282fabddc81bf4c0fbd0a641ec4f1e9754660c2) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the DISTRO variable descriptionScott Rifenbark2018-08-151-7/+14
| | | | | | | | | | I added a cross-reference to the "DISTRO_NAME" variable as it is the long version of the distribution name. (From yocto-docs rev: bb5638409faadb9c6a5fbca729e4e6b8a220433d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Grammar fixScott Rifenbark2018-08-151-1/+1
| | | | | | | (From yocto-docs rev: b850e0d520401a52fbba083975f05f529b2b554d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Updates to "Adjusting the Extensible SDK to Suit Build Host"Scott Rifenbark2018-08-151-19/+31
| | | | | | | | | I updated this section with clearer text. (From yocto-docs rev: 433388ff37297d905c465a5f05d93953dfe062c5) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Updates to "Configuring the Extensible SDK" sectionScott Rifenbark2018-08-151-12/+17
| | | | | | | | | | Made improvements to this section and tied the variables together for the explanation. (From yocto-docs rev: de882b81ed8525dee5e10f247cc6f5c8f15e0f72) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Fixed cross-reference wording in SDK_LOCAL_CONF_WHITELISTScott Rifenbark2018-08-151-5/+9
| | | | | | | | | Wording did not match that of similar SDK variables. (From yocto-docs rev: 696eb9ff0b89222dc696adc0bd28247c0a0c731a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Fixed grammar error in SDK_INHERIT_BLACKLIST descriptionScott Rifenbark2018-08-151-2/+2
| | | | | | | (From yocto-docs rev: 0a5775f7ad3e0b6531fcfd1d328d8e0da8727400) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added cross-reference to SDK_LOCAL_CONF_BLACKLIST varScott Rifenbark2018-08-151-0/+9
| | | | | | | | | | Put in a cross-reference to the section in the sdk-manual where it talks about customizing the configuration of the extensible SDK. (From yocto-docs rev: 062db19dd56cc1827ebd7614eb8a54660421df62) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the SDK_INHERIT_BLACKLIST variable descriptionScott Rifenbark2018-08-151-3/+16
| | | | | | | | | | | Added information on the class in which the default is set. Also, put in a reference for more information on customizing the extensible SDK configuration. (From yocto-docs rev: a0145996aeac1bb45fea9f613789b00327f92d1e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the SDK_LOCAL_CONF_WHITELIST variable descriptionScott Rifenbark2018-08-151-4/+16
| | | | | | | | | | | Enhanced this description by indicating the class that it is set in and by including a pointer back into the sdk-manual where filters are described for extending the extensible SDK. (From yocto-docs rev: 355b05366aadc337ec3337c0a3c918a23027923b) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the SDK_LOCAL_CONF_BLACKLIST variable descriptionScott Rifenbark2018-08-151-2/+21
| | | | | | | | | | | Added more detail including the class that sets the default variables for exclusion and the list of actual variables that are excluded by default. (From yocto-docs rev: f24287851998d554575c6aaf9dcc50d198931e48) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual, mega-manual: Updated the fig for installed ext. SDKScott Rifenbark2018-08-153-7/+5
| | | | | | | | | | | This figure had changed. I updated the file and folder hierarchy. Also fixed some wording. (From yocto-docs rev: 359292397781f9f5eac2fb693d89ec286ddf9940) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual, mega-manual: Updated standard SDK install directory figureScott Rifenbark2018-08-153-1/+1
| | | | | | | | | | | The figure was incorrect for the installed file and folder hierarchy for a standard SDK. I updated it. This figure goes in both the sdk-manual and the mega-manual. (From yocto-docs rev: a0dc11ce74bba0a18f385d9800f93524340ed033) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Final edits to the extracting root filesystem sectionScott Rifenbark2018-08-151-22/+26
| | | | | | | | | Verified a good example and updated the text to match that example. (From yocto-docs rev: 053467557ef22ce37762222a2997ff9c10be87e8) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Added note in step to set SDKMACHINEScott Rifenbark2018-08-151-0/+14
| | | | | | | | | | | The value of SDKMACHINE must match the architecture of the machine on which the SDK installer is being built if you are building an installer for an extensible SDK. I added a note to this effect. (From yocto-docs rev: ffdd9a9d00cccf270b5aa236279e6eeea0ff47ed) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: utils/md5_file: don't iterate line-by-lineRoss Burton2018-08-151-4/+9
| | | | | | | | | | | | | | | Opening a file in binary mode and iterating it seems like the simple solution but will still break on newlines, which for binary files isn't really useful as the size of the chunks could be huge or tiny. Instead, let's be a bit more clever: we'll be MD5ing lots of files, but we don't want to fill up memory: use mmap() to open the file and read the file in 8k blocks. (Bitbake rev: a0ac8d67f1471a0c611d691b856fede67efb53f6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: fixes for the compatibility interfaceAndrej Valek2018-08-152-0/+59
| | | | | | | | | | | | | Use a heap allocated string to set arg_ifname, since a stack allocated one would be lost after the function returns. (This last one broke the case where an interface name was suffixed with a dot, such as in `resolvconf -a tap0.dhcp`.) (From OE-Core rev: 48775d2f02d6d4024403796b81d6398f3028b965) Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Simon Ausserlechner <simon.ausserlechner@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: package Marvel usb 8997 firmwareJoshua Watt2018-08-151-0/+6
| | | | | | | | | | Add package for the firmware required by the Marvell 8997 chipset when connected over USB. (From OE-Core rev: 650a33d88abfa42936b61465d2a4d42da53d4018) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libunwind: Fix build with musl+security flagsKhem Raj2018-08-151-0/+2
| | | | | | | | | | Fixes src/os-linux.c:63: undefined reference to `__stack_chk_fail_local' (From OE-Core rev: 43894faa45884dcc3b6111ed67e1a96fbec019a8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: Support building allarch recipes againPeter Kjellerstedt2018-08-152-0/+29
| | | | | | | | | This registers "allarch" as a known CPU family. (From OE-Core rev: f12b64e9332e3988953f87d8cea39ca309be5046) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: Split validate-cpu.patch in threePeter Kjellerstedt2018-08-154-45/+115
| | | | | | | | | | | This makes it more suitable to work with, e.g., devtool. It also prepares for the update to 0.47.0 when the first patch will no longer be needed (as it is a backport). (From OE-Core rev: e1297f9a951b1dbafd0e211be63b348f06b1f3cd) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglinfo: Fix build with raspberrypi with userland graphics driverKhem Raj2018-08-152-1/+33
| | | | | | | | | | Let pkgconfig figure out headers and libraries instead of manually forcing waf to do it. (From OE-Core rev: 283026adda7c184e213dacd7f4e42678c304866a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Fix dirent struct alignment issue seen on armv5teKhem Raj2018-08-151-1/+1
| | | | | | | | | | | | | | | | - its a general problem however observed on armv5te based boards in OE other arches either have ways to compensate for misaligned access in hardware or compiler does not use 8byte alignment - fix internal linux headers Full logs https://git.musl-libc.org/cgit/musl/log/?qt=range&q=9cad27a3dc1a4eb349b6591e4dc8cc89dce32277..1ad8138819ced49851e618c9c063aa0ffc86718c (From OE-Core rev: 5fb668482e06ecd5de70a860d1bb9cef1019c4e8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: exit gracefully with an error message if qemu system is not evaluatedJagadeesh Krishnanjanappa2018-08-151-0/+5
| | | | | | | | | | | | | | | It solves below error: -- snip -- return 'qemu-system-%s' % qbsys UnboundLocalError: local variable 'qbsys' referenced before assignment -- snip -- [YOCTO #12846] (From OE-Core rev: 519273f54c0b8a6fff36afeb7646d8e37717be22) Signed-off-by: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pcmciautils: remove from oe-coreRoss Burton2018-08-156-197/+0
| | | | | | | | | | PCMCIA is pretty rare these days, so now that the recipe is in meta-oe we can remove it from oe-core. (From OE-Core rev: 0f8dcb9c717201c4b1edf4fa55880b432bfb7723) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Disble TLS for muslKhem Raj2018-08-151-1/+3
| | | | | | | | | | | | | | | | | | | | See https://bugs.freedesktop.org/show_bug.cgi?id=35268 mesa should infact stop using __attribute__((tls_model("initial-exec"))) until then we disale TLS in glx for musl The problem could happen even on glibc if static TLS sizes are large enough which would mean that additional space the glibc leaves for such rogue libraries get consumed and then same problems show up there as well Fixes errors seen in xorg logs e.g. (EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so: Error relocating /usr/lib/libGL.so.1: _ITM_deregisterTMCloneTable: initial-exec TLS resolves to dynamic definition in /usr/lib/libGL.so.1 enable readonly text segment on x86 for musl (From OE-Core rev: f3a59540d0d1f7ab42ba7cb5ff1a26ac3a8a9f68) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/package: Improve test to cover sparseness and hardlinking from sstateRichard Purdie2018-08-151-9/+18
| | | | | | | | | | | The sparseness test was sometimes working and sometimes failing depending on whether sstate was valid. This adds an explict test of sstate to the test for both hardlinking and sparseness. Tweak the test name to cover the fact its tests sparseness too. (From OE-Core rev: fe5b37c07b6d07c350516ab6bf849d6d86a84004) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate/lib.oe.path: Ensure file sparseness is preservedRichard Purdie2018-08-152-4/+4
| | | | | | | | | Files when restored from sstate were missing their sparseness. Fix up various functions to preserve this and make things more deterministic. (From OE-Core rev: 055402e5504f041c346571e243c7cf0894955cad) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: Replace bitbake -p with bitbake -eRichard Purdie2018-08-151-2/+2
| | | | | | | | | | | | | Parsing all the recipes is annoying when trying to re-execute oe-selftest and also unnecessary as its really just a sanity check. When the tests were originally being developed the guard was useful but less so now. Replace it with bitbake -e which is fast and checks the basic configuration is valid. (From OE-Core rev: acec5180b8d2731002979179e08439b615631e70) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure a given machine only removes things which it createdRichard Purdie2018-08-151-1/+16
| | | | | | | | | | | | | | | | | | | | | | Currently if you build qemux86 and then generic86, the latter will remove all of the former from deploy and workdir. This is because qemux86 is i586, genericx86 is i686 and the architctures are compatible therefore the sstate 'cleaup' code kicks in. There was a valid reason for this to ensure i586 packages didn't get into an i686 rootfs for example. With the rootfs creation being filtered now, this is no longer necessary. Instead, save out a list of stamps which a give machine has ever seen in a given build and only clean up these things if they're no longer "reachable". In particular this means the autobuilder should no longer spend a load of time deleting files when switching MACHINE, improving build times. (From OE-Core rev: 5634f2fb1740732056d2c1a22717184ef94405bf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager/sdk: Use filtered copies of the deploy ipk/deb directoriesRichard Purdie2018-08-154-11/+31
| | | | | | | | | | | | Similar to rpm, use copies of the ipk/deb directories for rootfs construction. This means the image creation code can no longer "see" recipes wich aren't in its dependency chain which is good for a variety of reasons including determinism, incompatible recipe (e.g. systemd/sysvinit) package conflicts and locking performance. (From OE-Core rev: c7c5f4065c102fde4e11d138fb0b6e25bffe0379) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager: Remove rpm specific pieces of create_packages_dir()Richard Purdie2018-08-151-13/+11
| | | | | | | | | This function is generic, tweak the variable names and move out the rpm specific directory name to make it truly generic and reusable for deb/ipk. (From OE-Core rev: dba876639b1fb8ea3ccb182c91e19966c4052115) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Fix locale archive path patchRichard Purdie2018-08-151-9/+45
| | | | | | | | | | The locale code uses the archive location in two places, ensure both are corrected to use the environment variable which avoids nasty build failures when archiving locales in images. (From OE-Core rev: 3ab1249a2ac92a0fcb008e92cc9ee272441408f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image: Add locale archive optimisationRichard Purdie2018-08-153-48/+54
| | | | | | | | | | | | | Refactor the locale archive function from the SDK to also make it work during general image creation. This reduces the size of the locales from 900MB to 220MB in core-image-lsb-sdk. The exception handling around subprocess was dropped as the standard subprocess exception printing is better handled than the catchall exception. (From OE-Core rev: 8ffd93bdb09b0a4a84b27dafcd684c6abba392ed) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/package: Add test to ensure sparse files are preservedRichard Purdie2018-08-152-0/+7
| | | | | | | | | | Add a new element to the hardlink test to check we also preseve file sparseness during the packing process. This should ensure we don't regress this issue again. (From OE-Core rev: 0a4e6974b49bf68c4a4098d339b5d655e202a3fd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-intel: Fix for glibcRichard Purdie2018-08-152-0/+26
| | | | | | | | It fails to build wi9th glibc 2.28, add the missing required header inclusion. (From OE-Core rev: 8f5f23a5a985f5d48973f27c143b0d5edb8ca797) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* screen: Add virtual/crypt dependencyRichard Purdie2018-08-151-1/+1
| | | | | | | | screen uses crypt() so add the missing DEPENDS triggered by glibc 2.28. (From OE-Core rev: 77ca6be2bcac35a54546b0b468a4d68e8cc8b894) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Add make-native dependsRichard Purdie2018-08-152-2/+2
| | | | | | | | | | glibc needs make >= 4 yet some of our build workers have older versions of make. Add a make-native dependency to work around this until all our supported distros have a recent version of make. (From OE-Core rev: 0cd89e4af625941f8ab8c033f72f900a2979b304) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: Fix build with glibc 2.28 + libxcryptKhem Raj2018-08-152-1/+73
| | | | | | | (From OE-Core rev: 87f2683ca19182dbffe48dc70a1f2628658fc08d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ppp, libpam: Add missing dep on virtual/cryptKhem Raj2018-08-152-2/+2
| | | | | | | (From OE-Core rev: 0842bd7093040d1f99ffa0523b993341653b1c87) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Disable crypt support in glibcKhem Raj2018-08-153-4/+3
| | | | | | | | | | Drop packaging libcrypt from 2.28+ onwards We have independent crypt implementation coming from libxcrypt (From OE-Core rev: 6146b8c4216daf56a69f4e3531861302df6a63a2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxcrypt: Upgrade to 4.1.1Khem Raj2018-08-151-3/+3
| | | | | | | | | | | | | license update: Remove CDDL code with Public Domain pieces https://github.com/besser82/libxcrypt/commit/c76847e3be40c4ac0d78bc8518502418c6207144#diff-fdcb2380ff1eeea2e5795ec115ba1c0d inherit pkgconfig as it uses pkg-config during build (From OE-Core rev: 600b1f7da1bc308a52b566b77c994a90ed744b7e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-17 19:47:51 +0000