From: alex.aring@gmail.com (Alexander Aring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] Raspberry Pi 2 support.
Date: Tue, 22 Dec 2015 15:26:49 +0100 [thread overview]
Message-ID: <20151222142643.GB29335@omega> (raw)
In-Reply-To: <874mfbflj3.fsf@eliezer.anholt.net>
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
next prev parent reply other threads:[~2015-12-22 14:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 23:55 [PATCH v2 0/8] Raspberry Pi 2 support Eric Anholt
2015-12-16 23:55 ` [PATCH v2 1/8] irq: bcm2836: Fix initialization of the LOCAL_IRQ_CNT*IRQ timers Eric Anholt
2015-12-16 23:55 ` [PATCH v2 2/8] irq: bcm2836: Add SMP support for the 2836 Eric Anholt
2015-12-17 5:17 ` Baruch Siach
2015-12-16 23:55 ` [PATCH v2 3/8] dt-bindings: Add root properties for Raspberry Pi 2 Eric Anholt
2015-12-19 4:18 ` Rob Herring
2015-12-16 23:55 ` [PATCH v2 4/8] ARM: bcm2835: Split the DT for peripherals from the DT for the CPU Eric Anholt
2015-12-18 10:00 ` Alexander Aring
2015-12-21 23:09 ` Eric Anholt
2015-12-16 23:55 ` [PATCH v2 5/8] ARM: bcm2835: Move the CPU/peripheral include out of common RPi DT Eric Anholt
2015-12-16 23:55 ` [PATCH v2 6/8] ARM: bcm2835: Add devicetree for bcm2836 and Raspberry Pi 2 B Eric Anholt
2015-12-22 10:11 ` Alexander Aring
2015-12-16 23:55 ` [PATCH v2 7/8] ARM: bcm2835: Add a compat string for bcm2836 machine probe Eric Anholt
2015-12-16 23:55 ` [PATCH v2 8/8] ARM: bcm2835: Add Kconfig support for bcm2836 Eric Anholt
2015-12-26 22:38 ` Eric Anholt
2016-01-03 21:53 ` Noralf Trønnes
2015-12-17 0:03 ` [PATCH v2 0/8] Raspberry Pi 2 support Arnd Bergmann
2015-12-17 0:37 ` Eric Anholt
2015-12-17 8:48 ` Stefan Wahren
2015-12-17 10:26 ` Arnd Bergmann
2015-12-18 10:08 ` Alexander Aring
2015-12-18 10:55 ` Alexander Aring
2015-12-20 22:11 ` Alexander Aring
2015-12-21 23:07 ` Eric Anholt
2015-12-22 14:26 ` Alexander Aring [this message]
2015-12-22 19:01 ` Eric Anholt
2015-12-26 21:38 ` Noralf Trønnes
2015-12-21 23:11 ` Arnd Bergmann
2015-12-22 14:20 ` Alexander Aring
2015-12-22 21:23 ` Arnd Bergmann
2015-12-25 0:01 ` Eric Anholt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151222142643.GB29335@omega \
--to=alex.aring@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox