From: Jani Nikula <jani.nikula@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Herbert, Marc" <marc.herbert@intel.com>,
"Deak, Imre" <imre.deak@intel.com>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/dmc: Accept symbolic link in firmware name
Date: Mon, 01 Aug 2016 16:24:49 +0300 [thread overview]
Message-ID: <87r3a8tye6.fsf@intel.com> (raw)
In-Reply-To: <1468967914.1777.172.camel@intel.com>
On Wed, 20 Jul 2016, "Vivi, Rodrigo" <rodrigo.vivi@intel.com> wrote:
> We don't hardcode all userspace libraries in the userspace side for
> the graphics stack and we do not validate all possible combinations of
> libdrm, mesa, ddx, libva, etc... Why should we need this with
> firmware?
Because the firmware blob is more like a binary kernel module that works
with a specific kernel version than an open source userspace component
written on top of a stable ABI.
You do not know what the firmware does, nor what the future versions of
it will do. The kernel provides an ABI with a strict no regressions
policy for its users. The firmware has no such guarantees, and it is
expected to go hand in hand with the operating system versions it has
been validated against. And as I've explained numerous times, we do not
have the resources to validate all kernel releases against all firmware
releases.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-01 13:24 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
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 [this message]
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=87r3a8tye6.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marc.herbert@intel.com \
--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