A20 is now in mainline which means you can build mainline kernel and it will work on A20-OLinuxino-LIME2.
Remy made blog post how to build Debian Linux with latest Kernel 3.19 from scratch – you can read how he did this here.
olimex
all fun projects at Olimex Ltd
olimex 
Feb 20, 2015 @ 22:24:34
Support for OLinuXino A20 LIME is included in official Debian-packaged Linux kernel targeted the upcoming Debian “wheezy” release (support was added in version 3.16.7-1 of the linux package). So unless you have special needs you should not need to build a custom kernel at all.
Feb 21, 2015 @ 00:55:20
Hmm – I might be wrong, actually: Seems only OLinuXino A20 LIME is covered yet in official Debian kernel targeted next stable release, not the LIME2.
I am sure a bugreport similar to would be much appreciated.
I might try locate and test the needed patch myself – when I actually have such devices to work on (I have just bought one of each tonight).
Feb 25, 2015 @ 11:50:45
Seems the Linux kernel targeted upcoming stable release of Debian will tonight gain support for LIME2: https://lists.debian.org/debian-kernel/2015/02/msg00267.html
Feb 25, 2015 @ 23:04:12
yay 🙂
Mar 01, 2015 @ 22:10:55
Took longer than first expected, but http://bugs.debian.org/777455 is now closed and LIME2 support should emerge in Debian unstable in 3-4 hours from now – and if all goes well then in Debian testing as well 5-10 days from now.
Feb 21, 2015 @ 00:56:54
Link got swallowed above – here it is: https://bugs.debian.org/764967
Feb 21, 2015 @ 16:23:49
No sound, no video? No point! At least for most use cases…
Or did i misunderstand anything?
Is there some plan when all will work without blobs? That would be a great thing.
Unfortunately linux-sunxi created more questions than answers.
Maybe one of the cracks could explain it for average mortals 😉
Feb 22, 2015 @ 10:55:20
Looks nice, but this blog post gets two things wrong:
1. “By default it comes with an 3.4 kernel with binary blobs and patches from Allwinner. Recently the mainline kernel has gained support for these boards, you can now run and use the mainline kernel without these awfull non-free binary blobs”.
In fact, there are no blobs in the 3.4 kernel. Mentioning “awfull non-free binary blobs” might be good for a better dramatic effect, but has nothing to do with reality. We don’t like the old 3.4 kernel because if offers relatively poor reliability and code quality, but not because of some mythical blobs.
2. “For example, if you need graphical output (hdmi) or sound it will not work with the 3.19 kernel”.
In fact, there *is* graphics support in the 3.19 kernel (both hdmi and lcd), implemented via simplefb. You just need to use the mainline u-boot for this instead of some random fork.
Feb 27, 2015 @ 12:14:03
Also, please don’t take out the compiler version check unless you’re really sure you know what you’re doing.
The particular bug being addressed by that check – https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854 – produces kernels that appear to work, but that randomly crash and/or silently corrupt your filesystem. Sometimes it takes days to see any problem.
Do yourself a favour and use a 4.7.x or 4.9.x version of GCC, especially when cross compiling with a linaro compiler as they have managed to ship versions that should be good but still include the bug. See
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/295174.html