Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753135AbcKTGaa convert rfc822-to-8bit (ORCPT ); Sun, 20 Nov 2016 01:30:30 -0500 Received: from mga09.intel.com ([134.134.136.24]:49843 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750851AbcKTGa1 (ORCPT ); Sun, 20 Nov 2016 01:30:27 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,520,1473145200"; d="scan'208";a="1071039432" From: "Levy, Amir (Jer)" To: "gregkh@linuxfoundation.org" CC: Simon Guinot , "andreas.noever@gmail.com" , "bhelgaas@google.com" , "corbet@lwn.net" , "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-doc@vger.kernel.org" , "mario_limonciello@dell.com" , thunderbolt-linux , "Westerberg, Mika" , "Winkler, Tomas" , "Zhang, Xiong Y" , "Jamet, Michael" , "remi.rerolle@seagate.com" Subject: RE: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Thread-Topic: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Thread-Index: AQHSOoO1E33Xz8/iJ0iynfF+yxmEQqDQlsUAgAArbLCACQXjgIAErlSQ///6CgCAAwTFwA== Date: Sun, 20 Nov 2016 06:30:19 +0000 Message-ID: References: <1478701208-4585-1-git-send-email-amir.jer.levy@intel.com> <20161109143632.GE6167@kw.sim.vm.gnt> <20161115105920.GH6167@kw.sim.vm.gnt> <20161118100700.GA7126@kroah.com> In-Reply-To: <20161118100700.GA7126@kroah.com> Accept-Language: he-IL, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.184.70.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 989 Lines: 23 On Fri, Nov 18 2016, 12:07 PM, gregkh@linuxfoundation.org wrote: > On Fri, Nov 18, 2016 at 08:48:36AM +0000, Levy, Amir (Jer) wrote: > > > BTW, it is quite a shame that the Thunderbolt firmware version can't > > > be read from Linux. > > > > > > > This is WIP, once this patch will be upstream, we will be able to > > focus more on aligning Linux with the Thunderbolt features that we have > for windows. > > Why is this patch somehow holding that work back? You aren't just sitting > around waiting for people to review this and not doing anything else, right? > Is there some basic building block in these patches that your firmware > download code is going to rely on? > > confused, > > greg k-h All the Thunderbolt SW features (including networking and FW update) depend on the communication with FW, which is patch 3/8 in the series. The patch also sets up a generic netlink for user space communication. So yes, the communication with Thunderbolt FW is a basic building block.