From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: "Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 00/23] tools/intel_vbt_decode: Improve the parser
Date: Wed, 15 Jun 2022 09:44:26 +0300 [thread overview]
Message-ID: <87edzqxw6t.fsf@intel.com> (raw)
In-Reply-To: <20220614233100.13834-1-ville.syrjala@linux.intel.com>
On Wed, 15 Jun 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Change the igt VBT parser to make copies of the BDB data blocks
> (just as we do in the kernel parser now). This makes it less
> hazardous/confusing if your block definition don't happent to
> match reality.
>
> Eg. with the current scheme we could very easily misinterpret
> random bits from other blocks/etc. as our block data by just
> using an overly large structure for decoding. With the block
> copies being at least as big as out struct definitions the
> worst that can happen is that we just decode some extra zeroes
> rather than some random other bits.
>
> The other thing I'm bringing over is the data pointer generation
> stuff for modern VBTS (which lack the LFP data table pointes block).
> That lets us keep decoding the LFP data block in exactly the
> same way on old and new VBTs.
>
> And naturally we have massive gaps in what data the tool actually
> parses from the VBT. So lots of patches to just parse more stuff.
> I didn't do an exhaustive study on this topic, so still probably
> missing some useful things.
I glanced through all this, and it LGTM, but can't claim I did a
detailed, thorough review. I also don't think it should really be
necessary for this particular tool. If the changes work for you, it's
good enough for me.
Cc: Petri, good to go with that?
BR,
Jani.
>
> Ville Syrjälä (23):
> tools/intel_vbt_decode: update vbt defs from kernel
> tools/intel_vbt_decode: Decode more DVO ports
> tools/intel_vbt_decode: Decode mode HDMI data rates
> tools/intel_vbt_decode: Clean up SSC freq decoding
> tools/intel_vbt_decode: Decode DP max link rate
> tools/intel_vbt_decode: Unify panel type handling
> tools/intel_vbt_decode: Dump the block size
> tools/intel_vbt_decode: Decode the LFP power block
> tools/intel_vbt_decode: Dump the LVDS panel options
> tools/intel_vbt_decode: Decode new fast link training rate
> tools/intel_vbt_decode: Parse the old fast link training rate
> correctly
> tools/intel_vbt_decode: Parse the new eDP max link rate
> tools/intel_vbt_decode: Include BDB block header in hex dump
> tools/intel_vbt_decode: Make copies of the BDB blocks
> tools/intel_vbt_decode: Specify a minimum size for the BDB block copy
> tools/intel_vbt_decode: Convert LFP data pointers to be relative to
> the data block
> tools/intel_vbt_decode: Simplify LVDS data block parsing
> tools/intel_vbt_decode: Dump the panel PNP ID
> tools/intel_vbt_decode: Decode the end of the LFP data
> tools/intel_vbt_decode: Dump the LVDS data ptrs
> tools/intel_vbt_decode: Validate LVDS data table pointers
> tools/intel_vbt_decode: Generate LVDS data table pointes if not
> provided
> tools/intel_vbt_decode: Warn if we lack the full definiton of the BDB
> block
>
> tools/intel_vbt_decode.c | 919 ++++++++++++++++++++++++++++++++++-----
> tools/intel_vbt_defs.h | 254 ++++++++---
> 2 files changed, 1018 insertions(+), 155 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-06-15 6:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 23:30 [igt-dev] [PATCH i-g-t 00/23] tools/intel_vbt_decode: Improve the parser Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 01/23] tools/intel_vbt_decode: update vbt defs from kernel Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 02/23] tools/intel_vbt_decode: Decode more DVO ports Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 03/23] tools/intel_vbt_decode: Decode mode HDMI data rates Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 04/23] tools/intel_vbt_decode: Clean up SSC freq decoding Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 05/23] tools/intel_vbt_decode: Decode DP max link rate Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 06/23] tools/intel_vbt_decode: Unify panel type handling Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 07/23] tools/intel_vbt_decode: Dump the block size Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 08/23] tools/intel_vbt_decode: Decode the LFP power block Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 09/23] tools/intel_vbt_decode: Dump the LVDS panel options Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 10/23] tools/intel_vbt_decode: Decode new fast link training rate Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 11/23] tools/intel_vbt_decode: Parse the old fast link training rate correctly Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 12/23] tools/intel_vbt_decode: Parse the new eDP max link rate Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 13/23] tools/intel_vbt_decode: Include BDB block header in hex dump Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 14/23] tools/intel_vbt_decode: Make copies of the BDB blocks Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 15/23] tools/intel_vbt_decode: Specify a minimum size for the BDB block copy Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 16/23] tools/intel_vbt_decode: Convert LFP data pointers to be relative to the data block Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 17/23] tools/intel_vbt_decode: Simplify LVDS data block parsing Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 18/23] tools/intel_vbt_decode: Dump the panel PNP ID Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 19/23] tools/intel_vbt_decode: Decode the end of the LFP data Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 20/23] tools/intel_vbt_decode: Dump the LVDS data ptrs Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 21/23] tools/intel_vbt_decode: Validate LVDS data table pointers Ville Syrjala
2022-06-14 23:30 ` [igt-dev] [PATCH i-g-t 22/23] tools/intel_vbt_decode: Generate LVDS data table pointes if not provided Ville Syrjala
2022-06-14 23:31 ` [igt-dev] [PATCH i-g-t 23/23] tools/intel_vbt_decode: Warn if we lack the full definiton of the BDB block Ville Syrjala
2022-06-15 0:24 ` [igt-dev] ✗ Fi.CI.BAT: failure for tools/intel_vbt_decode: Improve the parser Patchwork
2022-06-15 6:44 ` Jani Nikula [this message]
2022-06-15 8:19 ` [igt-dev] [PATCH i-g-t 00/23] " Petri Latvala
2022-06-22 11:01 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edzqxw6t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox