awindebe and awintcon [Was: Re: A20-Olinuxino-Lime2 + "internal" LCD question]

[Adrien Auzanneau <ada%netbsdfr.org@localhost>]

Hi Jared,
I am coming back on this topic as I am stuck and I can't get my head 
around the right next step to make progress.
I've seen recent support added for:
awindebe(4)
Add support for Allwinner A20/A31 Display engine backend (DE-BE). 
[jmcneill 20141110]
awintcon(4)
Add support for Allwinner A20/A31 TV/LCD controller. [jmcneill 20141110]

Which is OK from the dmesg output:
awindebe0 at awinio0 port 0: Display Engine Backend (BE0)
awintcon0 at awinio0 port 0: LCD/TV timing controller (TCON0)
awinhdmi0 at awinio0: HDMI 1.3
awinhdmi0: display connected
awinhdmi0: DVI mode (auto-detected)
genfb0 at awindebe0: switching to framebuffer console
genfb0: framebuffer at 0xca000000, size 1680x1050, depth 32, stride 6720
wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation)
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 1-3 added (default, vt100 emulation)


So it feels like it's recognized. I am using a bin generated from a .fex 
setup for this specific 7" screen (from the script provided by olimex 
for debian)
fex is here: 
http://packages.netbsdfr.org/HEAD/current/evbarm/olimex/a20-olinuxino-lime2/fex/a20olinuxinolime2-lcd7.fex

For some reason I keep thinking it's the uEnv who's not passing the 
right output...but I can't find the right way to set this up.
Olimex aren't the only one to have these LCD screens, Odroid has one as 
well for his C1. Is there a draft doc on how to get these to work?

Any help appreciated.
Thanks,
-- ada