This is the hidclass/ntoskrnl/setupapi counterpart to !359. As with that merge request, implementing `BusQueryContainerID` in the bus driver is left out and will be addressed in a different MR.
I believe this is useful to expose the Container ID no matter how those end up being assigned by the bus driver.
--
v10: ntoskrnl: Set device ContainerID from driver
hidclass: Expose ContainerID
hidclass: Copy device ContainerID to child devices
hidclass: Copy ContainerID from underlying driver in driver_add_device
hidclass: Improve error handling in get_device_id
ntoskrnl/tests: Add test for getting SPDRP_BASE_CONTAINERID from PnP driver
setupapi: Add support for SPDRP_BASE_CONTAINERID
https://gitlab.winehq.org/wine/wine/-/merge_requests/432
Gated behind a boolean environment variable WINETEST_COLOR for the moment
(default off).
I've experimented with this locally for a while, and I've found it helps me
immensely when looking for a specific kind of message. Too often failure or
succeeded-inside-todo messages get buried among todo messages, WINEDEBUG output,
or (in the case of some badly written test units) trace() output, but this has
also helped me check whether there are any todo and skip messages, in cases
where I want to make sure that one or the other doesn't show up.
I'm quite open to bikeshedding :-)
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/520
Under Wow64, disabling no-exec (done at the bottom of `alloc_module`) was failing.
Fixes crashes in games using older Steam DRM (where the EXE entry point is in a '.bind' section which is not marked executable)
--
v2: wow64: Allow setting NtSetInformationProcess(ProcessExecuteFlags).
ntdll: Allow changes to DEP flags under Wow64.
https://gitlab.winehq.org/wine/wine/-/merge_requests/500