Received: by 10.192.165.148 with SMTP id m20csp874561imm; Fri, 20 Apr 2018 18:26:54 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+3ipcLXrPP5VlcI/q/Y+ZQ3WZYtGGBup2pFsc813/ouk+1MC2hx6mErEgHKNvIfSf84OYE X-Received: by 2002:a17:902:9a04:: with SMTP id v4-v6mr12060053plp.21.1524274014448; Fri, 20 Apr 2018 18:26:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524274014; cv=none; d=google.com; s=arc-20160816; b=mp2EeYueDb+8kXJ3TKjccALMh6MixZXp/a7DiYtrJa5QDmRFJncT4GMBhsw8GFuRCX zOvjJhtHvN7/G4EovHDgZDTK11QDvTpngAj9wKO2qUZNOaLC15K7DyP+LF6yRHRa3zJW MBCbqvOpUwC98JNukwkde/z/+ve4PV+LJWbvWF1lOt7tOxG50m37wyvTKM7cWin+SzH3 Aqna2FdZZjZFVVLXNnXiMEm0ho/0+mx/P4otYr5/pTgroWbsI2NstTuskIRFBSIVPsk5 H2pJNsk76dKRACiBLsmFyO/JMt6lFoNbnnUws7xqcjI+3hAIFiHhiPIRFI1MNXeCraxy YM0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :dlp-reaction:dlp-version:dlp-product:content-language :accept-language:in-reply-to:references:message-id:date:thread-index :thread-topic:subject:cc:to:from:arc-authentication-results; bh=+zKgZqB/fTv/5Bj18P+CSIBZOxfunRk0t4MvqlAT6g0=; b=HjoYbiVq/D53tXr43f8xty+C0kjbW3jXbFYxzEivjl13/Z5zh5qfc1mnSaqoO2/n22 UnvCLC5EMBs9hEZrUwrmgo5+ZBi4gGsIU3RobTztwMszN/wr2l/ZloFeyBn+qZy2nugI UtLy8+FhgHmUSj/8OnMOhu9jo+EGLP2zyT7VRC6vzdQGTZSlET/MtDBQoLKZoIZdk4q7 00Zwvc9/sCXDM150v+JVCuAbsRQAe7WmvsZwgWd1PBiDfu5nv2rfKsAn9yPcijquaboB dCxaETmZ8sRgftIgObJwayyMU2STE0/zjQFZLUkFWOcvqZw11rrP7GpO4sdLK/2dRhhH NauQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 64-v6si6527470plb.574.2018.04.20.18.25.58; Fri, 20 Apr 2018 18:26:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752712AbeDUBWE convert rfc822-to-8bit (ORCPT + 99 others); Fri, 20 Apr 2018 21:22:04 -0400 Received: from mga12.intel.com ([192.55.52.136]:61456 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752605AbeDUBWC (ORCPT ); Fri, 20 Apr 2018 21:22:02 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Apr 2018 18:22:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,304,1520924400"; d="scan'208";a="43512815" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by FMSMGA003.fm.intel.com with ESMTP; 20 Apr 2018 18:22:02 -0700 Received: from fmsmsx107.amr.corp.intel.com ([169.254.6.41]) by fmsmsx104.amr.corp.intel.com ([169.254.3.21]) with mapi id 14.03.0319.002; Fri, 20 Apr 2018 18:22:01 -0700 From: "Botello Ortega, Luis" To: "Srivatsa, Anusha" , "Vivi, Rodrigo" , Jani Nikula , "Martinez Monroy, Elio" , "Vega, Ricardo" CC: Ian W MORRISON , "airlied@linux.ie" , Greg KH , "intel-gfx@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , "Wajdeczko, Michal" Subject: RE: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake Thread-Topic: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake Thread-Index: AQHT2NWgWvpJYzBMUEC0wyp8I7qceKQKadNw Date: Sat, 21 Apr 2018 01:22:01 +0000 Message-ID: References: <20180411044213.383-1-ianwmorrison@gmail.com> <871sfmhz88.fsf@intel.com> <87lgdugc85.fsf@intel.com> <83F5C7385F545743AD4FB2A62F75B073338FD128@ORSMSX108.amr.corp.intel.com> <87r2nefbnn.fsf@intel.com> <20180420180331.GE3304@intel.com> <83F5C7385F545743AD4FB2A62F75B0733390B83D@ORSMSX108.amr.corp.intel.com> In-Reply-To: <83F5C7385F545743AD4FB2A62F75B0733390B83D@ORSMSX108.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTUzOTc3MjktMWNjYS00NDc5LWE1ODItOTRhMzFiMDNiZWQ2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJwSm9OZnNXUUpGZHJaaWFkek00QWFiNGpVVkhBUDhkZWNtckNRUkNxdVdyaUp0UUFYWlBkeGl6UDFhNnZGUkJLIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.1.200.108] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 of this FW if it is used in top of current drm-tip kernel (4.17-rc0). Best Regards Luis Botello -----Original Message----- From: Srivatsa, Anusha Sent: Friday, April 20, 2018 1:30 PM To: Vivi, Rodrigo ; Jani Nikula ; Botello Ortega, Luis ; Martinez Monroy, Elio Cc: Ian W MORRISON ; airlied@linux.ie; Greg KH ; intel-gfx@lists.freedesktop.org; linux-kernel@vger.kernel.org; stable@vger.kernel.org; dri-devel@lists.freedesktop.org; Wajdeczko, Michal Subject: RE: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake >-----Original Message----- >From: Vivi, Rodrigo >Sent: Friday, April 20, 2018 11:04 AM >To: Jani Nikula >Cc: Srivatsa, Anusha ; Ian W MORRISON >; airlied@linux.ie; Greg KH >; intel-gfx@lists.freedesktop.org; linux- >kernel@vger.kernel.org; stable@vger.kernel.org; dri- >devel@lists.freedesktop.org; Wajdeczko, Michal > >Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for >Geminilake > >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.nikula@linux.intel.com] >> >>Sent: Wednesday, April 11, 2018 5:27 AM >> >>To: Ian W MORRISON >> >>Cc: Vivi, Rodrigo ; Srivatsa, Anusha >> >>; Wajdeczko, Michal >> >>; Greg KH ; >> >>airlied@linux.ie; joonas.lahtinen@linux.intel.com; >> >>linux-kernel@vger.kernel.org; stable@vger.kernel.org; >> >>intel-gfx@lists.freedesktop.org; dri- devel@lists.freedesktop.org >> >>Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE >> >>for Geminilake >> >> >> >>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 kernels which I have tested with the patch. I found that >> >>> earlier kernels didn't support the 'linux-firmware' package >> >>> required to get wifi working on Intel's new Gemini Lake NUC. >> >> >> >>You realize that this patch should have nothing to do with wifi? >> >> >> >>Rodrigo, Anusha, if you think Cc: stable is appropriate, please >> >>indicate the specific versions of stable it is appropriate for. >> > >> > Hi Jani, >> > >> > The stable kernel version is 4.12 and beyond. >> > It is appropriate to add the CC: stable in my opinion >> >> Who tested the firmware with v4.12 and later? We only have the CI >> results against *current* drm-tip. We don't even know about v4.16. >> > >I understand your concerns, but the problem was that our old process >was a bit >(lot?) messed and there was the unreliable time until the firmware >really lands on linux-firmware.git. So MODULE_FIRMWARE call was only >added after firmware was really there on firmware repository but it wasn't about the testing. > >In other words, the bump version patch was merged after tested, but >MODULE_FIRMWARE was left behind because firmware blob took a while to >get pulled into linux-firmware.git and we end up forgetting to add it there. > >In my opinion it should be safe to add the MODULE_FIRMWARE there based >on the tests from when the version was bumped. Luis, Elio, can you guys confirm that this firmware is tested and healthy? And also, give a tested-by to this patch please? Thanks, Anusha >> I'm not going to ack and take responsibility for the stable backports >> unless someone actually comes forward with credible Tested-bys. >> >> BR, >> Jani. >> >> >> > >> > Anusha >> >>BR, >> >>Jani. >> >> >> >>> >> >>>> >> >>>> PS. How is this a "RESEND"? I haven't seen this before. >> >>>> >> >>> >> >>> It is a 'RESEND' for that very reason. I initially sent the patch >> >>> to the same people as a similar patch >> >>> (https://patchwork.kernel.org/patch/10143637/) however after >> >>> realising this omitted required addresses I added them and resent >> >>> the >patch. >> >>> >> >>> Best regards, >> >>> Ian >> >> >> >>-- >> >>Jani Nikula, Intel Open Source Technology Center >> >> -- >> Jani Nikula, Intel Open Source Technology Center >> _______________________________________________ >> dri-devel mailing list >> dri-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/dri-devel