[ALPHA] ICS for Optimus M (NOW COMPILED AND BOOTING) - Page 8

PlayfulGod · December 21st, 2011, 08:41 PM

lol

Code:

external/oprofile/libpp/format_output.h:94:22: error: reference ‘counts’ cannot be declared ‘mutable’ [-fpermissive]
host C++: liboprofile_pp <= external/oprofile/libpp/symbol_sort.cpp
host C++: liboprofile_pp <= external/oprofile/libpp/xml_utils.cpp
host C++: liboprofile_pp <= external/oprofile/libpp/populate_for_spu.cpp
In file included from external/oprofile/libpp/op_header.cpp:34:0:
external/oprofile/libpp/format_output.h:94:22: error: reference ‘counts’ cannot be declared ‘mutable’ [-fpermissive]
In file included from external/oprofile/libpp/format_output.cpp:26:0:
external/oprofile/libpp/format_output.h:94:22: error: reference ‘counts’ cannot be declared ‘mutable’ [-fpermissive]
true
host C: liboprofile_db <= external/oprofile/libdb/db_debug.c
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/liboprofile_pp_intermediates/op_header.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/liboprofile_pp_intermediates/arrange_profiles.o] Error 1
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/liboprofile_pp_intermediates/format_output.o] Error 1
In file included from external/oprofile/libpp/xml_utils.h:15:0,
                 from external/oprofile/libpp/xml_utils.cpp:14:
external/oprofile/libpp/format_output.h:94:22: error: reference ‘counts’ cannot be declared ‘mutable’ [-fpermissive]
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/liboprofile_pp_intermediates/xml_utils.o] Error 1
target StaticLib: libc (out/target/product/generic/obj/STATIC_LIBRARIES/libc_intermediates/libc.a)
target StaticLib: libc_nomalloc (out/target/product/generic/obj/STATIC_LIBRARIES/libc_nomalloc_intermediates/libc_nomalloc.a)

And yall are my first line of searching the issues out to help me save time n still work on other stuff too lol. So much appreciated.

AndroidHogs · December 21st, 2011, 08:47 PM

removed didnt help lol...

tripdoc79 · December 21st, 2011, 09:15 PM

i have the corerewct answer for you PG, lol.. let me switch back to windows.. as i believe that page is still open lol

frameworks/base/libs/utils/Android.mk
- LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS)

+ LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS) -fpermissive

external/oprofile/pp/Android.mk

- LOCAL_CFLAGS := $(common_host_cflags)
+ LOCAL_CFLAGS := $(common_host_cflags) -fpermissive
there are a few places you need to change this within that file i believe

build/core/combo/HOST_linux-x86.mk
+ HOST_GLOBAL_CFLAGS := -fpermissive

may need to learn chinese.. lol but here http://liuju1234.blog.163.com/blog/static/16228152011101813615351/
and here http://blog.csdn.net/flydream0/article/details/7046612

PlayfulGod · December 21st, 2011, 10:01 PM

Quote:

Originally Posted by ghost.rider

#625060 - oprofile: FTBFS: format_output.h:94:22: error: reference 'counts' cannot be declared 'mutable' [-fpermissive] - Debian Bug report logs

maybe this will help you@playfulgods

thats why i build on 10.04 not as many problems.

but ill do what i can to help you all out. As my experience in all this is very low. i only been doing this for about 3 weeks and learning something new everyday. Google helped me out and as many of you as well have helped me out

didnt help lol

AndroidHogs · December 21st, 2011, 10:52 PM

i did find this.

Migrating to Android Ice Cream Sandwich 4.0

In Ice Cream Sandwich 4.0, we changed the device driver requirements for touch screens to follow the standard Linux multitouch input protocol and added support for protocol "B". We also support digitizer tablets and stylus-based touch devices.
You will probably need to update your input device driver to implement the Linux multitouch input protocol correctly according to the standard.
You will also need to update your input device configuration files because some properties have been changed to be simpler and more systematic.

jacobmacek · December 21st, 2011, 11:46 PM

i really like the looks of this rom so i put it on my vortex, I got it to boot up but the touch screen wouldnt work and the buttons have diff. funtions. Can you make a modified version to fit the specs of the vortex?

AndroidHogs · December 21st, 2011, 11:58 PM

Only one thing to do right now. We are working as well as we can. the touchscreen will be working once we find out how "ICS" is laid out.

reppard · December 22nd, 2011, 01:18 AM

Quote:

Originally Posted by tripdoc79

new error for me.. but when doing make again its goes fine... wierd

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00002b5d29797163, pid=28946, tid=47679113225984
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# v ~BufferBlob::getPsrInfo_stub
#
# An error report file with more information is saved as:
# /home/tripdoc/android/system/hs_err_pid28946.log
#
# If you would like to submit a bug report, please visit:
# HotSpot Virtual Machine Error Reporting Page
#
make: *** [out/target/common/obj/APPS/HoneycombGallery_intermediates/classes-full-debug.jar] Aborted

hey trip, are you using open-jdk or sun-jdk? i have had better results with sun-jdk. hope that helps

shroomster · December 22nd, 2011, 01:49 AM

