On Tuesday 21 April 2015 16:02:19 Eric Anholt wrote: > > Hard to know. Does anything reference BCM2835_PERIPH_VIRT? Does it work > > if you remove it? > Well, that's clear enough. It dies early with: > > Uncompressing Linux... done, booting the kernel. > [ 0.000000] Booting Linux on physical CPU 0xf00 > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Initializing cgroup subsys cpuacct > [ 0.000000] Linux version 4.0.0-rc1-v7+ (anholt@eliezer) (gcc version 4.9.2 ( 4.9.2-10) ) #487 SMP PREEMPT Tue Apr 21 15:58:29 PDT 2015 > [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache > [ 0.000000] Machine model: Raspberry Pi 2 Model B+ > [ 0.000000] bootconsole [earlycon0] enabled > [ 0.000000] cma: Reserved 64 MiB at 0x37000000 > [ 0.000000] Memory policy: Data cache writealloc > > (hung) > > The only thing I see using this 0xf0000000 range is DEBUG_BCM2836's > serial stuff, though. > Ok. Just to be clear: by removing that mapping, I meant removing the ".map_io = bcm2835_map_io" line as well, so the default debug_ll_io_init() function gets called. If you have a map_io function that does not call debug_ll_io_init() or something equivalent, you cannot use DEBUG_LL. It's possible that this mapping was just added for supporting DEBUG_LL, using the default debug_ll_io_init() is a better way to do that. Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
