Am 22.11.2010 13:24, schrieb Imre Kaloz:
Hi,
On Sun, 21 Nov 2010 12:37:37 +0100, Marcus Osdoba
marcus.osd...@googlemail.com wrote:
Currently I'm working on improved dockstar support for OpenWrt. The
current toolchain 4.3.3+cs is not that up to date and linaro 4.5 branch
is already included. Unfortunatly, this version does not support Marvell
Feroceon (mtune=marvell-f). The Linaro version 4.4.5 does. So I added
support for 4.4.5+l in OpenWrt, which can be found here:
http://gitorious.org/dockstar/openwrt-trunk/commit/2fcb44e0f16a41ef409aaa9d424e473bf86eb34c.patch
Once done, the kirkwood platforms may point to it by default:
http://gitorious.org/dockstar/openwrt-trunk/commit/b8d23a89c920f3caf8ac7b050b4dab568108f05b.patch
Talked to Linaro. The feroceon optimization has been removed from the
Linaro and CS toolchains because it will never make it upstream, as
Marvell didn't assign it to the FSF. I don't want to have yet another
gcc version, so if you really want this optimization, please submit a
patch to add only that - or we can go back to -mtune=xscale for feroceon
as well.
Thanks for clarifying that. Sorry, I wasn't aware of Marvell's policy.
I think the Feroceon Line started before Marvell bought Intel's Xscale.
So the current Feroceon Cores are a combination of original Marvell
Feroceon and Xscale features. Using only Xscale might cause some feature
loss. The current trunk points to -mtune=marvell-f. If switching to
Linaro gcc 4.5.1 this has to be altered anyway.
I will have a look into the patches for marvell-f support. But
furthermore, I think switching to Xscale as fallback might be more
realistic.
By the way, the kernel probes the mtune=marvell-f ability:
http://kerneltrap.org/mailarchive/git-commits-head/2008/12/31/4552164
Maybe, something similar is possible in OpenWrt, too?
Regards,
Marcus
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
