From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 4FA5A9C for ; Fri, 16 Oct 2015 06:52:44 +0000 (UTC) Received: from sipsolutions.net (s3.sipsolutions.net [5.9.151.49]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C5E628E for ; Fri, 16 Oct 2015 06:52:43 +0000 (UTC) Message-ID: <1444978357.2370.8.camel@sipsolutions.net> From: Johannes Berg To: Rob Herring , Theodore Ts'o Date: Fri, 16 Oct 2015 08:52:37 +0200 In-Reply-To: References: <20151012190137.GA1992@thunk.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] Draft agenda for the kernel summit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2015-10-15 at 19:41 -0500, Rob Herring wrote: > > - Gaps in driver subsystems: > - WiFi - Android gaps: mode switching, P2P, Chromecast, roaming, > ePNO, Passpoint I will be there, I can talk about this if desired, or you can poke me on the hallway to talk about it :) The overwhelming problem isn't our unwillingness to upstream this work though, it's the unwillingness of Google to release requirements early enough to make that possible, along with the unwillingness of chip vendors (hi Broadcom, Qualcomm, MediaTek) to have an upstream driver that they actually use (some of those do support an upstream driver, but don't ship that one and it doesn't nearly have the necessary features, while the actually used (still open source [1]) driver is a pile of spaghetti code that we'd probably never merge upstream...) [1] except for MediaTek, I think, who seem to never be releasing source code for any of their kernels johannes