[OpenWrt-Devel] Fwd: [RFC 1/2] Add support for the apm821xx Device Target
chrisrblake93 at gmail.com
Sun Apr 3 10:16:49 EDT 2016
On Fri, Apr 1, 2016 at 8:32 AM, Imre Kaloz <kaloz at openwrt.org> wrote:
> On Fri, 01 Apr 2016 15:26:46 +0200, Chris Blake <chrisrblake93 at gmail.com>
>> Hey Imre,
>> On Fri, Apr 1, 2016 at 7:35 AM, Imre Kaloz <kaloz at openwrt.org> wrote:
>>> Hi Chris,
>>> On Fri, 01 Apr 2016 03:46:09 +0200, Chris Blake <chrisrblake93 at gmail.com>
>>> 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.
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: unhandled signal 5 at 00000000 nip b7e0f60c lr
b7e0f5c8 code 0
[ 1.000192] Kernel panic - not syncing: Attempted to kill init!
[ 1.009293] ---[ end Kernel panic - not syncing: Attempted to kill
It's interesting, as we select all of the same configs that are set by
CONFIG_BLUESTONE , except for APM821xx, even though we already
enable the settings set by APM821xx , but PPC_FPU needs to be
selected by a config to be enabled . 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.
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel