summaryrefslogtreecommitdiff
path: root/libs/gui/BufferQueueThreadState.cpp
diff options
context:
space:
mode:
author Steven Moreland <smoreland@google.com> 2018-12-12 14:27:24 -0800
committer Steven Moreland <smoreland@google.com> 2018-12-12 14:51:19 -0800
commit8e0f539cc67d90b0656af44c1247c841168adedd (patch)
treec491bd6fc46fb263ec7af317661af710b3ab0e38 /libs/gui/BufferQueueThreadState.cpp
parentc8aaa44de4e775e90ae47e282a58523095f9ec85 (diff)
lshal: show VINTF column by default.
A HAL can't be retrieved unless it is in the VINTF manifest. This design decision was made so that people add HALs to the manifest as early as possible (this makes sure that the manifest is accurate on a change by change basis). A common problem people face is seeing a HAL in lshal, but because of the above, it can't be retreived. Currently, in order to see manifest information, you either have to dig into the lshal settings or dig into the filesystem. Since one of the most common debugging steps for a HAL is to check lshal for the HAL, having the information right here will help. Even though it doesn't explicitly say what the implications of 'FM' or 'DM' are, reading the lshal help gives a reasonable idea of this, and when a snippet of lshal is shown (either in a bugreport/email etc), it will contain the information required to diagnose the issue. This CL also fixes a couple bits of documentation in lshal and adjusts the formatting of the output slightly to break up table descriptions from the output. Change-Id: I2bdc08a8b48b8b78a4b143cc4a7cfdfbef62622d Fixes: 120871371 Test: lshal (manual)
Diffstat (limited to 'libs/gui/BufferQueueThreadState.cpp')
0 files changed, 0 insertions, 0 deletions