All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/firmware: Correct URL for firmware
Date: Wed, 2 May 2018 13:41:03 -0700	[thread overview]
Message-ID: <20180502204103.GC14581@intel.com> (raw)
In-Reply-To: <83F5C7385F545743AD4FB2A62F75B073339F56D7@ORSMSX108.amr.corp.intel.com>

On Tue, May 01, 2018 at 09:59:10AM -0700, Srivatsa, Anusha wrote:
> 
> 
> >-----Original Message-----
> >From: Vivi, Rodrigo
> >Sent: Monday, April 30, 2018 5:36 PM
> >To: Srivatsa, Anusha <anusha.srivatsa@intel.com>
> >Cc: intel-gfx@lists.freedesktop.org
> >Subject: Re: [PATCH] drm/i915/firmware: Correct URL for firmware
> >
> >On Mon, Apr 30, 2018 at 03:59:28PM -0700, Anusha Srivatsa wrote:
> >> Replace 01.org URL with upstream linux-firmware repo URL.
> >> We no longer release firmware to 01.org.
> >> linux-firmware.git is the ultimate place to find the i915 firmwares.
> >>
> >> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >> Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
> >> ---
> >>  drivers/gpu/drm/i915/intel_uc_fw.h | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/intel_uc_fw.h
> >> b/drivers/gpu/drm/i915/intel_uc_fw.h
> >> index dc33b12..87910aa 100644
> >> --- a/drivers/gpu/drm/i915/intel_uc_fw.h
> >> +++ b/drivers/gpu/drm/i915/intel_uc_fw.h
> >> @@ -30,7 +30,7 @@ struct drm_i915_private;  struct i915_vma;
> >>
> >>  /* Home of GuC, HuC and DMC firmwares */ -#define
> >> INTEL_UC_FIRMWARE_URL
> >"https://01.org/linuxgraphics/downloads/firmware"
> >> +#define INTEL_UC_FIRMWARE_URL
> >"https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
> >firmware.git/tree/i915"
> >
> >this or drm-firmware where we release first before our pull requests are accepted
> >on linux-firmware.git?
> 
> Linux-firmware .git should be where users should refer to. Drm-firmware might have blobs that might fail in the CI runs and not make it to the upstream repo at all.....

Makes total sense.

> 
> >Either way
> >
> >Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> 
> Thanks for the ack. 
> >just let me know what you want to do...
> I think that we need to have linux-firmware repo here.... But let me know if you feel otherwise.

pushed, thanks.

> 
> Regards,
> Anusha 
> >>
> >>  enum intel_uc_fw_status {
> >>  	INTEL_UC_FIRMWARE_FAIL = -1,
> >> --
> >> 2.7.4
> >>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-05-02 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 22:59 [PATCH] drm/i915/firmware: Correct URL for firmware Anusha Srivatsa
2018-04-30 23:22 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-01  0:36 ` [PATCH] " Rodrigo Vivi
2018-05-01 16:59   ` Srivatsa, Anusha
2018-05-02 20:41     ` Rodrigo Vivi [this message]
2018-05-01  1:32 ` ✗ Fi.CI.IGT: failure for " Patchwork

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=20180502204103.GC14581@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=anusha.srivatsa@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 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.