Hello Imre, On Fri, Apr 1, 2016 at 8:32 AM, Imre Kaloz <ka...@openwrt.org> wrote: > On Fri, 01 Apr 2016 15:26:46 +0200, Chris Blake <chrisrblak...@gmail.com> > wrote: > >> Hey Imre, >> >> On Fri, Apr 1, 2016 at 7:35 AM, Imre Kaloz <ka...@openwrt.org> wrote: >>> >>> Hi Chris, >>> >>> On Fri, 01 Apr 2016 03:46:09 +0200, Chris Blake <chrisrblak...@gmail.com> >>> >>>> +CONFIG_BLUESTONE=y >>> >>> >>> >>> I doubt we support that here. >>> >> >> From my understanding, Bluestone is the dev board for the apm821xx, so >> for dependencies shouldn't this be selected? > > > Nope, as we don't support it. > > > Imre >
I did some testing, and it seems that images fail to boot without this set in the kernel config, with the following error: [ 0.979336] Freeing unused kernel memory: 140K (c03b1000 - c03d4000) [ 0.986659] Bad trap at PC: b7e0f60c, SR: 2d000, vector=2010 [ 0.992337] init[1]: unhandled signal 5 at 00000000 nip b7e0f60c lr b7e0f5c8 code 0 [ 1.000192] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000005 [ 1.000192] [ 1.009293] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000005 [ 1.009293] It's interesting, as we select all of the same configs that are set by CONFIG_BLUESTONE [0], except for APM821xx, even though we already enable the settings set by APM821xx [1], but PPC_FPU needs to be selected by a config to be enabled [2]. Because of this, I believe for the apm821xx target we will need to leave this selected unless you have any ideas. We could do a kernel patch to add a new CONFIG_IKAREM target, but then this would need to be done for every device added to this target, which is why I think just leaving CONFIG_BLUESTONE enabled would be the best plan of action. [0]: https://github.com/torvalds/linux/blob/v4.4/arch/powerpc/platforms/44x/Kconfig#L20 [1]: https://github.com/torvalds/linux/blob/v4.4/arch/powerpc/platforms/44x/Kconfig#L346 [2]: https://github.com/torvalds/linux/blob/v4.4/arch/powerpc/platforms/Kconfig.cputype#L169 Thanks, Chris Blake _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel