Re: [oe] [meta-multimedia][PATCH 1/2] pipewire: update 1.0.7 -> 1.2.0
On Mon, Jul 1, 2024 at 11:56 AM Markus Volk wrote: > On Mon, Jul 1 2024 at 11:13:51 AM -07:00:00, Khem Raj > wrote: > > Yeah but maybe using arch overrides would be more familiar > > > Can we do this without adding a new line for every architecture? > I will accept your v2 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#111208): https://lists.openembedded.org/g/openembedded-devel/message/111208 Mute This Topic: https://lists.openembedded.org/mt/106959126/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [oe] [meta-multimedia][PATCH 1/2] pipewire: update 1.0.7 -> 1.2.0
On Mon, Jul 1 2024 at 11:13:51 AM -07:00:00, Khem Raj wrote: Yeah but maybe using arch overrides would be more familiar Can we do this without adding a new line for every architecture? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#111207): https://lists.openembedded.org/g/openembedded-devel/message/111207 Mute This Topic: https://lists.openembedded.org/mt/106959126/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [oe] [meta-multimedia][PATCH 1/2] pipewire: update 1.0.7 -> 1.2.0
On Mon, Jul 1, 2024 at 10:31 AM Markus Volk wrote:
> On Mon, Jul 1 2024 at 07:58:28 AM -07:00:00, Khem Raj
> wrote:
>
> riscv32/armv5/mips/ppc32 perhaps is all we care.
>
>
> # Specify linking with -latomic on architectures missing 64bit atomics.
> LDFLAGS += "${@bb.utils.contains_any('TUNE_FEATURES', 'riscv32 armv5 mips
> ppc32 m32', '-latomic', '', d)}"
>
> Would that be enough for now? According to my tests, it fixes the problem
> for clang i686-poky-linux-musl.
>
Yeah but maybe using arch overrides would be more familiar
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#111204):
https://lists.openembedded.org/g/openembedded-devel/message/111204
Mute This Topic: https://lists.openembedded.org/mt/106959126/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [oe] [meta-multimedia][PATCH 1/2] pipewire: update 1.0.7 -> 1.2.0
On Mon, Jul 1 2024 at 07:58:28 AM -07:00:00, Khem Raj
wrote:
riscv32/armv5/mips/ppc32 perhaps is all we care.
# Specify linking with -latomic on architectures missing 64bit atomics.
LDFLAGS += "${@bb.utils.contains_any('TUNE_FEATURES', 'riscv32 armv5
mips ppc32 m32', '-latomic', '', d)}"
Would that be enough for now? According to my tests, it fixes the
problem for clang i686-poky-linux-musl.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#111203):
https://lists.openembedded.org/g/openembedded-devel/message/111203
Mute This Topic: https://lists.openembedded.org/mt/106959126/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [oe] [meta-multimedia][PATCH 1/2] pipewire: update 1.0.7 -> 1.2.0
On Mon, Jul 1, 2024 at 4:42 AM Markus Volk wrote: > > On Sun, Jun 30 2024 at 04:34:47 PM -07:00:00, Khem Raj > wrote: > > perhaps we need to specify linking with -latomic on architectures missing > 64bit atomics. > > > Right. I verified that > LDFLAGS += "-latomic" > fixes the issue for 32bit x86 clang > > Do you know what exact platforms need this fix or should it be included for > all? riscv32/armv5/mips/ppc32 perhaps is all we care. Ideally it would be good to have a global architecture feature to indicate 64bit atomics and we could use that test because this change is sprinkled everywhere. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#111202): https://lists.openembedded.org/g/openembedded-devel/message/111202 Mute This Topic: https://lists.openembedded.org/mt/106959126/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [oe] [meta-multimedia][PATCH 1/2] pipewire: update 1.0.7 -> 1.2.0
On Sun, Jun 30 2024 at 04:34:47 PM -07:00:00, Khem Raj wrote: perhaps we need to specify linking with -latomic on architectures missing 64bit atomics. Right. I verified that LDFLAGS += "-latomic" fixes the issue for 32bit x86 clang Do you know what exact platforms need this fix or should it be included for all? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#98): https://lists.openembedded.org/g/openembedded-devel/message/98 Mute This Topic: https://lists.openembedded.org/mt/106959126/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [oe] [meta-multimedia][PATCH 1/2] pipewire: update 1.0.7 -> 1.2.0
It fails on 32bit x86 clang/lld linker - https://errors.yoctoproject.org/Errors/Details/788619/ perhaps we need to specify linking with -latomic on architectures missing 64bit atomics. On Sun, Jun 30, 2024 at 5:46 AM Markus Volk via lists.openembedded.org wrote: > > PipeWire 1.2.0 (2024-06-27) > > This is the 1.2 release that is API and ABI compatible with previous > 1.1.x and 1.0.x releases. > > This release contains some of the bigger changes that happened since > the 1.0 release last year, including: > > * Support for asynchronous processing has been implemented. Nodes can choose > (or be forced) to be scheduled asynchronously. The graph will not wait for > the output of the node to continue processing but it will use the output > of the previous cycle (or silence) instead. This adds one cycle of latency > but it can avoid having some nodes blocking the processing graph. Non > realtime > streams and filters now also use this asynchronous processing instead of > their own slightly broken version. > * The concept of node.sync-group was added. This groups nodes with > overlapping > sync-group together when one of them sets the node.sync = true. This is > now > used to make sure all nodes are scheduled together when JACK transport is > started so that they all see the same transport time. > * Config parsing errors are reported earlier and much better with line and > column numbers where the parsing started to fail. > * Add support for mandatory metadata when negotiating buffer parameters. > This > can be used to only negotiate extra buffer planes when certain metadata is > negotiated. One use case is the explicit sync support that requires 2 > extra fds for the timelines. > * Explicit sync metadata and support was added. > * Support was added for making and using multiple data-loops in the server > and clients. Support for CPU affinity and priorities was added to the > data-loops as well. > * The log topic debug levels can now be changed at runtime with metadata. > The log levels in the pulse server can be dynamically changed with a > /core message. > * The UCM conflicting devices patches were merged. > * Add snapcast-discover module to stream to snapcast servers. > * Rework how peers are linked and the counters are updated. Resume the > peers when a node is unlinked and not yet processed. This should cause > less occasional dropouts in the graph when reconnecting things. > * Many GStreamer element updates. > * Many more fixes and improvements. > > Enjoy the summer vacation! > > Highlights (since the previous 1.1.83 release) > - Small fixes here and there. > > PipeWire > - Compilation fixes after enabling -Werror=float-conversion > > Modules > - The module-rtp-sap now propagates the cleanup.sec property to the > rtp-source and the rtp-source now sets a property with the receiving > status. > - Fix for ROC 0.3, explicitly specify sender encoding. (#4070) > - Some fixes to the RAOP sink module, including a format fix for 32 bit > machines. > > Tools > - Fix pw-cli monitoring code. > > SPA > - Revert peer_enum_params again because it was not used and flawed. > - Fix multichannel processing in webrtc AEC. > > GStreamer > - Logging improvements. > - Fix a race in the bufferpool activation. > > Bluetooth > - Improvements to BAP broadcast code parsing. > > Older versions: > > PipeWire 1.1.83 (2024-06-17) > > This is the third and hopefully the last 1.2 release candidate that is > API and ABI compatible with previous 1.0.x releases. > > Some last minute changes went in to clean up the node activation and > scheduling that justify another pre-release. > > Highlights > - Rework how peers are linked and the counters are updated. Resume the > peers when a node is unlinked and not yet processed. This should cause > less occasional dropouts in the graph when reconnecting things. > - Improve xruns in module-ffado. > - Many GStreamer element updates. > - More fixes and improvements. > > PipeWire > - Rework how peers are linked and the counters are updated. Resume the > peers when a node is unlinked and not yet processed. This should cause > less dropouts in the graph when reconnecting. (#4026) > - Improve debug of xruns. > - Evaluate node.rules and device.rules before loading the plugin so that > extra properties can be passed to the plugin init function. > > Modules > - Improve timing reporting in module-ffado some more. > - Prealloc less memory in the profiler by default. > - Improve xrun handling in module-ffado. > > Tools > - Fix a crash in pw-link when a link fails. > - Fix pw-dump update for metadata. (#4053) > > SPA > - Improve handling of controls. (#4028) > - Fix the string size in v4l2 to hold the device and vendor id. > - Support meta_videotransform on buffers in v4l2. This can be used to > signal that the buffer was rota