checking on the progress.....and bookmarking this thread

reppard · December 22nd, 2011, 09:52 AM

Ok so I syced up with AOSP last night and compiled full-eng error free in Ubuntu 11.1. I also got my laptop in a state of kernel building. I wil try and work on getting some updated drivers into the kernel tonight when I get home from work.

edit: and when i said error free, i mean error free. Not one error, not even an xml error.

PlayfulGod · December 22nd, 2011, 10:48 AM

Quote:

Originally Posted by reppard

Ok so I syced up with AOSP last night and compiled full-eng error free in Ubuntu 11.1. I also got my laptop in a state of kernel building. I wil try and work on getting some updated drivers into the kernel tonight when I get home from work.

edit: and when i said error free, i mean error free. Not one error, not even an xml error.

ok bro what did u do to get it setup for it and does others builds still build?

reppard · December 22nd, 2011, 11:12 AM

Quote:

Originally Posted by PlayfulGod

ok bro what did u do to get it setup for it and does others builds still build?

I installed gcc 4.4 (4.4.6 to be exact) and sun-jdk. I made sure my system was using gcc 4.4. repo sync to get rid of any edits i made while trying to build the first time. . build/envsetup.sh; lunch full-eng; make -j8. ran without one hiccup. Dont know about other builds as this is the first time i've tried to build anything in a while. Hope that helps. Lemme know if you have any specific problems.

PlayfulGod · December 22nd, 2011, 11:39 AM

I'm still getting

Code:

external/oprofile/libpp/format_output.h:94:22: error: reference ‘counts’ cannot be declared ‘mutable’ [-fpermissive]
host C++: liboprofile_pp <= external/oprofile/libpp/populate.cpp
host C++: liboprofile_pp <= external/oprofile/libpp/profile.cpp
host C++: liboprofile_pp <= external/oprofile/libpp/profile_container.cpp
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/liboprofile_pp_intermediates/arrange_profiles.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/liboprofile_pp_intermediates/format_output.o] Error 1
In file included from external/oprofile/libpp/op_header.cpp:34:0:
external/oprofile/libpp/format_output.h:94:22: error: reference ‘counts’ cannot be declared ‘mutable’ [-fpermissive]
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/liboprofile_pp_intermediates/op_header.o] Error 1

I will resync n see if it helps...

tripdoc79 · December 22nd, 2011, 12:12 PM

Quote:

Originally Posted by jacobmacek

i really like the looks of this rom so i put it on my vortex, I got it to boot up but the touch screen wouldnt work and the buttons have diff. funtions. Can you make a modified version to fit the specs of the vortex?

dopnt own a vortex.. working on this phone now.. when its functional for this phone, it may be possible, but no promisses lol

tripdoc79 · December 22nd, 2011, 12:12 PM

PG did you try the fix i posted above?

tripdoc79 · December 22nd, 2011, 12:13 PM

Quote:

Originally Posted by reppard

hey trip, are you using open-jdk or sun-jdk? i have had better results with sun-jdk. hope that helps

was using sun-jdk, installed open-jdk on top of it, still got java errors, they were wierd, it would eror out, and then i wwould make again without changing anything and it would go through.. going to remove open-jdk

PlayfulGod · December 22nd, 2011, 01:08 PM

had missed em and have added em now, but getting another one now lol. Beginning to think today isnt a coding day lol

Skitzoe · December 22nd, 2011, 01:18 PM

Ice cream sandwich!!!

tripdoc79 · December 22nd, 2011, 03:19 PM

todays not working for me either.. lol.. updated ubuntu through the update manager.. still at 10.04 thankfully.. but kernel was updated and now my video drivers are broken.. only 1 screen turns on... desktop is tiny... like 800x600.. i boot into the old kernel, and only have 1 screen.. cant get the other to turn on.. tried about 10 fixes.. nothing.. wouldnt mind so much if it was my big monitor working, but its my smaller one.. not that 21 is bad. but im spoiled.. lol.. gonna play some skyrim.. take a break.. and ill get back to it.. i finished a compile last night, going to see if it boots when i log back into ubuntu

AndroidHogs · December 22nd, 2011, 04:24 PM

I believe cyanogenmods github has a updated driver for synatic_i2c_rmi it just needs some editing. I I'm going to try and compile the kernel again. And try and fix these errors.

undacova · December 22nd, 2011, 08:03 PM

Quote:

Originally Posted by playfulgod

for 1 windows sux for anything other than gaming n web surfing, 2.) you dont develop linux in windows, you develop it in linux.

@tripdoc, still issues lol.

ftfy

tripdoc79 · December 22nd, 2011, 09:03 PM

EDIT: removed my rant

AndroidHogs · December 22nd, 2011, 09:13 PM

Quote:

Originally Posted by tripdoc79

