From: Damien Lespiau <damien.lespiau@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915: Per-DDI I_boost override
Date: Fri, 3 Jul 2015 16:25:15 +0100 [thread overview]
Message-ID: <20150703152515.GA25396@strange.ger.corp.intel.com> (raw)
In-Reply-To: <20150703152158.GF5176@intel.com>
On Fri, Jul 03, 2015 at 06:21:58PM +0300, Ville Syrjälä wrote:
> > In the old VBT spec I have, each child_dev_config is supposed to have
> > only 33 bytes. But in this patch you're increasing it to 38. I believe
> > this is what's causing the errors I see when I boot my BDW.
> >
> > Are you sure they increased the VBT's ChildDevInfo to more than 33
> > bytes? I don't have access to your VBT spec right now, so I can't do a
> > proper review or a suggestion on how to fix the problem.
>
> The size depends on the version. On BSW last I looked it was maybe 36 or
> 37 bytes.
>
> I'm not sure we want to change common_child_dev_config since it's meant
> to be some kind of common stuff. So maybe add another member into the
> union for this stuff. Of course that still incrases the size of the union
> so other changes are required to make it work.
>
> Fortunately we copy these things out from the VBT, so I think just
> making sure the memcpy() doesn't try to copy too much and fixing the size
> check should be all that's needed. That would leave any extra we didn't
> fill with the copy zeroed, and if having it zeroed isn't good enough
> we can of course sprinkle more version checks around.
>
> And I guess we should still check that the size is at least 33 bytes
> since that was the official size for the longest time.
So child_dev_size lies to us?
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-03 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 11:28 [PATCH v2] drm/i915: Per-DDI I_boost override Antti Koskipaa
2015-07-03 15:09 ` Paulo Zanoni
2015-07-03 15:21 ` Ville Syrjälä
2015-07-03 15:25 ` Damien Lespiau [this message]
2015-07-03 15:35 ` Ville Syrjälä
2015-07-06 13:00 ` Daniel Vetter
2015-07-03 15:37 ` Antti Koskipää
2015-07-03 15:48 ` Damien Lespiau
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=20150703152515.GA25396@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox