Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
Actually, I don't want to redevelop anything. I found some bits of code here and there and wanted to make it work. I'll definitely try your lib. However, I haven't found out what is the GPIO used on my tablet (the chuwi vi8) and it looks like this guy found it. So I am asking for the information he found :) (without waiting for an hypothetical release in the future). Jonathan Le mer. 5 août 2015 à 14:26, Gregor Riepl onit...@gmail.com a écrit : Actually good news - I have ported it! Touch is working Not ideal at the moment but working! so who is interested - wait alittle for anounce. Do you have any code or anything to get me started ? What is the IOCNTL pin number ? I would really love to get this working too. What on earth is going on - suddenly everyone develops their own Silead touchscreen driver? Maybe we should consolidate activity a bit to reduce the amount of duplicated work. I rewrote most of Joe Burmeister's driver into one that would work with ACPI based systems. You can find the current version here: https://github.com/onitake/gslx680-acpi It has some problems currently and will only work with systems that have the powerup/powerdown sequence encoded in the ACPI DSDT at the moment. I'm still working on GPIO support. I also found out that some Silead controllers don't support finger tracking, so my driver uses the in-kernel finger tracker instead. Also, and probably most importantly, an Intel engineer posted a completely rewritten driver to the linux-input mailing list. It is not ready for kernel inclusion yet, and will not work with existing devices as-is. They decided to rely on information in the DSDT for panel configuration, but vendors have not included such information yet. To get this driver working on currently available devices, you'll have to override the DSDT or use the new OSDT functionality that will be added to Linux 4.2 (see http://comments.gmane.org/gmane.linux.acpi.devel/77637) -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
Actually, I don't want to redevelop anything. I found some bits of code here and there and wanted to make it work. I'll definitely try your lib. However, I haven't found out what is the GPIO used on my tablet (the chuwi vi8) and it looks like this guy found it. So I am asking for the information he found :) (without waiting for an hypothetical release in the future). Just consult your DSDT. It should have all the information you need to get the touchscreen controller working. The exact GPIO pin location might be different for every device, so it's a good idea to check for yourself in any case. If you prefer to use the userspace Silead driver by ???, you may need to do a bit of math to get the correct pin number. Kernel drivers can rely on the kernel to do the work. Consult https://github.com/onitake/gslx680-acpi/blob/master/acpi/gsl-dsdt.aml for the part you need to look for. To obtain your (decompiled) DSDT, use: cp /sys/firmware/acpi/tables/DSDT . iasl -d DSDT -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
If you prefer to use the userspace Silead driver by ???, you may need to do a The ??? was meant to say Rastersoft: https://github.com/rastersoft/gsl1680 Actually, I don't want to redevelop anything. Sorry, I totally misunderstood. :D I do hope that the effort can be consolidated a bit. A universal kernel driver would be marvellous. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
sergk.admin@... writes: Actually good news - I have ported it! Touch is working Not ideal at the moment but working! so who is interested - wait alittle for anounce. Hi, Do you have any code or anything to get me started ? What is the IOCNTL pin number ? I would really love to get this working too. Thanks, Jonathan -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
Can you share the operating steps. Thanks. On Tuesday, May 19, 2015 at 7:02:10 PM UTC+8, sergk...@gmail.com wrote: The problem is that there is usually NOAndroid kernel for device, for example Chuwi vi8 super with its plarform (vendor) drivers and platform initial settings. Actually I have found of the way how to detect corresponding gpio pin but it is manual (scripted + manual) guessing (enumerating). Moreover from kenel to kernel this is different gpio pin number. I still could not fix it how to immediately find out which exactly pin inside Z3735F architecture is used and how to find out it's number in any linux kernelю Currently - I just enumerating all on concrete linux kernel and for each kernel finding out its number - :( this is ridiculous but its works! Regards, Serge. On Tuesday, May 19, 2015 at 10:58:21 AM UTC+3, Henrik Nordström wrote:fre 2015-05-15 klockan 18:40 -0400 skrev jons...@gmail.com: Another way - hook up JTAG. Use boundary scan to toggle the pins. That will tell you the pin number. Look up the pin number and figure out the GPIO. Or look at the source of the Android kernel running on the device for any hints. Regards Henrik -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
As I wrote scripted+ manual and it is this is ridiculous but its works! So all information for you is inside this thread - there is no any magic script that do all instead yourself. All that you should to try - just one by one try each gpio pin. I have used ordinary cmd lines in linux shell for this. thats why it is manual. Regarding firmware I do not know what touch controller is inside Prestigio PMP880TD but usually firmware is located separately inside driver file sets, or has the name of the manufacturer of the touch or is built in inside drivers - there is here my manual how to extract it for elf binaries. The same story but with different tools for Win. On Thursday, May 28, 2015 at 6:10:56 PM UTC+3, Александр Голеншин wrote: On Saturday, May 16, 2015 at 2:08:55 AM UTC+3, sergk...@gmail.com wrote: Actually good news - I have ported it! Touch is working Not ideal at the moment but working! ;-) so who is interested - wait alittle for anounce. Can you please share a script you used to determine the IO CONTROL pin? I'm trying to port Ubuntu to a Prestigio PMP880TD which is a win81 only tablet. And I really need touch working. And by the way, where did you get digitizer firmware? -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
On Saturday, May 16, 2015 at 2:08:55 AM UTC+3, sergk...@gmail.com wrote: Actually good news - I have ported it! Touch is working Not ideal at the moment but working! ;-) so who is interested - wait alittle for anounce. Can you please share a script you used to determine the IO CONTROL pin? I'm trying to port Ubuntu to a Prestigio PMP880TD which is a win81 only tablet. And I really need touch working. And by the way, where did you get digitizer firmware? -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
The problem is that there is usually NOAndroid kernel for device, for example Chuwi vi8 super with its plarform (vendor) drivers and platform initial settings. Actually I have found of the way how to detect corresponding gpio pin but it is manual (scripted + manual) guessing (enumerating). Moreover from kenel to kernel this is different gpio pin number. I still could not fix it how to immediately find out which exactly pin inside Z3735F architecture is used and how to find out it's number in any linux kernelю Currently - I just enumerating all on concrete linux kernel and for each kernel finding out its number - :( this is ridiculous but its works! Regards, Serge. On Tuesday, May 19, 2015 at 10:58:21 AM UTC+3, Henrik Nordström wrote: fre 2015-05-15 klockan 18:40 -0400 skrev jons...@gmail.com javascript:: Another way - hook up JTAG. Use boundary scan to toggle the pins. That will tell you the pin number. Look up the pin number and figure out the GPIO. Or look at the source of the Android kernel running on the device for any hints. Regards Henrik -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
Thanks but this is described on the mentioned by me wiki page: http://linux-sunxi.org/GSL1680 THE PROBLEM IS - I am unnable to find out which gpio pin is responsible for manage IOCNTL line of GSL1680 controller. Without enabling this pin to 1 controller of the MSSL1680 will not raise communication via I2C and firmware will be NOT loaded, so datashet is useless untill will be not found the way to do this (again from the same mentioned above wiki page): GPIO The chip has four main pins to communicate with a CPU: - SDA and SCL: these two pins conform an I2C bus http://en.wikipedia.org/wiki/I%C2%B2C, allowing to exchange data between the chip and the main CPU. - IOCNTL: this pin, when active (logic 1) enables the chip, making it to answer to I2C commands and read the touch screen. When inactive (logic 0), the chip is in Low Power state. - INT: when there is data available (a press) or in other cases (not sure, not have enough documentation), this pin gets active to signal this to the CPU. Chip initialization The driver shows a quite obscure initialization procedure: - Enable the chip (*set IOCTNL to 1*) Kind regards, Serge. On Friday, May 15, 2015 at 6:37:28 PM UTC, Jon Smirl wrote: Here's the datasheet http://www.buydisplay.com/download/ic/GSL1680.pdf On Fri, May 15, 2015 at 2:32 PM, sergk...@gmail.com javascript: wrote: In addition some details from Android Under Android : Linux 3.10.20-263387 i686 I have the following: cat /sys/class/i2c-adapter/i2c-4/ 4-0040/name MSSL1680:00. or the same under other path: cat /sys/bus/i2c/devices/i2c-4/4- 0040/name MSSL1680:00. Also in Windows drivers there is fw Silead. Only base on this I am sure that I have 1680 chip! Also it is resides on 0x40! on i2c channel. Lsmod under undroid shows gslx68x_ts driver that is relative to mentioned above i2c channel. Under any of the Linux kernel - I prefer x86_64 there is the same MSSL1680:00 but on the i2c-3 channel. I2cdetect detects nothing at the same moment. My guessing that probable mentioned here http://linux-sunxi.org/GSL1680 IOCNTL pin is not set to logical 1 and this is a main my problem - I do not know how to detect to which gpio pin on z3735f is connected IOCNTL thats mean that for your driver I could not provide -gpio parameter! To make MSSL1680 communicate via I2c channel I need 1st to set IOCNTL to 1, and do not know how to do this and I do not have /sys/devices/virtual/misc/sun4i-gpio/pin/pb3. At the same moment - It looks strange but under classical linux kernels I have only 3 items inside /sys/class/gpio numbers of them also differ from kernel to kernel. ubuntu 14.10 (3.16.0-29). shows ghpiochip 126, gpiochip154,gpiochip82 - have tried all of them - your driver wrotes (by memory) - that unable to open such device. under Arch 4.0.1 kernel - set of gpios are 338,382,410. actually the same story. Numbers are different but all binded to the same - INT33F:0x. At the same moment cat /sys/kernel/debug/gpio shows about 145 values in the table. Kind regards, Serge Kolotylo On Friday, May 15, 2015 at 2:04:48 PM UTC, sergk...@gmail.com wrote: Dear All, please assist me in porting GSL1680 touchscreen driver to Linux x86/86_64 kernel. As a testing device I have tablet =Chuwi vi8 super. Specs of it http://techtablets.com/chuwi-vi8/ (baytrail based intel z3735f). I have successfully run on it Linux x86 and x86_64 (Arch linux, Ubuntu, Linux mint, sysrescue cd linux distros), the main last problem is - there is NO touch screen driver for Silead GSL1680 which is used in this tablet. I have successfully porting to x86_64 userspace driver https://github.com/rastersoft/gsl1680. BUT the problem is according http://linux-sunxi.org/GSL1680 to communicate with chip controller of this touchscreen you should 1st initialize it via setting IOCNTL line to 1, this line is mapped to GPIO pin. The main problem - how to determine without any documentation, having only device with Android 4.4 and Windows 8.1 with working touch screen which gpio pin serve IOCNTL. Please help to find out gpio pin for IOCNTL touch screen on Chuwi vi8 (baytrail) platform or with porting kernel level drive to Linux vanilla kernel for x86 plaforms. PS: I tend to run user space mentioned above driver because porting from sunxi linux driver into vanilla for x86 platforms is not so easy way due a lot of differences of included platform headers files. Regards, Serge Kolotylo. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com
Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
Turn on user space GPIO support and use sysfs to toggle the pins. Put on a scope on the chip. Start guessing. There are only about 50 GPIOs so this shouldn't take long. On Fri, May 15, 2015 at 6:27 PM, sergk.ad...@gmail.com wrote: Thanks but this is described on the mentioned by me wiki page: http://linux-sunxi.org/GSL1680 THE PROBLEM IS - I am unnable to find out which gpio pin is responsible for manage IOCNTL line of GSL1680 controller. Without enabling this pin to 1 controller of the MSSL1680 will not raise communication via I2C and firmware will be NOT loaded, so datashet is useless untill will be not found the way to do this (again from the same mentioned above wiki page): GPIO The chip has four main pins to communicate with a CPU: SDA and SCL: these two pins conform an I2C bus, allowing to exchange data between the chip and the main CPU. IOCNTL: this pin, when active (logic 1) enables the chip, making it to answer to I2C commands and read the touch screen. When inactive (logic 0), the chip is in Low Power state. INT: when there is data available (a press) or in other cases (not sure, not have enough documentation), this pin gets active to signal this to the CPU. Chip initialization The driver shows a quite obscure initialization procedure: Enable the chip (set IOCTNL to 1) Kind regards, Serge. On Friday, May 15, 2015 at 6:37:28 PM UTC, Jon Smirl wrote: Here's the datasheet http://www.buydisplay.com/download/ic/GSL1680.pdf On Fri, May 15, 2015 at 2:32 PM, sergk...@gmail.com wrote: In addition some details from Android Under Android : Linux 3.10.20-263387 i686 I have the following: cat /sys/class/i2c-adapter/i2c-4/ 4-0040/name MSSL1680:00. or the same under other path: cat /sys/bus/i2c/devices/i2c-4/4- 0040/name MSSL1680:00. Also in Windows drivers there is fw Silead. Only base on this I am sure that I have 1680 chip! Also it is resides on 0x40! on i2c channel. Lsmod under undroid shows gslx68x_ts driver that is relative to mentioned above i2c channel. Under any of the Linux kernel - I prefer x86_64 there is the same MSSL1680:00 but on the i2c-3 channel. I2cdetect detects nothing at the same moment. My guessing that probable mentioned here http://linux-sunxi.org/GSL1680 IOCNTL pin is not set to logical 1 and this is a main my problem - I do not know how to detect to which gpio pin on z3735f is connected IOCNTL thats mean that for your driver I could not provide -gpio parameter! To make MSSL1680 communicate via I2c channel I need 1st to set IOCNTL to 1, and do not know how to do this and I do not have /sys/devices/virtual/misc/sun4i-gpio/pin/pb3. At the same moment - It looks strange but under classical linux kernels I have only 3 items inside /sys/class/gpio numbers of them also differ from kernel to kernel. ubuntu 14.10 (3.16.0-29). shows ghpiochip 126, gpiochip154,gpiochip82 - have tried all of them - your driver wrotes (by memory) - that unable to open such device. under Arch 4.0.1 kernel - set of gpios are 338,382,410. actually the same story. Numbers are different but all binded to the same - INT33F:0x. At the same moment cat /sys/kernel/debug/gpio shows about 145 values in the table. Kind regards, Serge Kolotylo On Friday, May 15, 2015 at 2:04:48 PM UTC, sergk...@gmail.com wrote: Dear All, please assist me in porting GSL1680 touchscreen driver to Linux x86/86_64 kernel. As a testing device I have tablet =Chuwi vi8 super. Specs of it http://techtablets.com/chuwi-vi8/ (baytrail based intel z3735f). I have successfully run on it Linux x86 and x86_64 (Arch linux, Ubuntu, Linux mint, sysrescue cd linux distros), the main last problem is - there is NO touch screen driver for Silead GSL1680 which is used in this tablet. I have successfully porting to x86_64 userspace driver https://github.com/rastersoft/gsl1680. BUT the problem is according http://linux-sunxi.org/GSL1680 to communicate with chip controller of this touchscreen you should 1st initialize it via setting IOCNTL line to 1, this line is mapped to GPIO pin. The main problem - how to determine without any documentation, having only device with Android 4.4 and Windows 8.1 with working touch screen which gpio pin serve IOCNTL. Please help to find out gpio pin for IOCNTL touch screen on Chuwi vi8 (baytrail) platform or with porting kernel level drive to Linux vanilla kernel for x86 plaforms. PS: I tend to run user space mentioned above driver because porting from sunxi linux driver into vanilla for x86 platforms is not so easy way due a lot of differences of included platform headers files. Regards, Serge Kolotylo. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send
[linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
In addition some details from Android Under Android : Linux 3.10.20-263387 i686 I have the following: cat /sys/class/i2c-adapter/i2c-4/ 4-0040/name MSSL1680:00. or the same under other path: cat /sys/bus/i2c/devices/i2c-4/4- 0040/name MSSL1680:00. Also in Windows drivers there is fw Silead. Only base on this I am sure that I have 1680 chip! Also it is resides on 0x40! on i2c channel. Lsmod under undroid shows gslx68x_ts driver that is relative to mentioned above i2c channel. Under any of the Linux kernel - I prefer x86_64 there is the same MSSL1680:00 but on the i2c-3 channel. I2cdetect detects nothing at the same moment. My guessing that probable mentioned here http://linux-sunxi.org/GSL1680 IOCNTL pin is not set to logical 1 and this is a main my problem - I do not know how to detect to which gpio pin on z3735f is connected IOCNTL thats mean that for your driver I could not provide -gpio parameter! To make MSSL1680 communicate via I2c channel I need 1st to set IOCNTL to 1, and do not know how to do this and I do not have */sys/devices/virtual/misc/sun4i-gpio/pin/pb3.* *At the same moment - It looks strange but under classical linux kernels I have only 3 items inside /sys/class/gpio numbers of them also differ from kernel to kernel.* ubuntu 14.10 (3.16.0-29). shows ghpiochip 126, gpiochip154,gpiochip82 - have tried all of them - your driver wrotes (by memory) - that unable to open such device. under Arch 4.0.1 kernel - set of gpios are 338,382,410. actually the same story. Numbers are different but all binded to the same - INT33F:0x. *At the same moment cat */sys/kernel/debug/gpio shows about 145 values in the table. Kind regards, Serge Kolotylo On Friday, May 15, 2015 at 2:04:48 PM UTC, sergk...@gmail.com wrote: Dear All, please assist me in porting GSL1680 touchscreen driver to Linux x86/86_64 kernel. As a testing device I have tablet =Chuwi vi8 super. Specs of it http://techtablets.com/chuwi-vi8/ (baytrail based intel z3735f). I have successfully run on it Linux x86 and x86_64 (Arch linux, Ubuntu, Linux mint, sysrescue cd linux distros), the main last problem is - there is NO touch screen driver for Silead GSL1680 which is used in this tablet. I have successfully porting to x86_64 userspace driver https://github.com/rastersoft/gsl1680. BUT the problem is according http://linux-sunxi.org/GSL1680 to communicate with chip controller of this touchscreen you should 1st initialize it via setting IOCNTL line to 1, this line is mapped to GPIO pin. The main problem - how to determine without any documentation, having only device with Android 4.4 and Windows 8.1 with working touch screen which gpio pin serve IOCNTL. Please help to find out gpio pin for IOCNTL touch screen on Chuwi vi8 (baytrail) platform or with porting kernel level drive to Linux vanilla kernel for x86 plaforms. PS: I tend to run user space mentioned above driver because porting from sunxi linux driver into vanilla for x86 platforms is not so easy way due a lot of differences of included platform headers files. Regards, Serge Kolotylo. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Request for detaild for GSL1680 driver for porting to Linux x86_64 kernel on baytrail 3735f platform
Here's the datasheet http://www.buydisplay.com/download/ic/GSL1680.pdf On Fri, May 15, 2015 at 2:32 PM, sergk.ad...@gmail.com wrote: In addition some details from Android Under Android : Linux 3.10.20-263387 i686 I have the following: cat /sys/class/i2c-adapter/i2c-4/ 4-0040/name MSSL1680:00. or the same under other path: cat /sys/bus/i2c/devices/i2c-4/4- 0040/name MSSL1680:00. Also in Windows drivers there is fw Silead. Only base on this I am sure that I have 1680 chip! Also it is resides on 0x40! on i2c channel. Lsmod under undroid shows gslx68x_ts driver that is relative to mentioned above i2c channel. Under any of the Linux kernel - I prefer x86_64 there is the same MSSL1680:00 but on the i2c-3 channel. I2cdetect detects nothing at the same moment. My guessing that probable mentioned here http://linux-sunxi.org/GSL1680 IOCNTL pin is not set to logical 1 and this is a main my problem - I do not know how to detect to which gpio pin on z3735f is connected IOCNTL thats mean that for your driver I could not provide -gpio parameter! To make MSSL1680 communicate via I2c channel I need 1st to set IOCNTL to 1, and do not know how to do this and I do not have /sys/devices/virtual/misc/sun4i-gpio/pin/pb3. At the same moment - It looks strange but under classical linux kernels I have only 3 items inside /sys/class/gpio numbers of them also differ from kernel to kernel. ubuntu 14.10 (3.16.0-29). shows ghpiochip 126, gpiochip154,gpiochip82 - have tried all of them - your driver wrotes (by memory) - that unable to open such device. under Arch 4.0.1 kernel - set of gpios are 338,382,410. actually the same story. Numbers are different but all binded to the same - INT33F:0x. At the same moment cat /sys/kernel/debug/gpio shows about 145 values in the table. Kind regards, Serge Kolotylo On Friday, May 15, 2015 at 2:04:48 PM UTC, sergk...@gmail.com wrote: Dear All, please assist me in porting GSL1680 touchscreen driver to Linux x86/86_64 kernel. As a testing device I have tablet =Chuwi vi8 super. Specs of it http://techtablets.com/chuwi-vi8/ (baytrail based intel z3735f). I have successfully run on it Linux x86 and x86_64 (Arch linux, Ubuntu, Linux mint, sysrescue cd linux distros), the main last problem is - there is NO touch screen driver for Silead GSL1680 which is used in this tablet. I have successfully porting to x86_64 userspace driver https://github.com/rastersoft/gsl1680. BUT the problem is according http://linux-sunxi.org/GSL1680 to communicate with chip controller of this touchscreen you should 1st initialize it via setting IOCNTL line to 1, this line is mapped to GPIO pin. The main problem - how to determine without any documentation, having only device with Android 4.4 and Windows 8.1 with working touch screen which gpio pin serve IOCNTL. Please help to find out gpio pin for IOCNTL touch screen on Chuwi vi8 (baytrail) platform or with porting kernel level drive to Linux vanilla kernel for x86 plaforms. PS: I tend to run user space mentioned above driver because porting from sunxi linux driver into vanilla for x86 platforms is not so easy way due a lot of differences of included platform headers files. Regards, Serge Kolotylo. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