this is infuriating.... been at this for hours.. nothing friggin works.. kernel updated.. nvidia drivers broke, was looking around, nvidia kernel need to be recompiled with new linux kernel headers.. one problem.. when i go to install the drivers, it says "these drivers are already installed, would you like to uninstall and re-install?" YES i would, ok done, load up gdm, guess what.. still dotnw ork, try to uninstall drivers through terminal, sudo apt-get remove --purge nvidia* "E: no packages selected" blacklist, nothing, blacklist nouvea drivers, nothing, install nouvea drivers.. nothing, not a single change, nvidia settings is still there, both of my monitors are showing up in settings, but my second one shows up as not being connected to a video card, now how on earth would you know it was there if it wasnt connected? its just in its own place, not as an xscreen, just chillin, heres your 8500GT with xscreen0 connected to it, heres your GTX460, with nothing connected to it, heres your 24inch acer display, not connected. REALLY????????

Try webchat.freenode.net

And go to Ubuntu. If you already have a account just identify yourself. And got to Ubuntu they might be able to give you some help.

tripdoc79 · December 22nd, 2011, 09:58 PM

nope.. re-install.. lovely.. looks like after i re-install i wont be updating for quite a while lol

AndroidHogs · December 22nd, 2011, 10:32 PM

lol... im never updating its working for me just fine and i dont want to do updates that will cause some new error..

tripdoc79 · December 22nd, 2011, 10:35 PM

got it fixed.. after hours of toil.. stupid X server wasnt updating my xorg.conf file.. finally.. lol

hows your kernel project coming? anything new?

AndroidHogs · December 22nd, 2011, 10:39 PM

i can compile it. but im trying to get the cyanogen kernel to compile for synaptics

AndroidHogs · December 23rd, 2011, 07:26 AM

So I think I found out how stuff has to be added. You have to add it in the ICS source yourself. Just putting files in the device make and have it be called doesn't work. For some reason. '\

tripdoc79 · December 23rd, 2011, 10:52 AM

what id like to know is why nothing that i have compiled on 10.04 will boot.. the first completed compile on VM in 11.10 with a crap ton of workarounds booted first time it completed.. im using the same files.. only files that arent the same are the files i didnt have to edit for gcc incompatability... im about to copy my entire source directory from vmware and see if it boots...

UPDATE: ok this one did boot, took the better part of 20 minutes, but it did boot, unfortionately it has less functionality then the first compile, the screen flickers, touch doesnt work at all from what i can tell.. first build booted in a few minutes just like any other fresh flash..
also see alot of goldfish libs in my out folder that i didnt see before.. almost like ghost.riders problem with things not being added.. very strange..

AndroidHogs · December 23rd, 2011, 04:03 PM

Yea i went into frameworks and added the idc file just to see if it would get added to the source out folder. and guess what it was added. :\

jsphmuckey · December 23rd, 2011, 06:58 PM

I cant believe the optimus m has come this far!! ICS? If beta comes out, I might need to downgrade mine & switch back to my lg since not much is goin on in Admire land lol

AndroidHogs · December 23rd, 2011, 07:09 PM

Need someone that knows how to config kernel drivers for the touchscreen so it use pressure. i am not a expertise in that field so i am really not much of a help. if someone knows how to config it. please do so. so we can get further on making this work for our optimus M...

Primed · December 23rd, 2011, 07:09 PM

Quote:

Originally Posted by jsphmuckey

I cant believe the optimus m has come this far!! ICS? If beta comes out, I might need to downgrade mine & switch back to my lg since not much is goin on in Admire land lol

Yeah, I switched from my Admire back to my Optimus M, too. xD although I think someone is working on CM7 for the Admire.. Maybe we'll just have to wait and see.

Android?What!? · December 23rd, 2011, 07:35 PM

Quote:

Originally Posted by ghost.rider

Need someone that knows how to config kernel drivers for the touchscreen so it use pressure. i am not a expertise in that field so i am really not much of a help. if someone knows how to config it. please do so. so we can get further on making this work for our optimus M...

What's new on this since the first rom post? If you dont mind me asking that is

reppard · December 23rd, 2011, 07:46 PM

Quote:

Originally Posted by ghost.rider

Need someone that knows how to config kernel drivers for the touchscreen so it use pressure. i am not a expertise in that field so i am really not much of a help. if someone knows how to config it. please do so. so we can get further on making this work for our optimus M...

I'm gonna work on a kernel this weekend if I have time.

tripdoc79 · December 23rd, 2011, 10:46 PM

Quote:

Originally Posted by Android?What!?

What's new on this since the first rom post? If you dont mind me asking that is

not much.. we have been working on getting the screen to work, which will require updating the drivers in the kernel to meet the current requirements of ICS. we have tried many fixes, none of which have worked, and some have made things worse. google has made various kernel source available to the public, which has been updated, and we can hope includes updated drivers for various hardware, but unfortunately, nobody can get the kernel source to unpack, at least for the kernel we want.. so as it is, its either wait and continue trying to get the kernel source to sync correctly, or re-write our own drivers. i have tried the latter, unfortunately, i have had no success in that endeavor, and since switching from a VirtualBox to dual booting Ubuntu, i have yet to compile a ROM that that is as stable as the first one i compiled.. so i am currently moving my previous source to the new machine, may be some file that i have forgotten about that im missing, im not sure, this will be much easier when i can find the time to setup my github and fork everything correctly. anyway we thank you for your patience, and are working as much as we can on getting this working.

tripdoc79 · December 23rd, 2011, 11:02 PM

@reppard, ghostrider

just found this, everything looks to be coded correctly, going to pull it and try to compile our kernel with it. all calls have been changed to meet the new kernel standards.

https://github.com/CyanogenMod/lge-kernel-cosmo/blob/android-omap-2.6.35/drivers/input/touchscreen/synaptics_i2c_rmi.c

the headers are different, i may just pull that whole kernel and try to compile it with our config, restoring my phone to the stock rom and pulling a config from the kernel, funky sentence, but i was making up my mind as i was typing.. lol yeah.. so im gonna get started on this, its the new lg kernel source, have to check and see if any patches are going to be required for this.. cross your fingers.

tripdoc79 · December 23rd, 2011, 11:47 PM

ok.. i have configured the kernel for our phone, but somewhere it is still calling cosmo drivers.. i have to track down where its being called.. as im sure things have been edited int his kernel.. but here is the error im getting

Code:

LD      drivers/cosmo/charger/built-in.o
  LD      drivers/cosmo/fuel_gauge/built-in.o
  CC      drivers/cosmo/misc/vibrator.o
drivers/cosmo/misc/vibrator.c:25:26: error: plat/dmtimer.h: No such file or directory
drivers/cosmo/misc/vibrator.c:27:27: error: mach/vibrator.h: No such file or directory
drivers/cosmo/misc/vibrator.c: In function 'set_gptimer_pwm_vibrator':
drivers/cosmo/misc/vibrator.c:82: error: implicit declaration of function 'omap_dm_timer_enable'
drivers/cosmo/misc/vibrator.c:83: error: implicit declaration of function 'omap_dm_timer_set_match'
drivers/cosmo/misc/vibrator.c:84: error: implicit declaration of function 'omap_dm_timer_set_pwm'
drivers/cosmo/misc/vibrator.c:84: error: 'OMAP_TIMER_TRIGGER_OVERFLOW_AND_COMPARE' undeclared (first use in this function)
drivers/cosmo/misc/vibrator.c:84: error: (Each undeclared identifier is reported only once
drivers/cosmo/misc/vibrator.c:84: error: for each function it appears in.)
drivers/cosmo/misc/vibrator.c:85: error: implicit declaration of function 'omap_dm_timer_set_load_start'
drivers/cosmo/misc/vibrator.c:90: error: implicit declaration of function 'omap_dm_timer_stop'
drivers/cosmo/misc/vibrator.c:91: error: implicit declaration of function 'omap_dm_timer_disable'
drivers/cosmo/misc/vibrator.c: In function 'vibrator_probe':
drivers/cosmo/misc/vibrator.c:180: error: implicit declaration of function 'omap_dm_timer_request_specific'
drivers/cosmo/misc/vibrator.c:180: warning: assignment makes pointer from integer without a cast
drivers/cosmo/misc/vibrator.c:189: error: implicit declaration of function 'omap_dm_timer_set_source'
drivers/cosmo/misc/vibrator.c:189: error: 'OMAP_TIMER_SRC_SYS_CLK' undeclared (first use in this function)
drivers/cosmo/misc/vibrator.c:197: error: dereferencing pointer to incomplete type
drivers/cosmo/misc/vibrator.c:198: error: dereferencing pointer to incomplete type
drivers/cosmo/misc/vibrator.c:210: error: dereferencing pointer to incomplete type
drivers/cosmo/misc/vibrator.c: In function 'vibrator_remove':
drivers/cosmo/misc/vibrator.c:231: error: dereferencing pointer to incomplete type
drivers/cosmo/misc/vibrator.c:232: error: dereferencing pointer to incomplete type
drivers/cosmo/misc/vibrator.c: At top level:
drivers/cosmo/misc/vibrator.c:247: error: 'VIB_PWM_NAME' undeclared here (not in a function)
make[3]: *** [drivers/cosmo/misc/vibrator.o] Error 1
make[2]: *** [drivers/cosmo/misc] Error 2
make[1]: *** [drivers/cosmo] Error 2
make: *** [drivers] Error 2

its calling cosmo drivers.. i think if we can get past this this just may work.. im headed to bed for the night.. but will pick this back up int he morning. in the meantime if anyone else wants to give this a shot, thanx lol see yall in the morn

tripdoc79 · December 24th, 2011, 01:44 PM

past those errors.. have a new error.. working it out.. this thing is so close to a compile.. lol.. the cosmo vibrate driver is being called by our config, i removed the call for it.. we'll get the vibrate working later.. im getting as misc driver error now.. im going through the code trying to sort it out now.

tripdoc79 · December 24th, 2011, 04:39 PM

ok.. this all relates to the vibrate actuator from what i can see.. its also device specific, and its not for our device..

Quote:

if defined(CONFIG_MACH_LGE_COSMO_REV_A) || defined(CONFIG_MACH_LGE_COSMO_REV_B) || defined(CONFIG_MACH_LGE_COSMO_REV_C)

these driver files are also not present in the stock kernel for our phone, and im using the config for our phone, so im not sure why they are being called, the errors are all omap related, and we are using msm, another confusion.. but here is the error im trying to work around.. i have yet to track down where these drivers are being called to even be included..

