I believe it is not allowed to attach dmesg on the forum, I copy the
driver's output:
396 [ 8.005277]
===========================gslx680_ts_init=====================
397 [ 8.036669] _fetch_sysconfig_para.
398 [ 8.039569] gslx680 firmware 420tpc.fw.
399 [ 8.048699] _fetch_sysconfig_para: after: ctp_twi_addr is 0x40,
dirty_addr_buf: 0x40. dirty_addr_buf[1]: 0xfffe
400 [ 8.131368] _fetch_sysconfig_para: ctp_twi_id is 1.
401 [ 8.162988] _fetch_sysconfig_para: screen_max_x = 480.
402 [ 8.185533] _fetch_sysconfig_para: screen_max_y = 272.
403 [ 8.208446] _fetch_sysconfig_para: revert_x_flag = 0.
404 [ 8.232748] _fetch_sysconfig_para: revert_y_flag = 0.
405 [ 8.262853] _fetch_sysconfig_para: exchange_x_y_flag = 0.
406 [ 8.291023] i2c-core: driver [gslx680] using legacy suspend method
407 [ 8.322871] i2c-core: driver [gslx680] using legacy resume method
408 [ 8.353931] ctp_detect: Detected chip gslx680 at adapter 1,
address 0x40
409 [ 8.391662] ====gslx680_ts_probe begin=====.
410 [ 8.393688] ==kzalloc success=
411 [ 8.396476] [GSLX680] Enter gsl_ts_init_ts
412 [ 8.422147] ctp_set_irq_mode: config gpio to int mode.
413 [ 8.451901] ctp_set_irq_mode, 862: gpio_int_info, port = 7,
port_num = 11.
414 [ 8.453855] INTERRUPT CONFIG
415 [ 8.490769] input: gslx680 as
/devices/platform/sunxi-i2c.1/i2c-1/1-0040/input/input1
416 [ 8.618349] =============gsl_load_fw start==============
417 [ 23.431110] =============gsl_load_fw end==============
418 [ 23.738046] ==gslx680_ts_probe over =
On Monday, May 5, 2014 10:25:14 PM UTC-5, hunter hu wrote:
Hi Joe,
Thank you so much for replying and following up the issue, I
really appreciate your help.
Here I attached the dmesg on the driver integration output, my
android gslx680.ko and the firmware extracted from it using your
script.
Regards,
-Hunter
On Mon, May 5, 2014 at 3:30 PM, Joe Burmeister
<[email protected] <javascript:>> wrote:
Hi Hunter,
Sorry didn't get back sooner, only had my phone with me and
writing anything of any length on it is painful.
Can you send me your dmesg output and your gslx680.ko?
Maybe there is something in the dmesg output that will tells
us more. If not, perhaps some extra verbose info can be added
to the driver to give us a clue.
The other thing I want to check the firmware extracted by the
extractor, perhaps it's not all of it.
Joe
On 03/05/14 20:50, hunter hu wrote:
Hi Joe,
I have a gsl1680 chip and it is a 4.3" 480x272 display. I
used the "firmware/fw_extractor" tool extracted the firmware
from the Android binary gslx680.ko for my tablet, but
experiencing the same issue Selim had before.
dmesg shows the driver successfully loaded, chip probed and
firmware also loaded correctly, but evtest shows no output
whatsoever.
Any help or ideas will be appreciated, thanks in advance.
thanks,
-Hunter
On Tuesday, March 18, 2014 5:03:24 AM UTC-5, Joe Burmeister
wrote:
On 18/03/14 09:03, [email protected] wrote:
> 17 Mart 2014 Pazartesi 00:52:27 UTC+2 tarihinde Joe
Burmeister yazdı:
>> On 14/03/14 15:36, [email protected] wrote:
>>
>>> 14 Mart 2014 Cuma 17:33:56 UTC+2 tarihinde
[email protected] yazdı:
>>>> 13 Mart 2014 Perşembe 14:22:52 UTC+2 tarihinde Joe
Burmeister yazdı:
>>>>> On 13/03/14 12:05, [email protected] wrote:
>>>>>> 13 Mart 2014 Perşembe 12:20:15 UTC+2 tarihinde Joe
Burmeister yazdı:
>>>>>>> On 13/03/14 09:52, [email protected] wrote:
>>>>>>>> 27 Ağustos 2013 Salı 22:14:14 UTC+3 tarihinde
[email protected] yazdı:
>>>>>>>>> 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
<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
>>>>>>>>>
>>>>>>>> Hi,
>>>>>>>> I have a A13 tablet (just like this one -->
http://moveontechnology.com/hugoenchina/?p=324
<http://moveontechnology.com/hugoenchina/?p=324>)
>>>>>>>> and while trying to make touchscreen working I
came acrross with this gslx680
driver(https://gitorious.org/gslx680-for-sunxi
<https://gitorious.org/gslx680-for-sunxi>)
>>>>>>>> I'm using sunxi-3.4 kernel and compiled the
driver successfully for this kernel. My screen resolution
is 800x480 so I'm using the firmware supplied by the
source code.
>>>>>>>> I can successfully insmod the driver, got the
successfull dmesg messages as expected, but when I try
testing the driver with "evtest" tool, i got totally no
output from gslx680 mmodule (/dev/event/event1).
>>>>>>>> I am completely stuck at this point, any
suggestion will be really helpfull.
>>>>>>>> Thanks in advance.
>>>>>>>> selim
>>>>>>> Hi Selim,
>>>>>>> I've done an update recently that makes the new
code work properly with
>>>>>>> X, it was broken at one point.
>>>>>>> At this point, as far as I know, I need to start
the process of getting
>>>>>>> it into sunxi properly. Maybe add DT and get it
fully upstreamed. Yet to
>>>>>>> start that process.
>>>>>>> Anyway, no output from evtest tells me the
problem is probably the firmware.
>>>>>>> You need to extract the firmware from your
android driver. There is a
>>>>>>> python script in the firmware directory called
fw_extractor (and
>>>>>>> fw_info) that should be able to do this, if the
driver is related to the
>>>>>>> Android one with my device. If the firmware isn't
in the Android driver,
>>>>>>> then we need to find where it lives on your
device and put it into the
>>>>>>> same binary format.
>>>>>>> If you feel you aren't getting anywhere, send me
the Android driver and
>>>>>>> I'll have a look to see if the firmware is in
there and adapt the script
>>>>>>> to find it there too.
>>>>>>> We need to start building a database of the
firmware for the gslx680
>>>>>>> chips. If we can work out how to tell which chip
needs which firmware,
>>>>>>> we can select the right one automatically. The
aim of course is
>>>>>>> everything just works. :-)
>>>>>>> Joe
>>>>>> Joe Hi,
>>>>>> Thanks for the quick reply,
>>>>>> Indeed I have read in some forum posts that people
trying wrong
>>>>>> gslx680 firmwares got shifted touch outputs, I
haven't seen a post
>>>>>> with no output from the driver.
>>>>>> I hope its about the wrong firmware.
>>>>>> Ok, now I will pull the successfully running
driver (gslX680.ko)
>>>>>> from running android device and extract the
firmware as you suggested.
>>>>>> Thanks again.
>>>>>> selim
>>>>> Hi Selim,
>>>>> No prob, delighted when someone has a play with it.
:-)
>>>>> The result of the wrong firmware is hard to guess.
>>>>> The firmware for this device is just a buck load of
settings from what I
>>>>> can see.
>>>>> Only thing that probably holds is it depends how
far out your device is
>>>>> from the settings in the firmware on how well it
works.
>>>>> Please please let me know how you get on.
>>>>> Joe
>>>> Hi Joe,
>>>> Today I have rooted my tablet, successfully find the
touchscreen module named as "A13_gslX680" and pulled the
ko file with adb pull.
>>>> Good news :)
>>>> After extracting the firmware from the original
module and trying gslx680_ts driver with the original
firmware everything worked like a charm, now I can get
outputs from evtest tool.
>>>> More information about my tablet and firmware is;
>>>> my tablet exactly looks like this one -->
https://drive.google.com/file/d/0B7kdmqnGET4eeHVlY1k2REVlemc/edit?usp=sharing
<https://drive.google.com/file/d/0B7kdmqnGET4eeHVlY1k2REVlemc/edit?usp=sharing>
>>>> Screen size: 9" , 800x480
>>>> Mainboard ID : TW_A0910_16B_V1.1_0830
>>>> Touch screen IC : GSL3680
>>>> Original Module :
https://docs.google.com/file/d/0B7kdmqnGET4eeHVlY1k2REVlemc/edit?pli=1
<https://docs.google.com/file/d/0B7kdmqnGET4eeHVlY1k2REVlemc/edit?pli=1>
>>>> Original Firmaware (extracted):
https://docs.google.com/file/d/0B7kdmqnGET4eNzItc0tYYW5PY3M/edit?pli=1
<https://docs.google.com/file/d/0B7kdmqnGET4eNzItc0tYYW5PY3M/edit?pli=1>
>>>> I hope it is useful for others.
>>>> Thanks for your help.
>>>> selim
>>> sorry wrong link for the tablet !
>>> my tablet exactly looks like this one -->
>>>
http://www.aliexpress.com/item/MV90-9-inchs-Allwinner-A13-Tablet-9-single-core-4GB-512MB-360-deg-gravity-sensor-cheap/1528614982.html
<http://www.aliexpress.com/item/MV90-9-inchs-Allwinner-A13-Tablet-9-single-core-4GB-512MB-360-deg-gravity-sensor-cheap/1528614982.html>
>> Thanks, I've added your firmware to the repo. I also
took apart my
>>
>> tablet to see exactly which gsl?680 mine is. Answer,
gsl1680. So we have
>>
>> gsl1680 and gsl3680. When I get a spare moment, I'll
process this stuff
>>
>> update the wiki page.
>>
>>
>>
>> Joe
>
> Joe,
>
> I'm using the latest sources, but while I dont have an X
> (or any kind of window manager) on my target device,
> I cant help you with X compatibility.
>
> I'm using Qt/QWS with tslib (direct access to fb) on my
target,
> now I'm trying to work it out.
> I will inform you when I succeed.
>
> Regards.
>
> selim
>
Cheers,
Should work, I'm sticking the to protocol as far as I know.
You should be able to use single or multitouch events.
Joe
--
You received this message because you are subscribed to a
topic in the Google Groups "linux-sunxi" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/linux-sunxi/SZGxiTQcFyY/unsubscribe
<https://groups.google.com/d/topic/linux-sunxi/SZGxiTQcFyY/unsubscribe>.
To unsubscribe from this group and all its topics, send an
email to [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to a
topic in the Google Groups "linux-sunxi" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/linux-sunxi/SZGxiTQcFyY/unsubscribe
<https://groups.google.com/d/topic/linux-sunxi/SZGxiTQcFyY/unsubscribe>.
To unsubscribe from this group and all its topics, send an
email to [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to a topic in the
Google Groups "linux-sunxi" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/linux-sunxi/SZGxiTQcFyY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
