Hi.
AFAIK xtensa linux port is currently in bad shape: it doesn't work in the
mainline, it fails to build in the linux-next. The latest working kernels for
xtensa are 2.6.29...31 trees hosted at the git.linux-xtensa.org.
I have a goal to make xtensa arch in the linux mainline usable.
Currently I have a number of patches on top of Linus' tree that allow to build
working allnoconfig, defconfig and allmodconfig kernels for ISS machine with
dc232b and fsf core variants [1]. For the next several weeks I'm planning to
forward-port patches accumulated in linux-xtensa.org git trees and make the
resulting kernels rock-solid. I'd like to restore xtensa participation in the
linux-next. Further (currently undetailed) plans are to bring modern Linux
features to the xtensa port, e.g. device trees.
I have a couple of questions regarding the path of xtensa-specific patches
upstream:
- which git tree should they be targeted for? Should I set up a tree for
pull requests, or will patches be picked up into some existing tree?
(Looks like Linus' tree is the right target. AFAIK previously xtensa
patches went mostly through akpm tree).
- which mailing lists should they go to?
(I guess that besides linux-xtensa@xxxxxxxxxxxxxxxx list they should go
to linux-kernel@xxxxxxxxxxxxxxx for general review. Anything else?)
Should you wonder what I am:
I am a member of St.Petersburg Open Source and Linux Lab [2].
My previous contributions to Linux are related to p54spi wireless driver.
I'm also a developer and maintainer of the target-xtensa QEMU port [3].
[1] https://github.com/jcmvbkbc/linux-xtensa
[2] http://osll.spb.ru
[3] http://wiki.qemu.org/Features/Xtensa
--
Thanks.
-- Max
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
