hakurei/internal/pipewire/header_test.go, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/internal/pipewire/header_test.go?h=develop2025-11-29T16:39:39Zinternal/pipewire: implement Core::Error2025-11-29T16:39:39ZOphestracat@gensokyo.uk2025-11-29T16:39:39Zurn:sha1:3d4c7cdd9e82d1cc48e2564f4e5a569424a1819b
Sample was captured from pw-cli.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Core::Ping, Core::Pong2025-11-29T14:25:29ZOphestracat@gensokyo.uk2025-11-29T14:23:19Zurn:sha1:4fd6d6c037b30b02aff861542721b0cc40f083fe
I could not get the server to produce these events, however I am confident enough with the implementation to do it by hand.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement SecurityContext::Create2025-11-29T07:46:39ZOphestracat@gensokyo.uk2025-11-29T07:08:31Zurn:sha1:de3fc7ba381988c06fdbb0be8446b8e8d2e75af4
This is finally the thing we are after.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Registry::Bind2025-11-28T18:01:53ZOphestracat@gensokyo.uk2025-11-28T17:58:44Zurn:sha1:5a5c4705dd47c7e27f49526b4ccf0d4c7c1bab5a
This change also adds test cases for messages before this one.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Registry::Global2025-11-27T17:32:45ZOphestracat@gensokyo.uk2025-11-27T16:57:30Zurn:sha1:5c12425d48e7f3aad70a4e712ec35b96653b9935
Dealing with this event reawakened my burning hatred for OOP.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: store sample iovec continuously2025-11-27T15:35:10ZOphestracat@gensokyo.uk2025-11-27T15:34:32Zurn:sha1:72a2601d7461c0e2e24a3f97f19392dc30ee4c68
This removes the need for manual splitting. The understanding of the format is robust enough to allow this to happen anyway.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: shorten test data filenames2025-11-27T11:06:01ZOphestracat@gensokyo.uk2025-11-27T11:06:01Zurn:sha1:2bafde99e352ffec2e35a1e45aaf6c26bf864485
These were getting very annoying to type.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Core::Done2025-11-26T10:02:21ZOphestracat@gensokyo.uk2025-11-26T10:02:21Zurn:sha1:2698ca00e8fad5f7243c1e1b4c078d322854917c
The message in the sample does not correspond to any known method call. The spec does not mention what to do with messages like this, but all existing usage code simply drops it.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: additional Client::Info test case2025-11-26T07:28:57ZOphestracat@gensokyo.uk2025-11-26T07:27:46Zurn:sha1:a55c209099c96101288350043817c5dc50fdb158
This appears to add *one single entry* compared to the message before it. The inefficiency of this protocol is beyond imagination.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: additional Client::Info test case2025-11-26T07:17:38ZOphestracat@gensokyo.uk2025-11-26T07:17:38Zurn:sha1:10ff276da187868be1fa136ffd41ee2904c2cea8
This message follows the other Client::Info event before it. No idea why.
Signed-off-by: Ophestra <cat@gensokyo.uk>