public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: "chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/dmc: Accept symbolic link in firmware name
Date: Mon, 11 Jul 2016 17:01:59 +0300	[thread overview]
Message-ID: <1468245719.30897.43.camel@intel.com> (raw)
In-Reply-To: <20160711135033.GH6157@nuc-i3427.alporthouse.com>

On ma, 2016-07-11 at 14:50 +0100, chris@chris-wilson.co.uk wrote:
> On Mon, Jul 11, 2016 at 04:24:50PM +0300, Imre Deak wrote:
> > On ma, 2016-07-11 at 13:55 +0100, chris@chris-wilson.co.uk wrote:
> > > And then you get random changes in the firmare whilst bisecting
> > > the
> > > kernel.
> > 
> > What do you mean random? During bisecting we want to load the
> > firmware
> > version that was used with a particular commit. With a symlink
> > pointing
> > to the wrong firmware file for a given commit, we'd fail loading
> > the
> > firmware due to the version check and hide/introduce bugs for that
> > commit.
> 
> No. You want to be changing exactly one variable, which means leaving
> the firmware constant.

Hm, not sure. When looking for a working snapshot you also want to
consider bugs introduced by the firmware itself. This is in a way the
exact reason why we want stricter control on the firmware version and
introduced a white list. This also means that loading a firmware
version other than what the driver allows (at a given commit) won't
work anyway.

> The firmware should be side-ways compatible for
> everything with the same minor version (thus resolvable from the same
> symlink), right?

From the same major version I guess it should, but the reason things
don't work that way is why we introduced version white listing.

--Imre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-11 14:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05  9:25 [PATCH] drm/i915/dmc: Accept symbolic link in firmware name Mika Kuoppala
2016-07-05  9:58 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-07-06 17:31 ` [PATCH] " Vivi, Rodrigo
2016-07-07 14:57   ` Mika Kuoppala
2016-07-07 23:47     ` Vivi, Rodrigo
2016-07-11 11:23     ` Imre Deak
2016-07-11 12:39       ` chris
2016-07-11 12:45         ` Imre Deak
2016-07-11 12:55           ` chris
2016-07-11 13:24             ` Imre Deak
2016-07-11 13:50               ` chris
2016-07-11 14:01                 ` Imre Deak [this message]
2016-07-19 21:58                   ` Herbert, Marc
2016-07-19 22:39                     ` Vivi, Rodrigo
2016-07-21 13:32                       ` Imre Deak
2016-08-01 13:24                       ` Jani Nikula
2016-08-03  6:00                         ` Vivi, Rodrigo
2016-08-03  7:25                           ` Daniel Vetter
2016-08-03  9:45                             ` 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=1468245719.30897.43.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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