All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 05/13] tools/intel_vbt_decode: Dump AIM offsets
Date: Thu, 11 Apr 2024 15:25:24 +0300	[thread overview]
Message-ID: <875xwo6q8b.fsf@intel.com> (raw)
In-Reply-To: <20240322204125.17212-6-ville.syrjala@linux.intel.com>

On Fri, 22 Mar 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Dump the AIM offsets from the header. I don't think these should
> be actually in ant of modern VBT, but no harm in dumping them out
> anyway.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

> ---
>  tools/intel_vbt_decode.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c
> index ead3dd6450e9..9c0774248e56 100644
> --- a/tools/intel_vbt_decode.c
> +++ b/tools/intel_vbt_decode.c
> @@ -2734,6 +2734,8 @@ static void dump_headers(struct context *context)
>  	printf("\tVBT size:\t\t0x%04x (%u)\n", vbt->vbt_size, vbt->vbt_size);
>  	printf("\tVBT checksum:\t\t0x%02x\n", vbt->vbt_checksum);
>  	printf("\tBDB offset:\t\t0x%08x (%u)\n", vbt->bdb_offset, vbt->bdb_offset);
> +	for (i = 0; i < ARRAY_SIZE(vbt->aim_offset); i++)
> +		printf("\tAIM #%d offset:\t\t0x%08x (%u)\n", i+1, vbt->aim_offset[i], vbt->aim_offset[i]);
>  
>  	printf("\n");

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-04-11 12:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 20:41 [PATCH i-g-t 00/13] tools/intel_vbt_decode: Various improvement Ville Syrjala
2024-03-22 20:41 ` [PATCH i-g-t 01/13] tools/intel_vbt_decode: update vbt defs from kernel Ville Syrjala
2024-04-11 12:20   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 02/13] tools/intel_vbt_decode: Extract default_algorithm() Ville Syrjala
2024-04-11 12:20   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 03/13] tools/intel_vbt_decode: Allow blocks to be named without full decoding Ville Syrjala
2024-04-11 12:22   ` Jani Nikula
2024-04-11 13:12     ` Jani Nikula
2024-04-11 13:15       ` Ville Syrjälä
2024-03-22 20:41 ` [PATCH i-g-t 04/13] tools/intel_vbt_decode: Print the block min size Ville Syrjala
2024-04-11 12:24   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 05/13] tools/intel_vbt_decode: Dump AIM offsets Ville Syrjala
2024-04-11 12:25   ` Jani Nikula [this message]
2024-03-22 20:41 ` [PATCH i-g-t 06/13] tools/intel_vbt_decode: Decode the backlight i2c stuff Ville Syrjala
2024-04-11 12:44   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 07/13] tools/intel_vbt_decode: Decode the obsolote DPST supported field Ville Syrjala
2024-04-11 12:46   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 08/13] tools/intel_vbt_decode: Check version before decoding lace_aggressiveness_profile Ville Syrjala
2024-04-11 13:03   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 09/13] tools/intel_vbt_decode: Add version checks for backlight decoding Ville Syrjala
2024-04-11 13:06   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 10/13] tools/intel_vbt_decode: Dump out the backlight entry size Ville Syrjala
2024-04-11 13:06   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 11/13] tools/intel_vbt_decode: Dump MIPI sequences in the order they appear in VBT Ville Syrjala
2024-04-11 13:08   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 12/13] tools/intel_vbt_decode: Decode all the driver feature bits Ville Syrjala
2024-04-11 13:10   ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 13/13] tools/intel_vbt_decode: Decode the EFP index Ville Syrjala
2024-04-11 13:11   ` Jani Nikula
2024-03-22 23:39 ` ✓ CI.xeBAT: success for tools/intel_vbt_decode: Various improvement Patchwork
2024-03-22 23:56 ` ✓ Fi.CI.BAT: " Patchwork
2024-03-23 22:43 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-13 13:13 ` [PATCH i-g-t 00/13] " Kamil Konieczny

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=875xwo6q8b.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.