One crucial component of firmware is the graphics VBT file. Right now, we either have to extract it from stock firmware (and usually guess which one to use), or boot Linux and obtain the working file ourselves.
Describe the solution you'd like
We can find the active, working VBT in debugfs, at /sys/kernel/debug/dri/0/*_vbt, for example i915_vbt. This can be automatically copied and included in the HCL dumps.
Where is the value to a user, and who might that user be?
It would reduce time spent on a trivial, repetitive activity and make the HCL dumps even more useful
The problem you're addressing (if any)
One crucial component of firmware is the graphics VBT file. Right now, we either have to extract it from stock firmware (and usually guess which one to use), or boot Linux and obtain the working file ourselves.
Describe the solution you'd like
We can find the active, working VBT in debugfs, at
/sys/kernel/debug/dri/0/*_vbt
, for examplei915_vbt
. This can be automatically copied and included in the HCL dumps.Where is the value to a user, and who might that user be?
It would reduce time spent on a trivial, repetitive activity and make the HCL dumps even more useful
Describe alternatives you've considered
No response
Additional context
No response