Hi,

I've never tried the Android build. I left it in pretty much as from the original yuandao-n90-window-dual-core-2 I ported from. But I don't see how this dependency came in if you are building the source I worked on.

Unless I'm miss understanding, it looks like you are taking kernel modules from one kernel and inserting them into another kernel. That is not good. The Linux kernel doesn't have a stable ABI, so you can't safely swap modules between kernels.

You will need to build the gslx680 driver from https://gitorious.org/gslx680-for-sunxi, pointing it at the build of the your sunxi kernel. It's currently out of tree you see. So you will need to build the sunxi kernel, then build the gslx680 kernel module. You will also need to extract the firmware from your Android gslx680.ko to feed your build of the gslx680.ko as a separate file. All the gslx680 stuff is explained in the repo's readme, and the how to build sunxi is explained at: http://linux-sunxi.org/Linux_Kernel

On my list of assorted things to do in life, "get gslx680 merged" is listed. ;-)

As I've never tried the Android build, it might not "just work", in which case, as we know the normal Linux build one works, just comment out the Android stuff. It will use more power, but it will work at least.

Joe


On 30/05/14 00:34, [email protected] wrote:
Greetings,

I've just been reading this message board regarding the 420TPC.
The board is INET A13_66V but cannot find sources for that board so have been
using a sun5i configuration.
What I have working so far is the latest sunxi 3.4.90 kernel, 8188eu wifi 
driver and both a linaro and debian prebuilt image from the olimex site.
The only driver that seems to be of most difficulty is the gslx680 touchscreen.
Upon inspecting this in android, it depends upon an inet_ctp module which I 
have attempted to force modprobe but with kernel taints and crashes so this is 
no longer an option.
The firmware is loaded properly because Android can also load it and the 
touchscreen remains working so the FW dump form the gslx680.ko works.

It is simply the inet_ctp.ko driver I have no idea about.
It seems like an ioctl interface because a whole bunch of random touchscreen 
modules are loaded into it and one will eventually be the proper driver.
I cannot find sources for this driver, it seems proprietary.

Not sure what to do at this point. On a previous tablet, the same issue with an 
ioctl driver that needed to be loaded before wifi, touchscreen, keypad and 
would only work force modprobing if lucky.

Any ideas on where or how to figure what is inside this inet_ctp.ko driver?
Here is a modinfo of it:

filename:       /home/eynstyne/Desktop/modules/inet_ctp.ko
license:        Dual BSD/GPL
description:    INET CTP CONTROL
author:         <[email protected]>
srcversion:     4BF8B04CF61036647FA46D2
depends:
vermagic:       3.0.8+ preempt mod_unload modversions ARMv7

and here is a modprobe --dump-modversions:

0xa87cd4f1      module_layout
0x2e5810c6      __aeabi_unwind_cpp_pr1
0xeae3dfd6      __const_udelay
0x27e1a049      printk
0xefd6cf06      __aeabi_unwind_cpp_pr0

Any ideas on how to get this touchscreen working?


On Tuesday, 27 August 2013 15:14:14 UTC-4, [email protected]  wrote:
Hi,

For a while I've been working on getting my A13 tablet touch screen working 
with GNU/Linux.

It's now working well enough for my purposes and I figured it was time to push 
it out.
The code can be found at:
https://gitorious.org/gslx680-for-sunxi

It would be easy to move it in tree. What is a bit different from the other 
touch screen drivers is that it doesn't include the firmware in the driver.
I've split the firmware into a separate file that you name in the 
fex/script.bin file.
The reason for this is that the firmware defines things about the hardware such 
as resolution and can't be easily modified. So to support multiple devices 
you'd need multiple firmware included. Or your have to build for each 
driver+firmware combination. Better to have it a seperate file and which 
firmware be a configuration thing. That fits better to me with fex/script.bin 
or Device Tree. I've also added legacy single touch as well as multi touch.

Not sure where we go from here, but no point me sitting on it. ;-)

Joe


--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to