-22 is -EINVAL error. One of possible reasons may be transfer size limitation here: https://github.com/torvalds/linux/blob/master/drivers/spi/spi-sun4i.c#L178
This patch removes this limit http://lists.infradead.org/pipermail/linux-arm-kernel/2015-August/363074.html
but I don't have proper hardware to test it.
I've uploaded a dump of the U-Boot for my CB1 to http://phelum.net/temp/CB1_U-Boot . Please try this. I'll try to generate a replacement from a newer base and advise if it works.
I'm trying to organize my thoughts, such as the are, on the topic of the LCD with Armbian. Attached is my "mind map" on it. Details are extremely light. I'm uploading the PDF and the Mind Map document for editing. Oop, I'm "not permitted to upload this kind of file" 'round here.
I posted the Mind Map .mup file to pastebin: http://pastebin.com/ZnvXMr0K
Hope that helps to illustrate all that I don't know on this topic.
What's missing? I have no idea what the syntax is of the boot_args apart from the ones in my copy of boot.cmd, which modules are required to be loaded, what DT entries need to be created to supply the parameters to the modules or kernel ....
The HDMI is coming up, and I can't see how that's happening from the parameters I know about in the boot.cmd and DTB file for the running kernel.
I tried enabling framebuffer@2 like this:
framebuffer@2 {
compatible = "allwinner,simple-framebuffer", "simple-framebuffer";
allwinner,pipeline = "de_fe0-de_be0-lcd0";
clocks = <0x2 0x1 0x3 0x24 0x3 0x2c 0x3 0x2e 0x4 0x19 0x4 0x1a>;
status = "enabled";
};
This had no effect AFAIK.
Any pointer would be appreciated.
Thanks
Chris
Armbian-LCD-MM-rev0.pdf
Xenial is one of the first options after starting compile.sh. My build host is trusty. I started again and selected trusty this time for the system to build.