Quote:

CC drivers/misc/tspdrv/tspdrv.o
In file included from drivers/misc/tspdrv/tspdrv.c:46:
drivers/misc/tspdrv/ImmVibeSPI.c:68:1: warning: "PWM_DUTY_MAX" redefined
drivers/misc/tspdrv/ImmVibeSPI.c:47:1: warning: this is the location of the previous definition
In file included from drivers/misc/tspdrv/tspdrv.c:46:
drivers/misc/tspdrv/ImmVibeSPI.c: In function 'vib_generatePWM':
drivers/misc/tspdrv/ImmVibeSPI.c:105: error: implicit declaration of function 'omap_dm_timer_enable'
drivers/misc/tspdrv/ImmVibeSPI.c:106: error: implicit declaration of function 'omap_dm_timer_set_match'
drivers/misc/tspdrv/ImmVibeSPI.c:107: error: implicit declaration of function 'omap_dm_timer_set_pwm'
drivers/misc/tspdrv/ImmVibeSPI.c:107: error: 'OMAP_TIMER_TRIGGER_OVERFLOW_AND_COMPARE' undeclared (first use in this function)
drivers/misc/tspdrv/ImmVibeSPI.c:107: error: (Each undeclared identifier is reported only once
drivers/misc/tspdrv/ImmVibeSPI.c:107: error: for each function it appears in.)
drivers/misc/tspdrv/ImmVibeSPI.c:108: error: implicit declaration of function 'omap_dm_timer_set_load_start'
drivers/misc/tspdrv/ImmVibeSPI.c:117: error: implicit declaration of function 'omap_dm_timer_stop'
drivers/misc/tspdrv/ImmVibeSPI.c:118: error: implicit declaration of function 'omap_dm_timer_disable'
drivers/misc/tspdrv/ImmVibeSPI.c: In function 'ImmVibeSPI_ForceOut_Initialize':
drivers/misc/tspdrv/ImmVibeSPI.c:177: error: implicit declaration of function 'omap_dm_timer_request_specific'
drivers/misc/tspdrv/ImmVibeSPI.c:177: warning: assignment makes pointer from integer without a cast
drivers/misc/tspdrv/ImmVibeSPI.c:182: error: implicit declaration of function 'omap_dm_timer_set_source'
drivers/misc/tspdrv/ImmVibeSPI.c:182: error: 'OMAP_TIMER_SRC_SYS_CLK' undeclared (first use in this function)
In file included from drivers/misc/tspdrv/tspdrv.c:46:
drivers/misc/tspdrv/ImmVibeSPI.c: In function 'ImmVibeSPI_ForceOut_SetSamples':
drivers/misc/tspdrv/ImmVibeSPI.c:255: error: implicit declaration of function 'omap_dm_timer_start'
drivers/misc/tspdrv/ImmVibeSPI.c:211: warning: unused variable 'tmp'
make[3]: *** [drivers/misc/tspdrv/tspdrv.o] Error 1
make[2]: *** [drivers/misc/tspdrv] Error 2
make[1]: *** [drivers/misc] Error 2
make: *** [drivers] Error 2

tripdoc79 · December 24th, 2011, 04:48 PM

new plan of attack.. going to try to compile new drivers with existing kernel source

EDIT:
added drivers to our kernel source.. had a few warning when compiling it.. but made it past and its still going.. just might make it to the end.. hopefully it does.. then time to pack it and flash it

got an error,, at what i hope is the end..

Quote:

LD .tmp_vmlinux1
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function mtc_send_key_log_data:tlmm-msm7200a.c(.text+0x3fdd4): error: undefined reference to 'max_x'
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function mtc_send_key_log_data:tlmm-msm7200a.c(.text+0x3fdd8): error: undefined reference to 'max_y'
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: drivers/built-in.o: in function SynaDoReflash:lowmemorykiller.c(.text+0x88134): error: undefined reference to 'is_need_forced_update'
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: drivers/built-in.o: in function SynaDoReflash:lowmemorykiller.c(.text+0x8813c): error: undefined reference to 'is_fw_reflash'
make: *** [.tmp_vmlinux1] Error 1

Android?What!? · December 24th, 2011, 07:28 PM

I can almost taste the ice cream

reppard · December 24th, 2011, 09:06 PM

Quote:

Originally Posted by tripdoc79

new plan of attack.. going to try to compile new drivers with existing kernel source

EDIT:
added drivers to our kernel source.. had a few warning when compiling it.. but made it past and its still going.. just might make it to the end.. hopefully it does.. then time to pack it and flash it

got an error,, at what i hope is the end..

There are a few things missing from that driver that our lge board source needs....still noodling this one over in the ol brain.

p-bOt · December 25th, 2011, 01:43 AM

I can't hit the thanks button enough for what you guys are doing. Really great job. I admire your dedication because honestly I would have put a few bullets through my monitor by now lol

tripdoc79 · December 25th, 2011, 01:35 PM

Quote:

Originally Posted by reppard

There are a few things missing from that driver that our lge board source needs....still noodling this one over in the ol brain.

