Hi,
Sorry for brief answer - built in did not work for me.
As minimum in case of Chuwi Vi10 icn8528 you should load firmware with all
related to this stuff + irq mode is still under development, under standard
things irg/gpio was not getted automatically and there is no enough info at
the
Hi all,
;-) At least I am releasing my icn85xx (tested on icn8528 on Chuvi Vi10,
Baytrail) kernel space driver.
It is unfortunately polling mode, but at the moment I am happy with it and
have no enough time to dig in with irq mode.
https://gitlab.com/SergK/icn85xx/tree/master
My special thanks
Hi, Gregor.
Just wrote some my test module-stub, mix of acpi and just direct i2cdev
creation on i2c-4 0x48, anyway it is even possible just used echo icn8528
0x48 > /sys/bus/i2c/devices/i2c-4/newdevice
instead it.
The main question is - wakeup chip, and gpios pins.
Actually, the procedure of
Hi Gregor,
Thank you for reply!
As I mentioned in linux-input@How to use ACPI for touchscreen - the acpi
provided info looks like total false.
For the begining I am trying to achieve mimimal - detect chip and just wake
up it.
Actually have tried - modified your driver for gsl1680 and also
Hi All :) that still keep silence!
I would like to mention the following :
In linux-sunxi there is
http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728_stripped/lichee/linux-3.4/drivers/input/touchscreen/icn83xx/
it is strange that the author is from Chipone, as minimum should be someone
who
Coud someone be so kind to describe how to initialize this chip?
I guess it has INT/WAKE gpio pin? Am I right?
How to find out having working touch in Android and Windows it ? There is
no at the moment driver in Linux for this touch, so I have not "right point
of start" for finding out gpio
Hi all,
Could please somebody be so kind to describe or reference to datasheet of
chipone85xx touchscreen controller.
AFAIK icn83xx is implemented in linux sunxi.
All I have discovered:
http://www.chiponeic.com/index.php/website/products/18
But what is the logic?
How to init the chip? Chip is
Hi Gregori.
Thank you for explanation regarding ACPI, but - in case if you have working
device (Android as I have wrote before) - all information is available from
Android kernel.
fortunately address on I2C is usually for touchscreens fixed and in my
case it is 0x38. (under Android it is
Hi, Priit.
But this is not new device (I mean touchscreen) - Chuwi Vi10
(approximately) has focaltech TS ft5x0x that is supported in sunxi under
arm or atmel, thats why I have created this thread - to grab practical info
and to port it to Baytrail.
I have mentioned Chuwi vi10 as a platform
Hiya All!
New tablet ;-) old problems.
Goal - to tun Linux on Chuwi Vi10 rev 11: Current problem: Make it working
touchscreen!
There are Android with i2c-tools on it and Windows 8. - for digging and
researching hardware.
What I have discovered in Android:
lsmod shows loaded atmel_mxt_ts
at
Hello, ALL.
Could anyone please describe the logic (concept (core) of algorithmic
logic) of how to work with IRQ line for GSL 1680.
Unfortunately on https://linux-sunxi.org/GSL1680 there is nothing about
this.
It will be very gooв to enhance this web page with this information.
As far as I
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
So while this might help with some tablets it's not going to work with
others.
I understand that tool that provides result immediately is cool but for the
case when it does not work anyone should try method that I have passed
before this tool was created:
1) Extract firmware from elf files
Thank you very much! This tool is one that what is missed in complete set
of make it working GSL1680.
Have ported your code to baytrail.
1st - these lines I think is rudшmental in section include (it is
important for porting! ) and came from user space driver where was used
uinput device.
Ok,
So fresh news and summary.
Many many thanks to Sergio Costas for his work and assistance. He wrote and
published FW extractor. I suppose it will be useful for someone trying to
make it works GSL1680.
In my case, Chuwi Vi8 super (baytrail architecture) it looks that chinese
developers put
Ok,
So fresh news and summary.
Many many thanks to Sergio Costas for his work and assistance. He wrote and
published FW extractor. I suppose it will be useful for someone trying to
make it works GSL1680.
In my case, Chuwi Vi8 super (baytrail architecture) it looks that chinese
developers put
I would like to rise up topic into the following direction: Lets try to
dump currently loaded firmware for GSL1680 on Adroid.
From the theory on https://linux-sunxi.org/GSL1680
Chip is located on I2C bus on 0x040 address
Firmware is reading/writing from/into chip via set of chunks, each 128
Since there are no recently any practical replies just report current
status - loosing hope that I could get correct firmware I have just added
rescaling to ported Sergio Costa's userspace driver and it woks pretty good
if not taking into account absence of using INT line from chip.
One more
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).
Thank you for make it clear.
;-) Lets transform this knowledge into practical result!
I have successfully compiled i2c-tools for x86 Android.
So, what is the exact command line to grab all loaded into GSL 1680 chip
firmware?
i2cbus or i2cget? and how to use it , How via this toolset I could
On Tuesday, May 19, 2015 at 12:53:43 PM UTC+3, Michal Suchanek wrote:
That's one page of the configuration which is 128 bytes or 32 integers.
Writing the page register gives access (read or write) to different pages.
So one blob might have multiple such pages or the firmware can be
composed of
Given extracted firmware from an Android driver for a 7inch A13 tablet.
Thanks, I will try this
https://code.google.com/p/yuandao-n90-window-dual-core-2/source/browse/drivers/input/touchscreen/gslx680_ts.h
BUT
in my case it is Chuwi vi8 super Baytrail tablet with 8 screen size
1280x800.
Som I
Regarding firmware extraction - some newer drivers print a message in
dmesg which firmware they loaded so that might be hint which one to
try first.
Thanks
Michal
Thanks but unfortunately in my case there is nothing in dmesg besides
fw_loading and fw_loaded, also fw is not loaded
Could you please explain more detailed this portion by reading registers 00
to 7F for each 128-byte block.
Questions:
1) Does it enough only one 128-byte block?
2) How to determine how much such 128byte blocks should be read and where
is the finish?
On Monday, May 18, 2015 at 11:52:13 AM
Thanks,
Am I understand right - all I need - it is just open .ko file, jumb to
symbols page and choose needed variable (4ex:
GSLX680_FW_I81_GSL3676B_8001280_OGS_SG) and choose export to binary and
as result I will get my firmware?
In that case = declarations exists in .rodata and .data.
To ALL:
Could anyone share binary static linked i2c tools for Baytrail x86 (i386)
Android? If I understand right simply PC-i386/i686 i2c-tool package will
not work?
On Monday, May 18, 2015 at 11:52:13 AM UTC+3, raste...@gmail.com wrote:
Check if you have the i2c tools in your android system,
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
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
28 matches
Mail list logo
