Android Tablets Forum banner
41 - 60 of 104 Posts

·
Registered
Joined
·
41 Posts
As for Elf II, touchscreen is:

Code:
I: Bus=0000 Vendor=0000 Product=0000 Version=0000<br />
N: Name="ft5x06"<br />
P: Phys=<br />
S: Sysfs=/devices/virtual/input/input5<br />
U: Uniq=<br />
H: Handlers=event5 <br />
B: PROP=0<br />
B: EV=b<br />
B: KEY=400 0 0 0 0 0 0 0 0 0 0<br />
B: ABS=650000 0<br />
Which is Focaltech I2C capacitive touchscreen in config. Tomorrow I'll check for Aurora, but you can also check with simple:
cat /proc/bus/input/devices
N: Name="ft5x06" for Aurora II
 

·
Registered
Joined
·
1,014 Posts
Discussion Starter · #42 ·
The touchscreen is likely to be the same in both devices, and the only real difference is the ips isn't it?
I only have an Elf II, (can't afford an aroura ii to test)

We need lcd/ips to get some kind of output before worrying about touch.

Sorry not being much help at the moment, been bed bound for a few days with not a lot of time awake.

Sent from my ELF-II using Tapatalk 2
 

·
Registered
Joined
·
1,014 Posts
Discussion Starter · #43 ·
Anarsoul, did you build a new uboot to go with the zimage? What did you use for the memory address in the command line when building the boot. img

Sent from my ELF-II using Tapatalk 2
 

·
Registered
Joined
·
148 Posts
The touchscreen is likely to be the same in both devices, and the only real difference is the ips isn't it?
I only have an Elf II, (can't afford an aroura ii to test)

We need lcd/ips to get some kind of output before worrying about touch.

Sorry not being much help at the moment, been bed bound for a few days with not a lot of time awake.

Sent from my ELF-II using Tapatalk 2
So, LCD and TS are not the same device/driver? Sorry if stating the obvious, but I'm new to android device configs
 

·
Registered
Joined
·
1,014 Posts
Discussion Starter · #45 ·
Yeah...
One does output the other input usually


Of course that's never 100% when it comes to some of these small GPL violators.. God knows what they do
.

In seriousness the touchscreen and lcd are more commonly bonded together, and so physically they are one.
however electrically they are different. Often the touchscreen is driven by a programmable micro cpu can be a tricky thing to get the code right, (the one in the hans pad was 2 touchscreens joined together and controlled by said microcpu). and so if we have that already we're doing well..

Sent from my ELF-II using Tapatalk 2
 

·
Registered
Joined
·
1,014 Posts
Just had a look and there only seems very generic amlcd devices inside the rom

3 i2c channels
i2c0 has
0x38 ft5x06 touchscreen
0x03c gt2005-i2c cmos sensor
i2c1 has
1x018 bma250 accelerometer
1x01a wm8960 wolfson audio code.
I2c2 has
2x034 Axp20, multifunction power management

I'd say all these are soc so likely to be in the amlogic common.
The cmos is common enough to have existing code if not. There is a weird one though a device with no hw allocation. ir_kbd_i2c

Now lcd......

Sent from my ELF-II using Tapatalk 2
 

·
Developer
Joined
·
427 Posts
It builds (already tried with codesourcery 2010q1 toolchain), however there're some compile errors in SMP code (they declared inline function in C file and then trying reference it from another file... gcc reports error
), but they're easy to fix...
Hi Anarsoul,
I also got a few warnings from gcc, could you please share with the rest of us how you fixed the offending code?

I am still trying to get my compilation to finish without fatal errors!
Thanks!
 

·
Registered
Joined
·
26 Posts
Anarsoul, did you build a new uboot to go with the zimage? What did you use for the memory address in the command line when building the boot. img
There's no need to build uboot\other bootloader, kernel can be launched by default uboot by this way:
1. Create uImage ( make uImage, or using mkimage )
2. Copy uImage to microSD card.
3. Rename to uImage_recovery
4. Shutdown and start recovery.
Also, it's possible to start by custom aml_autoscript, which is created by mkimage.
 

·
Registered
Joined
·
41 Posts
Just had a look and there only seems very generic amlcd devices inside the rom

3 i2c channels
i2c0 has
0x38 ft5x06 touchscreen
0x03c gt2005-i2c cmos sensor
i2c1 has
1x018 bma250 accelerometer
1x01a wm8960 wolfson audio code.
I2c2 has
2x034 Axp20, multifunction power management

I'd say all these are soc so likely to be in the amlogic common.
The cmos is common enough to have existing code if not. There is a weird one though a device with no hw allocation. ir_kbd_i2c

Now lcd......

Sent from my ELF-II using Tapatalk 2
On aurora there's hi253_i2c cmos sensor instead of gt2005
 

·
Registered
Joined
·
41 Posts
Hi Anarsoul,
I also got a few warnings from gcc, could you please share with the rest of us how you fixed the offending code?

I am still trying to get my compilation to finish without fatal errors!
Thanks!
As of SMP part, here's diff: http://dpaste.org/scJnM/
Now trying to fix mali driver, something's broken in its Makefile for sure, I'm getting a log of:
gcc: error: directory: No such file or directory
gcc: error: directory": No such file or directory
gcc: error: directory: No such file or directory
gcc: error: directory": No such file or directory

Also I did not fix HDMI driver, just disabled it.
 

·
Registered
Joined
·
1,014 Posts
Discussion Starter · #53 ·

·
Registered
Joined
·
1,014 Posts
Discussion Starter · #55 ·
OK i got it to compile, there is a uImage_recovery and uImage in the common folder.

in the install root dir i have /root/boot/mali.ko and ump.ko

What next? how to intergrate this with android source framework, etc. Any way we can get a config file from Aurora II or Elf II (both preferrably?) I could try if someone is willing to explain a bit.

Im guessing that diff conf is needed for different drivers on the devices, right?
I'm presuming (I haven't started looking at the uImage format yet)
that you'll need an initramfs somewhere along the way?

