-
Notifications
You must be signed in to change notification settings - Fork 103
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
platform/DRMFormat: Don't require a
FormatInfo
for each format. (#3463
) We're now using `DRMFormat` in a situation (linux-dmabuf) where: * We don't actually need to care about many the properties of the format, and * We're processing formats submitted by cilents. This means that the existing “throw an exception if we haven't got a `FormatInfo`” approach works badly; we will disconnect clients with a Wayland internal error if they submit buffers in a format we haven't explicitly listed, even though it *would* work if we just treated the format as an opaque identifier. So, don't do that anymore. Instead, store the fourcc code directly in `DRMFormat`, only look up the `FormatInfo` (now `DRMFormat::Info`) when code asks for it. Additionally, we log the first time code asks for the `DRMFormat::Info` for a format we haven't got info for; this way we can fill out the needed formats on an as-noticed basis. Fixes: #3462
- Loading branch information
Showing
10 changed files
with
151 additions
and
111 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
usr/lib/*/libmirplatform.so.29 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.