yeah i noticed that the error i have is coming from the new driver.. im digging around in the cosmo kernel source trying to find where those 4 things are being defined, once i have that figured out i think it will work

AndroidHogs · December 25th, 2011, 01:43 PM

Check the kconfig files that's where their being called.

tripdoc79 · December 25th, 2011, 02:37 PM

just tried something probably not going to wok.. lol.. changed the define from uint16_t to int.. max x and max y are being defined in the driver file.. in the section of code where they are used..

uint16_t max_x, max_y;

tripdoc79 · December 25th, 2011, 02:40 PM

Code:

CC      drivers/input/touchscreen/synaptics_reflash.o
In file included from drivers/input/touchscreen/synaptics_reflash.c:22:
drivers/input/touchscreen/synaptics_abstractionlayer.h:52: warning: function declaration isn't a prototype
In file included from drivers/input/touchscreen/synaptics_reflash.c:23:
drivers/input/touchscreen/synaptics_firmwareimage.h:1814: warning: large integer implicitly truncated to unsigned type
In file included from drivers/input/touchscreen/synaptics_reflash.c:24:
drivers/input/touchscreen/synaptics_reflash.h:15: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:16: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:17: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:18: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:19: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:21: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:23: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:24: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:26: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:27: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.h:30: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:80: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:91: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c: In function 'SynaReadFirmwareInfo':
drivers/input/touchscreen/synaptics_reflash.c:103: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
drivers/input/touchscreen/synaptics_reflash.c: At top level:
drivers/input/touchscreen/synaptics_reflash.c:108: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c: In function 'SynaReadConfigInfo':
drivers/input/touchscreen/synaptics_reflash.c:120: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
drivers/input/touchscreen/synaptics_reflash.c: At top level:
drivers/input/touchscreen/synaptics_reflash.c:124: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:142: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c: In function 'RMI4WaitATTN':
drivers/input/touchscreen/synaptics_reflash.c:211: warning: unused variable 'm_ret'
drivers/input/touchscreen/synaptics_reflash.c: At top level:
drivers/input/touchscreen/synaptics_reflash.c:314: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:326: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:338: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:421: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:426: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:431: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:509:1: warning: "/*" within comment
drivers/input/touchscreen/synaptics_reflash.c:511: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c: In function 'SynaFlashFirmwareWrite':
drivers/input/touchscreen/synaptics_reflash.c:517: warning: unused variable 'i'
drivers/input/touchscreen/synaptics_reflash.c:515: warning: unused variable 'temp'
drivers/input/touchscreen/synaptics_reflash.c: At top level:
drivers/input/touchscreen/synaptics_reflash.c:561: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c:586: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_reflash.c: In function 'SynaProgramConfiguration':
drivers/input/touchscreen/synaptics_reflash.c:591: warning: unused variable 'i'
drivers/input/touchscreen/synaptics_reflash.c:590: warning: unused variable 'temp'
drivers/input/touchscreen/synaptics_reflash.c: At top level:
drivers/input/touchscreen/synaptics_reflash.c:634: warning: function declaration isn't a prototype
  CC      drivers/input/touchscreen/synaptics_abstractionlayer.o
In file included from drivers/input/touchscreen/synaptics_abstractionlayer.c:1:
drivers/input/touchscreen/synaptics_abstractionlayer.h:52: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_abstractionlayer.c:17: warning: function declaration isn't a prototype
drivers/input/touchscreen/synaptics_abstractionlayer.c: In function 'SynaI2CClientInit':
drivers/input/touchscreen/synaptics_abstractionlayer.c:128: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'struct i2c_client *'
  CC      drivers/input/touchscreen/mcs6000_ts.o
drivers/input/touchscreen/mcs6000_ts.c: In function 'mcs6000_ts_probe':
drivers/input/touchscreen/mcs6000_ts.c:710: warning: unused variable 'hw_ver'
drivers/input/touchscreen/mcs6000_ts.c:710: warning: unused variable 'fw_ver'

there is a slight issue.. the file i am getting these warnings on.. doesnt exist int he cosmo source

Code:

CC      drivers/video/msm/mddi_hitachi_hvga.o
drivers/video/msm/mddi_hitachi_hvga.c: In function 'mddi_hitachi_lcd_vsync_detected':
drivers/video/msm/mddi_hitachi_hvga.c:455: warning: unused variable 'num_vsyncs'
drivers/video/msm/mddi_hitachi_hvga.c:454: warning: unused variable 'elapsed_us'
drivers/video/msm/mddi_hitachi_hvga.c:453: warning: unused variable 'now'
drivers/video/msm/mddi_hitachi_hvga.c:450: warning: unused variable 'first_time'
drivers/video/msm/mddi_hitachi_hvga.c:449: warning: unused variable 'start_time'
drivers/video/msm/mddi_hitachi_hvga.c: In function 'mddi_hitachi_lcd_init':
drivers/video/msm/mddi_hitachi_hvga.c:731: warning: ISO C90 forbids mixed declarations and code
drivers/video/msm/mddi_hitachi_hvga.c: At top level:
drivers/video/msm/mddi_hitachi_hvga.c:36: warning: 'mddi_hitachi_curr_vpos' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:37: warning: 'mddi_hitachi_monitor_refresh_value' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:38: warning: 'mddi_hitachi_report_refresh_measurements' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:48: warning: 'mddi_hitachi_usecs_per_refresh' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:107: warning: 'mddi_hitachi_display_on_1st' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:133: warning: 'mddi_hitachi_display_off' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:152: warning: 'mddi_hitachi_initialize_1st' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:303: warning: 'mddi_hitachi_initialize_3rd_p500' defined but not used
drivers/video/msm/mddi_hitachi_hvga.c:384: warning: 'compare_table' defined but not used
  CC      drivers/video/msm/mddi_novatek_hvga.o
