| Age | Commit message (Collapse) | Author |
|---|
|
Running intel_bios_reader upon itself causes the reader to crash and
burn. It obviously finds a VBT signature inside the binary, but then
does not rigorously check that all data blocks are valid before
dereferencing them.
Reported-by: Emanuel Bronshtein
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=45205
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
|
|
As a pleasant side effect you can now feed it an opregion dump and it'll
decode without crashing.
Signed-off-by: Adam Jackson <ajax@redhat.com>
|
|
intel_bios_reader.c: In function ‘dump_backlight_info’:
intel_bios_reader.c:192:22: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘unsigned int’ [-Wformat]
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Some of our device class defines were incorrect, and we were missing
several recent ones, so fix those up and dump more child device data if
we have it.
|
|
Actually, fix to work on _any_ machine where the ROM file doesn't match
the GPU. Just extract the device ID from the ROM itself rather than
look at the running system.
Signed-off-by: Adam Jackson <ajax@redhat.com>
|
|
Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
|
|
Signed-off-by: Adam Jackson <ajax@redhat.com>
|
|
Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
|
