PINE64 Don't be evil devkit (pine64-dontbeevil)
USB Networking |
Unavailable |
---|---|
Flashing |
Unavailable |
Touchscreen |
Broken |
Display |
Works |
WiFi |
Broken |
Xwayland |
Works |
FDE | |
Mainline |
Works |
Battery |
Broken |
3D Acceleration |
Broken |
Accelerometer |
Works |
Audio |
Broken |
Bluetooth |
Broken |
Camera |
Broken |
GPS |
Broken |
Mobile data |
Broken |
SMS |
Broken |
Calls |
Broken |
USB OTG |
Broken |
Contributors
Serial console
There is a 3.3V uart on the 2x5pin connector near the modem. The pin in the corner toward VOL- is GND and the next pin is TX.
The baudrate in u-boot and in Linux is 115200n8
Components
Component | Model | Mainline |
---|---|---|
Touchscreen | FocalTech FT6336GU | edt_ft5x06 |
Rear camera | OmniVision OV5640 | Yes, ov5640 |
Front camera | GalaxyCore GC2035 | Nope |
LCD | JD9365D | pine64/linux |
Wifi/Bluetooth | RTL8723BS | CONFIG_RTL8723BS |
Modem | Quectel EC25-E | USB_NET_QMI_WWAN |
Magnetometer | ST LIS3MDL | yes |
Ambient light / Proximity | SensorTek STK3335 | works with stk3310 |
Sixaxis | InvenSense MPU-6050 | yes |
Touchscreen
The touchscreen is controlled by the edt_ft5x06
module on i2c-0. The current issue is that it takes a long while before the i2c-0 bus works after booting. For some reason it takes ~110 seconds before communication is possible. This causes an issue because the module tries to probe the touchscreen before the bus works.
The current workaround is to build edt_ft5x06
as a module and rmmod/modprobe the module after the i2c-0 bus works so it gets probed again.
It also seems that the touchscreen is flipped vertically so that probably needs some calibration data in the dts.
See also
- pmaports!308 Initial merge request