drivers/video/msm/mddi_novatek_hvga.c: In function 'mddi_novatek_lcd_vsync_detected':
drivers/video/msm/mddi_novatek_hvga.c:1022: warning: unused variable 'num_vsyncs'
drivers/video/msm/mddi_novatek_hvga.c:1021: warning: unused variable 'elapsed_us'
drivers/video/msm/mddi_novatek_hvga.c:1020: warning: unused variable 'now'
drivers/video/msm/mddi_novatek_hvga.c:1017: warning: unused variable 'first_time'
drivers/video/msm/mddi_novatek_hvga.c:1016: warning: unused variable 'start_time'
drivers/video/msm/mddi_novatek_hvga.c: At top level:
drivers/video/msm/mddi_novatek_hvga.c:1172: warning: initialization from incompatible pointer type
drivers/video/msm/mddi_novatek_hvga.c:1172: warning: initialization from incompatible pointer type
drivers/video/msm/mddi_novatek_hvga.c: In function 'mddi_novatek_lcd_init':
drivers/video/msm/mddi_novatek_hvga.c:1236: warning: ISO C90 forbids mixed declarations and code
drivers/video/msm/mddi_novatek_hvga.c: At top level:
drivers/video/msm/mddi_novatek_hvga.c:61: warning: 'mddi_novatek_curr_vpos' defined but not used
drivers/video/msm/mddi_novatek_hvga.c:62: warning: 'mddi_novatek_monitor_refresh_value' defined but not used
drivers/video/msm/mddi_novatek_hvga.c:63: warning: 'mddi_novatek_report_refresh_measurements' defined but not used
drivers/video/msm/mddi_novatek_hvga.c:73: warning: 'mddi_novatek_usecs_per_refresh' defined but not used
drivers/video/msm/mddi_novatek_hvga.c:131: warning: 'mddi_novatek_display_on' defined but not used
drivers/video/msm/mddi_novatek_hvga.c:151: warning: 'mddi_novatek_display_off' defined but not used
drivers/video/msm/mddi_novatek_hvga.c:953: warning: 'compare_table' defined but not used
  LD      drivers/video/msm/built-in.o

also why is it calling 2 screens? that was the 2 differant model of the phone right?

andheres the last.. still get the same error, even changing uint16_t to int

Code:

/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function mtc_send_key_log_data:tlmm-msm7200a.c(.text+0x3fdd4): error: undefined reference to 'max_x'
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function mtc_send_key_log_data:tlmm-msm7200a.c(.text+0x3fdd8): error: undefined reference to 'max_y'
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: drivers/built-in.o: in function SynaDoReflash:lowmemorykiller.c(.text+0x88134): error: undefined reference to 'is_need_forced_update'
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: drivers/built-in.o: in function SynaDoReflash:lowmemorykiller.c(.text+0x8813c): error: undefined reference to 'is_fw_reflash'
make: *** [.tmp_vmlinux1] Error 1

tripdoc79 · December 25th, 2011, 02:55 PM

the kgonfig and makefile are differant.. i copied them over.. got a few more options.. might need to tweak them.. but its a start i think the cosmo uses the same screen as us.. if not i think its similar.. the makefile had 5 differant options for synaptics i2c toushscreen

tripdoc79 · December 25th, 2011, 03:09 PM

ok.. i copied the kconfig, makefile synaptics_i2c_rmi.c, synaptics_ts_firmare.h, synaptics_ts_firmware_rev_c.h from the cosmo driver/input/touchscreen directory to our kernel, and the synaptics_i2c_rmi.h file from cosmo to our kernel in /includes/linux, have to add int use_irq to the file, i made it through the driver section without any warnings at all, went right through, i am however still getting the max x and max y error, but i am not getting the other 2 errors anymore.. so close...

Code:

  CC      drivers/input/sensor/ami304.o
  LD      drivers/input/sensor/built-in.o
  CC      drivers/input/touchscreen/synaptics_i2c_rmi.o
  LD      drivers/input/touchscreen/built-in.o
  CC      drivers/input/keyreset.o
  LD      drivers/input/built-in.o
  CC      drivers/leds/led-core.o
  CC      drivers/leds/led-class.o

/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function mtc_send_key_log_data:tlmm-msm7200a.c(.text+0x3fdd4): error: undefined reference to 'max_x'
/home/tripdoc/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: arch/arm/mach-msm/built-in.o: in function mtc_send_key_log_data:tlmm-msm7200a.c(.text+0x3fdd8): error: undefined reference to 'max_y'
make: *** [.tmp_vmlinux1] Error 1

