angler: support Wi-Fi and graphics

Created by: zhuowei

With these patches, the Nexus 6P supports Wi-Fi and almost actually supports Weston.

Issues/questions:

• Graphics still don't work properly: I had to run while [ ! ]; do cat /sys/class/graphics/fb0/modes > /sys/class/graphics/fb0/mode; done. Not sure how the Nexus 5 fixed this; I guess I can add a patch in Weston to automatically run this (or the equivalent ioctl) every frame. (With that command running, graphics work well.) msm-fb-refresher fixes this
• (Note that the Android recovery does send this ioctl every frame for double buffering)
• KGSL is disabled in the kernel, so freedreno won't work, and everything's software rendered. KGSL is not disabled in the kernel anymore, although I haven't enabled the KGSL_DRM compat layer in the kernel yet, nor have I packaged the a440 blobs, so freedreno still won't run. That's for later.
• Should a kernel have NFS enabled? I had it enabled for testing. - based on review, yes.
• Wi-Fi uses the blobs from linux-firmware, which are old; I can package the AOSP blobs (used on this device's stock firmware) that are more up to date if you want. (see the discussion on #513 (closed)) newer blobs packaged.
• The Wi-Fi calibration file is different for various revisions of this hardware; I've added the one that was for my device, but it may not work for earlier/later revisions. Android chooses the correct calibration file at boot in the init.angler.rc.

Tested over an NFS mounted root, but it should work on regular devices.

aports/device/device-huawei-angler/90-android-touch-dev.rules

 # udev rules file
 # All device names can be read from weston's logfile (/tmp/weston.log in postmarketOS)
+# Use default calibration for now.
+SUBSYSTEM=="input", ATTRS{name}=="synaptics_dsx", \
+ENV{ID_INPUT}="1", ENV{ID_INPUT_TOUCHSCREEN}="1" \
+ENV{ID_INPUT_TOUCHPAD}="" ENV{ID_INPUT_KEY}="" \
+ENV{LIBINPUT_CALIBRATION_MATRIX}="1 0 0 0 1 0"

[Administrator]

@zhuowei is the LIBINPUT_CALIBRATION_MATRIX necessary? seems the default value, probably works without it

By Daniele Debernardi on 2017-09-27T09:13:51

[Administrator]

Created by: zhuowei

it's to explicitly indicate that we are using default config; it's not actually needed.

By * postmarketOS Bot on 2017-09-27T12:55:26

[Administrator]

Created by: ollieparanoid

This is fine for me. we could discuss in #182 whether we prefer the explicit notation or leaving it out and then apply it to all devices at once.

By * postmarketOS Bot on 2017-09-27T17:32:47