Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=master-test 2021-01-21T23:25:53+00:00 2021-01-21T23:25:53+00:00 Wang Mingyu wangmy@cn.fujitsu.com 2021-01-21T08:19:51+00:00 urn:sha1:a640c988d6172917b2f60057a1591ef2e6b0d447 refresh 0002-do-not-display-CLFAGS-to-improve-reproducibility-bui.patch (From OE-Core rev: ebdd0ad4149e2f59012c66e4e261c2bc3404deb7) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-12-21T22:29:57+00:00 Tanu Kaskinen tanuk@iki.fi 2020-12-21T13:51:08+00:00 urn:sha1:26e04aa138750d22e303a772cacd628adc2c5f2f The location of the generated client.conf changed when switching from Autotools to Meson. Fixes this error when enabling autospawn-for-root: sed: can't read src/client.conf: No such file or directory (From OE-Core rev: 16d31a54c586840fb11e03702bb854c43ce4c5eb) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-12-21T22:29:57+00:00 Khem Raj raj.khem@gmail.com 2020-12-20T16:05:35+00:00 urn:sha1:41bb5e7cb7ef0ed8a270971444de469db80dadaa (From OE-Core rev: 01d21bd4c48aa3f899c012a2c3fd72c689e75944) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-12-20T00:03:04+00:00 Tanu Kaskinen tanuk@iki.fi 2020-12-17T19:27:38+00:00 urn:sha1:4b63c75b80bea668bd18c11b6cef2024b017fb64 Upstream is moving from Autotools to Meson, Autotools support will be dropped in 15.0. I dropped some configure options: * --enable-tcpwrap=no doesn't (currently) have a counterpart in Meson, TCP Wrappers support is always disabled. * --disable-esound doesn't have a counterpart in Meson, EsounD support is always disabled. * --disable-gconf doesn't have a counterpart in Meson, GConf support is always disabled. I backported a patch that implements support for the -Dvalgrind=disabled option. I checked with buildhistory what the differences are before and after this patch (with qemuarm with neon removed from TUNE_FEATURES, all PACKAGECONFIGs enabled): * Obvious differences in DEPENDS: Autotools stuff removed and Meson stuff added. There wasn't anything strange here. * Packages have superfluous RDEPENDS removed from them. With Autotools something caused for example X11 libraries to be added to RDEPENDS of packages that don't have anything to do with X11. * The pulseaudio-src package had MMX and SSE related files removed and Neon related files added. I don't know why the ARM build previously had MMX and SSE files included, the addition of Neon files is explained by the fact that with Meson the Neon optimizations can't be disabled if the compiler supports Neon (see below). * libfoo.so symlinks changed to point to libfoo.so.X rather than directly to libfoo.so.X.Y.Z. To my understading that's fine, since libfoo.so.X is a symlink that points to libfoo.so.X.Y.Z. * There were various file size changes, which I didn't investigate. Previously the recipe disabled ARM Neon optimizations when "neon" was not in TUNE_FEATURES. That was originally added in commit 4e7b91b5a2613b957b08aefbee1aac28fdd19598 at a time when PulseAudio's build system didn't check the availability of the arm_neon.h header, causing compilation errors when the header wasn't available. That issue was fixed a long time ago, so there was little need for the TUNE_FEATURES check, although it was still possible to make the build fail if non-neon -mfpu was passed in CFLAGS, so the TUNE_FEATURES check still had some theoretical benefit (theoretical, because generally OE passes -mfpu in CC instead of CFLAGS, so OE's -mfpu option appears very early in the compiler command line, which doesn't trip up PulseAudio's current Autotools build system). With Meson there's no option for disabling Neon optimizations if the compiler supports Neon. If -mfpu is set in CC or CFLAGS, it's ignored, because the build system adds -mfpu=neon at the end of the compiler command line, overriding any earlier -mfpu options. This shouldn't be a problem, because PulseAudio detects at runtime whether the CPU supports Neon instructions. (From OE-Core rev: 80bbea06e706fde3600950ea9ddfc38a1a76b8bb) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-12-20T00:03:04+00:00 Tanu Kaskinen tanuk@iki.fi 2020-12-17T19:27:37+00:00 urn:sha1:b381e01a667b769ebe245b75194c5ef4038cb7b0 The GConf module is only needed for older versions of paprefs, other applications shouldn't be interacting with PulseAudio's GConf settings. Paprefs isn't packaged in OpenEmbedded, so there probably aren't any users of the GConf functionality. My immediate motivation for doing this is that I'm converting the pulseaudio recipe to use Meson, and the GConf module isn't supported by the Meson build system. Adding support for it would be possible, but pretty pointless. The GConf module will be removed in PulseAudio 15.0. (From OE-Core rev: 6e06eb987002031c43f76f908caef240b556e6a1) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-12-20T00:03:04+00:00 Tanu Kaskinen tanuk@iki.fi 2020-12-17T19:27:36+00:00 urn:sha1:94e565c64914dd53de3cd6f0e600a9250eb066b8 This disables PulseAudio's EsounD emulation and the EsounD sink module. EsounD has been obsolete for a long time, and doesn't seem to be packaged for OpenEmbedded, so probably there are no applications around that would need PulseAudio's EsounD support. (From OE-Core rev: ee107217d2deee13d90b737bfb459838f27a94d9) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-12-20T00:03:04+00:00 Tanu Kaskinen tanuk@iki.fi 2020-12-17T19:27:35+00:00 urn:sha1:726a8695994ae67515526d66e915bce49bcf82ce I don't know what these variables were supposed to do, but there doesn't seem to be anything that would use these variables, so removing them should be safe. The PulseAudio recipe is the only place where these appear in the repository. These lines were included already in the original PulseAudio recipe that was added in commit d9a4c588ef24e7e4019fbe5a2314addbcd3a6bb8 in 2007, and already at that time there didn't seem to be anything using these variables. (From OE-Core rev: 7a0b9209a366de7a2aed9b23a337b4ffdba61abe) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-11-29T20:24:32+00:00 zangrc zangrc.fnst@cn.fujitsu.com 2020-11-27T09:19:07+00:00 urn:sha1:098d5bbafae4b0734d642373e1b974be3b876d26 0001-remap-arm-Adjust-inline-asm-constraints.patch 0001-remap_neon-use-register-r12-instead-of-r7.patch Removed since these are included in 14.0. (From OE-Core rev: 5ae2156d971ddd18f13a4377b4f9cc99bd4173fe) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-11-08T14:03:20+00:00 Yi Zhao yi.zhao@windriver.com 2020-11-05T08:05:54+00:00 urn:sha1:56aa4f69c83966921fe70c0edb50d8328d443fd6 Make the volatiles file name start with a numeric value to unified volatiles file naming. I searched in oe-core, only pluseaudio volatiles file name is not start with number. On a default sato-sdk image: $ ls /etc/default/volatiles/ 00_core 01_bootlogd 99_dbus 99_sshd 99_wpa_supplicant volatiles.04_pulse This is just a name change and will not affect the functionality. (From OE-Core rev: 8e7b8db0e6b3f5c7267afca16133e9369a43d45f) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-07-19T15:20:53+00:00 Tanu Kaskinen tanuk@iki.fi 2020-07-18T05:15:55+00:00 urn:sha1:f5731d48a595aba8704b5f5e8602024b49bb71ee By changing the register that PulseAudio uses in its asm code makes it unnecessary to care whether frame pointers are enabled or not. This fix was suggested by Andre McCurdy. (From OE-Core rev: f0a9be4c196c99661cdd18f80bf25281beb04216) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>