Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-30 Thread Joonas Lahtinen
Quoting Jani Nikula (2018-04-27 12:20:55) > On Wed, 25 Apr 2018, Ian W MORRISON wrote: > > Can I ask if this is on anyone's radar as I'm concerned this patch will > > stall otherwise? > > Pushed to drm-intel-next-queued, thanks for the patch. > > I opted to drop the Cc:

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-27 Thread Jani Nikula
On Wed, 25 Apr 2018, Ian W MORRISON wrote: > Can I ask if this is on anyone's radar as I'm concerned this patch will > stall otherwise? Pushed to drm-intel-next-queued, thanks for the patch. I opted to drop the Cc: stable for now. This doesn't mean it can't be backported

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-25 Thread Ian W MORRISON
Hi Anusha, Can I ask if this is on anyone's radar as I'm concerned this patch will stall otherwise? I see that the significance of testing with the 4.14 kernel enabled the firmware to be included in the latest Chrome OS kernel (

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-21 Thread Ian W MORRISON
On 21 April 2018 at 11:22, Botello Ortega, Luis wrote: > Hi all: > > We tested GLK DMC 1.04 FW in last week of September 2017, using the latest > drm-tip version for that time (4.14.0-rc2) and according to our results we > could declare this FW as acceptable and

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-20 Thread Botello Ortega, Luis
Hi all: We tested GLK DMC 1.04 FW in last week of September 2017, using the latest drm-tip version for that time (4.14.0-rc2) and according to our results we could declare this FW as acceptable and healthy to be used with kernel version 4.14 . However, we cannot guarantee quality and healthy

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-20 Thread Srivatsa, Anusha
>-Original Message- >From: Vivi, Rodrigo >Sent: Friday, April 20, 2018 11:04 AM >To: Jani Nikula >Cc: Srivatsa, Anusha ; Ian W MORRISON >; airl...@linux.ie; Greg KH >;

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-20 Thread Rodrigo Vivi
On Tue, Apr 17, 2018 at 12:02:52PM +0300, Jani Nikula wrote: > On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote: > >>-Original Message- > >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com] > >>Sent: Wednesday, April 11, 2018 5:27 AM > >>To: Ian W MORRISON

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-20 Thread Ian W MORRISON
On 20 April 2018 at 17:50, Jani Nikula wrote: > On Fri, 20 Apr 2018, Ian W MORRISON wrote: >> I've performed backport testing and some additional analysis as follows: > > What testing did you do beyond booting? Did you run igt? > > BR, > Jani.

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-20 Thread Jani Nikula
On Fri, 20 Apr 2018, Ian W MORRISON wrote: > I've performed backport testing and some additional analysis as follows: What testing did you do beyond booting? Did you run igt? BR, Jani. -- Jani Nikula, Intel Open Source Technology Center

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-19 Thread Ian W MORRISON
On 18 April 2018 at 00:14, Joonas Lahtinen wrote: > Quoting Jani Nikula (2018-04-17 12:02:52) >> On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote: >> >>-Original Message- >> >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com]

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-17 Thread Joonas Lahtinen
Quoting Jani Nikula (2018-04-17 12:02:52) > On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote: > >>-Original Message- > >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com] > >>Sent: Wednesday, April 11, 2018 5:27 AM > >>To: Ian W MORRISON

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-17 Thread Jani Nikula
On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote: >>-Original Message- >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com] >>Sent: Wednesday, April 11, 2018 5:27 AM >>To: Ian W MORRISON >>Cc: Vivi, Rodrigo ;

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-16 Thread Srivatsa, Anusha
>-Original Message- >From: Jani Nikula [mailto:jani.nik...@linux.intel.com] >Sent: Wednesday, April 11, 2018 5:27 AM >To: Ian W MORRISON >Cc: Vivi, Rodrigo ; Srivatsa, Anusha >; Wajdeczko, Michal

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-11 Thread Ian W MORRISON
On 11 April 2018 at 22:27, Jani Nikula wrote: > On Wed, 11 Apr 2018, Ian W MORRISON wrote: >> >> >>> >>> NAK on indiscriminate Cc: stable. There are zero guarantees that older >>> kernels will work with whatever firmware you throw at them.

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-11 Thread Jani Nikula
On Wed, 11 Apr 2018, Ian W MORRISON wrote: > > >> >> NAK on indiscriminate Cc: stable. There are zero guarantees that older >> kernels will work with whatever firmware you throw at them. >> > > I included 'Cc: stable' so the patch would get added to the v4.16 and > v4.15

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-11 Thread Ian W MORRISON
> > NAK on indiscriminate Cc: stable. There are zero guarantees that older > kernels will work with whatever firmware you throw at them. > I included 'Cc: stable' so the patch would get added to the v4.16 and v4.15 kernels which I have tested with the patch. I found that earlier kernels didn't

Re: [Intel-gfx] [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

2018-04-11 Thread Jani Nikula
On Wed, 11 Apr 2018, ianwmorri...@gmail.com wrote: > From: Ian W MORRISON > > As the Geminilake firmware is now merged to linux-firmware.git > use MODUE_FIRMWARE to load the firmware. > > This removes the error message in the dmesg log: > > i915 :00:02.0: Direct