From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932684AbbLVO0y (ORCPT ); Tue, 22 Dec 2015 09:26:54 -0500 Received: from mail-wm0-f50.google.com ([74.125.82.50]:36262 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754663AbbLVO0x (ORCPT ); Tue, 22 Dec 2015 09:26:53 -0500 Date: Tue, 22 Dec 2015 15:26:49 +0100 From: Alexander Aring To: Eric Anholt Cc: linux-rpi-kernel@lists.infradead.org, Mark Rutland , devicetree@vger.kernel.org, Ian Campbell , Florian Fainelli , Jason Cooper , Scott Branden , Marc Zyngier , Ray Jui , linux-kernel@vger.kernel.org, Rob Herring , bcm-kernel-feedback-list@broadcom.com, Kumar Gala , Thomas Gleixner , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 0/8] Raspberry Pi 2 support. Message-ID: <20151222142643.GB29335@omega> References: <1450310115-22163-1-git-send-email-eric@anholt.net> <20151218100826.GB1145@omega> <20151220221158.GA6416@omega> <874mfbflj3.fsf@eliezer.anholt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <874mfbflj3.fsf@eliezer.anholt.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 21, 2015 at 03:07:44PM -0800, Eric Anholt wrote: ... > > > > But still getting this panic, your patches does not contain some > > defconfig, so I still try to figure out what I need to enable to get it > > working. Maybe it is some missing config entry which should be enabled. > > > > But, for me it looks like some devicetree issue, because of_iomem returns > > NULL, at [0]. Don't know what I am doing wrong. > > My best guess is that since you're not using U-Boot, the firmware's > mangling the DT in some way that breaks us. Notably, in my current > firmware checkout, set /soc/ranges to just the first entry that we're > using, which would break the mapping. However, > rpi/rpi-4.4.y:arch/arm/boot/dts/bcm2709.dtsi uses the same /soc/ranges > setup that we do, so I'm not sure what's going on. Perhaps > bcm2709_io_desc[]'s initialization covers for it? I boot here with two different bootloaders, both ends in the same panic. Finally I figured out if I do a user/kernel split (2G/2G) then the issue is gone. Later I need to enable "CONFIG_HAVE_ARM_ARCH_TIMER" so the kernel doesn't hang forever. After finally booting the RPi2 I get several messages of: unexpected IRQ trap at vector 00 while typing _one_ character over uart. Can you provide somehow your RPi2 kernelconfig? - Alex From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Aring Subject: Re: [PATCH v2 0/8] Raspberry Pi 2 support. Date: Tue, 22 Dec 2015 15:26:49 +0100 Message-ID: <20151222142643.GB29335@omega> References: <1450310115-22163-1-git-send-email-eric@anholt.net> <20151218100826.GB1145@omega> <20151220221158.GA6416@omega> <874mfbflj3.fsf@eliezer.anholt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <874mfbflj3.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Eric Anholt Cc: linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Mark Rutland , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Ian Campbell , Florian Fainelli , Jason Cooper , Scott Branden , Marc Zyngier , Ray Jui , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Rob Herring , bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org, Kumar Gala , Thomas Gleixner , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: devicetree@vger.kernel.org On Mon, Dec 21, 2015 at 03:07:44PM -0800, Eric Anholt wrote: ... > > > > But still getting this panic, your patches does not contain some > > defconfig, so I still try to figure out what I need to enable to get it > > working. Maybe it is some missing config entry which should be enabled. > > > > But, for me it looks like some devicetree issue, because of_iomem returns > > NULL, at [0]. Don't know what I am doing wrong. > > My best guess is that since you're not using U-Boot, the firmware's > mangling the DT in some way that breaks us. Notably, in my current > firmware checkout, set /soc/ranges to just the first entry that we're > using, which would break the mapping. However, > rpi/rpi-4.4.y:arch/arm/boot/dts/bcm2709.dtsi uses the same /soc/ranges > setup that we do, so I'm not sure what's going on. Perhaps > bcm2709_io_desc[]'s initialization covers for it? I boot here with two different bootloaders, both ends in the same panic. Finally I figured out if I do a user/kernel split (2G/2G) then the issue is gone. Later I need to enable "CONFIG_HAVE_ARM_ARCH_TIMER" so the kernel doesn't hang forever. After finally booting the RPi2 I get several messages of: unexpected IRQ trap at vector 00 while typing _one_ character over uart. Can you provide somehow your RPi2 kernelconfig? - Alex -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: alex.aring@gmail.com (Alexander Aring) Date: Tue, 22 Dec 2015 15:26:49 +0100 Subject: [PATCH v2 0/8] Raspberry Pi 2 support. In-Reply-To: <874mfbflj3.fsf@eliezer.anholt.net> References: <1450310115-22163-1-git-send-email-eric@anholt.net> <20151218100826.GB1145@omega> <20151220221158.GA6416@omega> <874mfbflj3.fsf@eliezer.anholt.net> Message-ID: <20151222142643.GB29335@omega> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Dec 21, 2015 at 03:07:44PM -0800, Eric Anholt wrote: ... > > > > But still getting this panic, your patches does not contain some > > defconfig, so I still try to figure out what I need to enable to get it > > working. Maybe it is some missing config entry which should be enabled. > > > > But, for me it looks like some devicetree issue, because of_iomem returns > > NULL, at [0]. Don't know what I am doing wrong. > > My best guess is that since you're not using U-Boot, the firmware's > mangling the DT in some way that breaks us. Notably, in my current > firmware checkout, set /soc/ranges to just the first entry that we're > using, which would break the mapping. However, > rpi/rpi-4.4.y:arch/arm/boot/dts/bcm2709.dtsi uses the same /soc/ranges > setup that we do, so I'm not sure what's going on. Perhaps > bcm2709_io_desc[]'s initialization covers for it? I boot here with two different bootloaders, both ends in the same panic. Finally I figured out if I do a user/kernel split (2G/2G) then the issue is gone. Later I need to enable "CONFIG_HAVE_ARM_ARCH_TIMER" so the kernel doesn't hang forever. After finally booting the RPi2 I get several messages of: unexpected IRQ trap at vector 00 while typing _one_ character over uart. Can you provide somehow your RPi2 kernelconfig? - Alex