max x and y errors is coming from from something in the arch/arm/mach-msm/lge folder i think

Code:

  CC      arch/arm/mach-msm/lge/lge_handle_panic.o
arch/arm/mach-msm/lge/lge_handle_panic.c: In function 'display_panic_reason':
arch/arm/mach-msm/lge/lge_handle_panic.c:231: warning: comparison between pointer and integer
  CC      arch/arm/mach-msm/lge/lge_proc_comm.o
  CC      arch/arm/mach-msm/lge/LG_rapi_client.o
arch/arm/mach-msm/lge/LG_rapi_client.c:62: warning: type defaults to 'int' in declaration of 'boot_info'
arch/arm/mach-msm/lge/LG_rapi_client.c: In function 'msm_chg_LG_cable_type':
arch/arm/mach-msm/lge/LG_rapi_client.c:94: warning: ISO C90 forbids mixed declarations and code
  CC      arch/arm/mach-msm/lge/lge_mtd_direct_access.o
arch/arm/mach-msm/lge/lge_mtd_direct_access.c:96: warning: initialization from incompatible pointer type
arch/arm/mach-msm/lge/lge_mtd_direct_access.c:106: warning: initialization from incompatible pointer type
arch/arm/mach-msm/lge/lge_mtd_direct_access.c:133: warning: initialization from incompatible pointer type
arch/arm/mach-msm/lge/lge_mtd_direct_access.c:230: warning: initialization from incompatible pointer type
  CC      arch/arm/mach-msm/lge/lg_diag_testmode.o
arch/arm/mach-msm/lge/lg_diag_testmode.c: In function 'LGF_TestModeBlueTooth_RW':
arch/arm/mach-msm/lge/lg_diag_testmode.c:182: warning: passing argument 3 of 'update_diagcmd_state' makes integer from pointer without a cast
arch/arm/mach-msm/lge/lg_fw_diag_communication.h:28: note: expected 'int' but argument is of type 'byte *'
arch/arm/mach-msm/lge/lg_diag_testmode.c:202: warning: format '%d' expects type 'int', but argument 4 has type 'byte *'
  CC      arch/arm/mach-msm/lge/lg_fw_diag_class.o
  CC      arch/arm/mach-msm/lge/lg_fw_diag_communication.o
  CC      arch/arm/mach-msm/lge/lg_diag_event_log.o
  CC      arch/arm/mach-msm/lge/lg_diag_keypress.o
arch/arm/mach-msm/lge/lg_diag_keypress.c:67: warning: excess elements in array initializer
arch/arm/mach-msm/lge/lg_diag_keypress.c:67: warning: (near initialization for 'keytrans_table')
arch/arm/mach-msm/lge/lg_diag_keypress.c:68: warning: excess elements in array initializer
arch/arm/mach-msm/lge/lg_diag_keypress.c:68: warning: (near initialization for 'keytrans_table')
arch/arm/mach-msm/lge/lg_diag_keypress.c:69: warning: excess elements in array initializer
arch/arm/mach-msm/lge/lg_diag_keypress.c:69: warning: (near initialization for 'keytrans_table')
  CC      arch/arm/mach-msm/lge/lg_diag_screen_shot.o
  CC      arch/arm/mach-msm/lge/lg_diag_udm.o
  CC      arch/arm/mach-msm/lge/lg_fw_diag_mtc.o
  CC      arch/arm/mach-msm/lge/lg_diag_wifi.o
  CC      arch/arm/mach-msm/lge/lg_pcb_version.o
  CC      arch/arm/mach-msm/lge/board-thunderc.o
  CC      arch/arm/mach-msm/lge/board-thunderc-mmc.o
  CC      arch/arm/mach-msm/lge/board-thunderc-snd.o
  CC      arch/arm/mach-msm/lge/board-thunderc-panel.o
  CC      arch/arm/mach-msm/lge/board-thunderc-bt.o
  CC      arch/arm/mach-msm/lge/board-thunderc-camera.o
  CC      arch/arm/mach-msm/lge/board-thunderc-input.o
arch/arm/mach-msm/lge/board-thunderc-input.c: In function 'ts_set_vreg':
arch/arm/mach-msm/lge/board-thunderc-input.c:206: warning: unused variable 'rc'
arch/arm/mach-msm/lge/board-thunderc-input.c: At top level:
arch/arm/mach-msm/lge/board-thunderc-input.c:250: warning: initialization from incompatible pointer type
  CC      arch/arm/mach-msm/lge/board-thunderc-misc.o
arch/arm/mach-msm/lge/board-thunderc-misc.c:465: warning: 'thunderc_hs_mic_bias_power' defined but not used
  CC      arch/arm/mach-msm/lge/board-thunderc-pm.o
  CC      arch/arm/mach-msm/lge/lge_flight_mode.o
arch/arm/mach-msm/lge/lge_flight_mode.c: In function 'lge_tempdevice_probe':
arch/arm/mach-msm/lge/lge_flight_mode.c:81: warning: no return statement in function returning non-void
  CC      arch/arm/mach-msm/lge/devices_lge.o