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

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)
and while trying to make touchscreen working I came acrross with this gslx680 
driver(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

--
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