From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Deacon Subject: Re: Unable to boot mainline on snow chromebook since 3.15 Date: Mon, 8 Sep 2014 12:21:12 +0100 Message-ID: <20140908112112.GK26030@arm.com> References: <20140905115704.GO13515@arm.com> <20140905122232.GP13515@arm.com> <540C202E.2060009@collabora.co.uk> <540C7F5B.6070307@gmail.com> <540C83DE.10505@collabora.co.uk> <540C8577.2070907@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:52289 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752973AbaIHLVz (ORCPT ); Mon, 8 Sep 2014 07:21:55 -0400 Content-Disposition: inline In-Reply-To: <540C8577.2070907@gmail.com> Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: Tomasz Figa Cc: Javier Martinez Canillas , Doug Anderson , "kgene.kim@samsung.com" , "olof@lixom.net" , "rahul.sharma@samsung.com" , "linux-arm-kernel@lists.infradead.org" , "linux-samsung-soc@vger.kernel.org" , Mark Brown On Sun, Sep 07, 2014 at 05:19:03PM +0100, Tomasz Figa wrote: > At least for next 3.17-rc I'd suggest fixing this up in respective clock > driver and dropping the hack only after Exynos DRM patches are merged > and confirmed working. Whilst I'm sympathetic to people working to enable DRM, I think this is the right solution to the problem. The transition from simplefb to DRM shouldn't break display for a bunch of kernel revisions whilst the code is in flux. Will From mboxrd@z Thu Jan 1 00:00:00 1970 From: will.deacon@arm.com (Will Deacon) Date: Mon, 8 Sep 2014 12:21:12 +0100 Subject: Unable to boot mainline on snow chromebook since 3.15 In-Reply-To: <540C8577.2070907@gmail.com> References: <20140905115704.GO13515@arm.com> <20140905122232.GP13515@arm.com> <540C202E.2060009@collabora.co.uk> <540C7F5B.6070307@gmail.com> <540C83DE.10505@collabora.co.uk> <540C8577.2070907@gmail.com> Message-ID: <20140908112112.GK26030@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, Sep 07, 2014 at 05:19:03PM +0100, Tomasz Figa wrote: > At least for next 3.17-rc I'd suggest fixing this up in respective clock > driver and dropping the hack only after Exynos DRM patches are merged > and confirmed working. Whilst I'm sympathetic to people working to enable DRM, I think this is the right solution to the problem. The transition from simplefb to DRM shouldn't break display for a bunch of kernel revisions whilst the code is in flux. Will