From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752043AbdJYV2T convert rfc822-to-8bit (ORCPT ); Wed, 25 Oct 2017 17:28:19 -0400 Received: from muru.com ([72.249.23.125]:45576 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751668AbdJYV2Q (ORCPT ); Wed, 25 Oct 2017 17:28:16 -0400 Date: Wed, 25 Oct 2017 14:28:07 -0700 From: Tony Lindgren To: Pavel Machek Cc: pali.rohar@gmail.com, sre@kernel.org, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com, clayton@craftyguy.net, martijn@brixit.nl, sakari.ailus@linux.intel.com, filip.matijevic.pz@gmail.com Subject: Re: 4.13 (and probably all recent) kernels refuse to boot on one Nokia N950, work or another Message-ID: <20171025212806.GA21504@atomide.com> References: <20171025203459.GA22035@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <20171025203459.GA22035@amd> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Pavel Machek [171025 13:36]: > Hi! > > ...hardware should be identical. 3.5.3-nemo kernel seems to work on > both. 4.13-rc2 with display and clock patches boots on phone "S", but > does not on phone "P"; nothing nothing is received on serial port. > > There is some difference in the bootloaders: S's bootloader provides > lots of debug info, P's is silent. R&D settings do _not_ have > influence on bootloader. We know P's serial works, as 3.5.3 kernel > prints "Uncompressing linux...booting" there. > > I'll need to return "S" phone and serial cable tommorow. If you have > any ideas, let me know. If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart? Also try booting with mem=512M@0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken? Regards, Tony