the easy way to get the initramfs is to extract it from one of Ainols boot.img and look at how they have the init set up..

I posted a script to extract it earlier in the thread.

are you using the kernel.mk ?
$ make -f kernel.mk INSTALL_ROOT=/PATH_TO_/initramfs/






http://openlinux.amlogic.com/index.php//3.Building_the_Code
for building a complete android system.
(you need a lot more than they say there as they expect you to have their build system from their ssh secured git server <<<< CRAP THATS NOT OPEN SOURCE)

for example we are likely to need proprietary files from our tablets, such as gralloc in a device tree.
 

·
Registered
Joined
·
41 Posts
Did anyone succeed to build mali driver from Ainol tree?

Btw, drivers/amlogic/power/aml_power.c tries to include missing linux/aml_power.h,
Also, arch/arm/mach-meson6/board-meson6-ref.c lacks power{on,off} function for
SDIO WiFi...

In general code quality is very poor, AMLogic did not use gpiolib framework,
clk framework, generic rfkill-gpio driver, code does not follow code style guide,
etc, etc...

I think it's too much work to clean up that code and reverse engineer missing parts,
can take up to several months.

I think AMLogic still violates GPL, it's close to impossible to compile _usable_ kernel image
from this crap they released.
 

·
Developer
Joined
·
427 Posts
As of SMP part, here's diff: http://dpaste.org/scJnM/
Now trying to fix mali driver, something's broken in its Makefile for sure, I'm getting a log of:
gcc: error: directory: No such file or directory
gcc: error: directory": No such file or directory
gcc: error: directory: No such file or directory
gcc: error: directory": No such file or directory

Also I did not fix HDMI driver, just disabled it.
Thank you very much!

I'll try again to compile the kernel and hopefully we can get a functional AML8726-MX kernel soon.
 
41 - 60 of 104 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top