Author Topic: Touchscreen updated list for Cubieboard 2  (Read 1009 times)

Offline Yann-Kaelig

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Touchscreen updated list for Cubieboard 2
« on: November 07, 2016, 12:28:27 pm »
Hi,

This thread with your help aims to list all touchscreen running on cubieboard-2 (A20) with the mainline kernel. I spent a lot of time on the web to find appropriate information that could help me, but most of them are outdated running on obsolete files and kernel.
So it seems appropriate to compile  the current state of these hardware running on cubieboard 2 with mainline kernel. Apparently there are several method to connect and use touchscreen on cubieboard 2. I made three categories.

1) Touchscreen connected through a baseboard.
2) Touchscreen connected on converter.
3) Touchscreen self-running with hdmi/usb.

Let's developing each case.

1) In this first case we need a baseboard.

Currently on the market they are two available baseboard for cubieboard 2:
--- Cubie Baseboard developed by iotllc available on the official website. LINK
--- DVK522 Baseboard developed by waveshare available on the official website. LINK

A cubieboard is connected on the baseboard, the baseboard ready to host your touchscreen with different type of connectors  depending on the baseboard model.

2) In this second case we need a converter.

The touchscreen is connected on the converter through plate connector. The converter has different type of video input HDMI/VGA and more. Connect the video output from the cubieboard 2 to the input of the card converter.

3) In this third case the touchscreen work as standalone

The touchscreen doesn't need extra converter or baseboard, has HDMI/VGA or others input connectors and can be directly plugged on the cubieboard 2 video output.

Normally from this point you should be in this situation, which method to choose and why.
The answer in my opinion is very simple :
1) First priority given on touchscreen hardware running on the mainline kernel without closed source firmware
2) Second for touchscreen hardware running on the mainline kernel with not too much crappy closed source firmware.

Obviously there could be other factors to take care about, and one of them certainly the method to power the touchscreen.

From there, we will build the method to present the touchscreen. All your suggestions are welcome to expand the criteria.
Observe the shape and be clear in order to help the beginners and also improve our debate and comparison over the thread.

So, here is a first beta criteria list

Product commercial reference :
Product hardware reference :
Manufacturer :
Datasheet :
Url:

This touchscreen can be used with Cubie baseboard : YES / NO
This touchscreen can be used with DVK522 baseboard : YES / NO
This touchscreen can be used with converter : YES / NO 
--- Converter type : $commercial reference  / hardware reference
--- Converter manufacturer :
--- Converter datasheet :
--- Converter Url :
This touchscreen is standalone : YES / NO

Additional information about how the touchscreen is supplied :

This touchscreen work with mainline kernel : $kernel_version
This touchscreen work with mainline kernel driver : $kernel_driver name
This touchscreen need a kernel driver not in mainline kernel : $Url
This touchscreen need a closed source firmware : YES / NO
--- Closed source firmware Url :

This touchscreen has been tested on Gnu-Linux OS : $OS_name
--- Screenshot : $Url
--- Video : $Url

This touchscreen can run out of the box : YES / NO
This touchscreen need a hack : NO / YES $Full_information about the hack.

Any other important observation : $Full_information





« Last Edit: November 07, 2016, 12:53:23 pm by YKaelig »