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 6B909360 for ; Thu, 8 Sep 2016 08:34:52 +0000 (UTC) Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A77E11C3 for ; Thu, 8 Sep 2016 08:34:50 +0000 (UTC) Received: by mail-oi0-f53.google.com with SMTP id y2so61483404oie.0 for ; Thu, 08 Sep 2016 01:34:50 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <57C78BE9.30009@linaro.org> <20160905111105.GW3950@sirena.org.uk> <20160905140327.a6wgdl3lr42nlww4@thunk.org> <9895277.d39OTXtlqC@avalon> <20160906133429.5ktkvafprbtxr5sd@localhost> From: Linus Walleij Date: Thu, 8 Sep 2016 10:34:48 +0200 Message-ID: To: Olof Johansson Content-Type: text/plain; charset=UTF-8 Cc: James Bottomley , "ltsi-dev@lists.linuxfoundation.org" , "ksummit-discuss@lists.linuxfoundation.org" , "gregkh@linuxfoundation.org" Subject: Re: [Ksummit-discuss] [Stable kernel] feature backporting collaboration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Sep 6, 2016 at 6:46 PM, Olof Johansson wrote: > Chrome OS was successful in this (if I might say so myself), getting > several vendors who earlier had very thin upstream presence to > significantly improve. I haven't seen all that many other projects > being able to do it, but for those of you who are in positions to help > steer SoC choices, do keep this in mind, work with your internal > development teams to make them understand the importance of this, and > make it a priority. Actually what you did with SoC vendors from Chrome OS and stating clearly that upstream presence is a factor in procurement was the *only* thing I have ever seen that actually works to change the behaviour of an entire company, apart from dedicated individuals on the inside of the companies. It got one major SoC vendor "hooked" on upstreaming to the point that they have now come around to internalize that way of working, at least partly. So Chrome OS SoC procurement did good. You should be proud. When it comes to Android, as I think I remarked in the past, the problem since its inception is that the Android people making Nexus devices (or whatever they will call it now) have traditionally thought of themselves as inferior by being tied to someone actually doing the hardware such as HTC, Samsung, LG etc, and they see it as those companies are doing the actual procurement of components and SoC, where BSP software is just another "component". The day the Android people say that for a Nexus(-ish) device it's gonna be all upstream kernel and they will pick the SoC that delivers that, then things will happen. But as it seems, they are not doing the SoC pick, it is done by someone else. But I guess they *do* pick which company will make the Nexus-ish device and they could communicate this along to them. They can also say "upstream strategy document or no playstore for you" to all handset and tablet vendors any day, but I guess it would be percieved as too aggressive. But I would personally have used that hammer immediately. Yours, Linus Walleij