Hardware plane management
Description
Environment
Activity
Marius Vlad April 22, 2021 at 8:48 AM
The back-end handles/manages indirectly the HW planes. The front-end library has no way of interfering with that. Depending on the HW, on the size and the on pixel format the back-end will attempt to place the view/surface on a HW plane at its disposal, and it happens automatically it is highly optimized to take advantage even with HW planes that are underneath the primary one (in latest libweston version and on the HW that exposes that). I can see two follow-ups on this: a way to determine and debug if the app is using the HW planes optimally and determine why it might not be the case (which we can use with debug scopes to fetch data from the backed-end) and maybe some client examples (ideally this should be in tandem with some HW that has support for additional HW planes). You can safely close this one.
Walt Miner April 21, 2021 at 9:03 PM
. Another old feature request for you take a look at. Is this covered in our current design?

Takashi Matsuzawa March 9, 2018 at 2:13 AM(edited)
Rear veiw camera
Video decode
Some comment on possible use-case / demo scenarios.
Not saying that AGL demo should implement all of these, but the system should be flexible so that vendors can easily integrate such solutions based onto AGL demo.
(e.g. plugin can be written to intercept video stream, etc.)
Simple use-cases to complex ones:
(Simple)
Just showing video streaming (from camera or media player, etc.)
Overlay fixed image (like guidance for parking, captions like "Rear", "Front", compass icon, etc.)
Simple image recoginition. e.g. Can alert if there is little children around car.
(Not really a rear-view, but HUD, etc. use-caseOverlay POIs - like signal post, intersections, etc. based on map information.
Image enhancement - so that images shown on screen is easier to understand, than just showing views of outside (in bad weather, or in the night).
(Complex)

Harunobu Kurokawa March 5, 2018 at 2:45 PM
It's my comment for hardware plane. I think Hardware plane has two issue.
1) When output is rotation (e.g. 270 degree), hardware plane is disable. Current AGL is rotated. In Addition, when surface has scale or any other layer control, I guess weston can use Hardware plane
2) I don't know ivi-shell support it.
Details
Details
Assignee
Reporter

In automotive use case, especially rear view camera is very important feature for safety and performance, FPS, point of view.
So it is perferably captured on a hardware plane which is different one from Weston composing.
Its order and positioning needs to be managed by window manager. We shall define interface as ilm.
Inside of ilm, it would be SoC specific.