From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [i-g-t PATCH 2/5] intel_bios_reader: check mipi sequence block version
Date: Mon, 21 Dec 2015 17:05:53 +0200 [thread overview]
Message-ID: <1450710356-9594-2-git-send-email-jani.nikula@intel.com> (raw)
In-Reply-To: <1450710356-9594-1-git-send-email-jani.nikula@intel.com>
Bail out on v3+, we don't support that just yet.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
tools/intel_bios_reader.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/tools/intel_bios_reader.c b/tools/intel_bios_reader.c
index e308eaa081d6..09ca50d44a77 100644
--- a/tools/intel_bios_reader.c
+++ b/tools/intel_bios_reader.c
@@ -1036,6 +1036,11 @@ static void dump_mipi_sequence(const struct bdb_block *block)
return;
}
+ printf("\tSequence block version v%u\n", sequence->version);
+
+ if (sequence->version >= 3)
+ return;
+
block_size = get_blocksize(sequence);
/*
--
2.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-21 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 15:05 [i-g-t PATCH 1/5] intel_opregion_decode: add new ASLE fields Jani Nikula
2015-12-21 15:05 ` Jani Nikula [this message]
2015-12-21 15:05 ` [i-g-t PATCH 3/5] intel_bios_reader: rewrite the mipi sequence block dumping Jani Nikula
2015-12-21 15:05 ` [i-g-t PATCH 4/5] intel_bios_reader: improve element dumpers Jani Nikula
2015-12-21 15:05 ` [i-g-t PATCH 5/5] intel_bios_reader: add dumping of i2c element in mipi sequence Jani Nikula
2015-12-22 12:22 ` [i-g-t PATCH 1/5] intel_opregion_decode: add new ASLE fields 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=1450710356-9594-2-git-send-email-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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