Board device tree.

It's my understanding that the supported linux kernel is the 3.0.35 version, this is before devicetree came to the arm architecture.

I've not been able to find anything beyond the kernels at https://github.com/embest-tech/linux-imx as mentioned in the users manual.  So it's likely there simply isn't a dts for this board.

Depends on how they've configured the default kernel, but you may be able to get the config used by looking at the contents of /proc/config.gz

Well this helps a little bit but it is not really the way it should be done.

iMX6 has multifunctional IOs and each board use them in different ways. At the given pointer it is rather difficult to know how io muxing has been done.

If you have a look at similar boards like "wandboard" you will see that same IOs are not used for the same functions.

Official linux kernel release provides already support for Wandboard, Olinuxino, Zedboard and other equivalent boards based on A10, A13, A20.

I do not like the idea of having a cooked kernel for this one, I prefer to have the freedom of doing all from scratch.

I asked the question just not to do the work twice. Apparently nobody has done the dts file for this board yet. I'll try to get it done based on latest kernel release. The compiled kernel should be the same for all iMX6 platforms, the only thing that should change is the device tree for each specific board this is the trend to follow on ARM Linux kernels now.

You're absolutely right, devicetree is the way to go today for current kernels. Unfortunate then that this particular board has no upstream support in current kernels, or in upstream u-boot.  Personally, I'm holding off on getting one until there's at least some indication that there's at least a plan to push support upstream. Like you say, it's mostly just an appropriate dts that's needed. The manufacturer not doing it isn't a particularly good sign though. That said, it does appear to be firmly aimed at android, so possibly Linux isn't something they're particularly interested in.

The commit to add RIoT support is this one: https://github.com/embest-tech/linux-imx/commit/a0660f4c989e6874d79b9a6d737b3f9fe7228057

the detail of the pinmux configuration is buried in there, mostly in the board files arch/arm/mach-mx6/board-mx6q_riot.c & arch/arm/mach-mx6/board-mx6dl_riot.h in the way that was normal for Arm before devicetree came along.

Freescale have moved on to a 3.10.17 base kernel here http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/log/?h=imx_3.10.17_1.0.0_beta that does include devicetree, but as far as I can tell there's nothing in there for RIoT either.

You're absolutely right, devicetree is the way to go today for current kernels. Unfortunate then that this particular board has no upstream support in current kernels, or in upstream u-boot.  Personally, I'm holding off on getting one until there's at least some indication that there's at least a plan to push support upstream. Like you say, it's mostly just an appropriate dts that's needed. The manufacturer not doing it isn't a particularly good sign though. That said, it does appear to be firmly aimed at android, so possibly Linux isn't something they're particularly interested in.

The commit to add RIoT support is this one: https://github.com/embest-tech/linux-imx/commit/a0660f4c989e6874d79b9a6d737b3f9fe7228057

the detail of the pinmux configuration is buried in there, mostly in the board files arch/arm/mach-mx6/board-mx6q_riot.c & arch/arm/mach-mx6/board-mx6dl_riot.h in the way that was normal for Arm before devicetree came along.

Freescale have moved on to a 3.10.17 base kernel here http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/log/?h=imx_3.10.17_1.0.0_beta that does include devicetree, but as far as I can tell there's nothing in there for RIoT either.