[LG Optimus L9 P760, P765, P768, P769] villan.co:
yes, "porting" is exactly what i'm doing, if i can get gcc to f*cking compile - arrrgh! i've had the source code for compiling u-boot and x-boot for a while now, but i don't know how to get past that f*cking gcc error. i got 2 threads on the gcc problem, and no help.

http://xdaforums.com/showthread.php?t=2474927

http://forums.debian.net/viewtopic.php?f=8&t=107984

the i2c and amtel stuff is in the lg kernel source code under drivers and drive

rs/touchscreen, respectively. most of the i2c stuff is built into the linux kernel, but, i would favor this device's file, since theirs are likely to contain different addresses. i'll try to attach them.

also, there is ANOTHER file, which has it's own cmd_unlock_bootloader command, BUT, it uses 2 different static variables, which are not defined in the same file, and i can not find WHERE they are defined (did a search into all the kernel files, and could not file those vars), which suggests that functionality is THERE, to unlock the bootloader, but there's nothing calling it i don't see any thing that's calling.

i also looked through them and noticed that the *client struct is comprised of a [bus address, memory address, flags], and that client_send_cmd (that's not its actually name, i'm doing this from memory) takes that addresss, and can use it to send it a command, by adding the 2 8-bit buffers to the message packet, and i could not see for certain which or where it was adding the read/write flag into the message struct.

any way, i'll try to FIND, and then attach, the files. if i cant attach them, i'll update this post later to tell you where they are.

oh, if you're a ginux developer, you NEED to install "rpl" - that's a baaaad mofo. "apt-get install rpl" or "yum -y install rpl". it's a "search and replace, recursively" tool, but you don't HAVE to go recursive, and you don't HAVE to replace any thing - it's AWESOME for finding text within files, but you don't know WHICH files or WHERE they will be. i've use the sh*t out of that tool for years now.

examples:

# "R" = recursive
# "i" = case insensitive
# "s" = simulation (simulated search and replace - don't modify the files, just tell me which files WOULD be modified)
# "e" = parse expressions, like newlines or tabs (otherwise, it will use PLAIN text - use this if you need "\t" to match a tab and not "\\t")

$ rpl -Ris "searchtext" "replacetext" /path/to/search/from/or/path/to/single/file
replacing "xxx" with "yyy" ...
the following files would be modified if not in simulation mode:
/path/to/search/from/or/path/to/single/file.sql
/path/to/search/from/or/path/to/single/other/file.txt

$ rpl -Ri "searchtext" "replacetext" /path/to/search/from/or/path/to/single/file
2 files modified

note that if you have $ in your "search" or "replace" text, you need to use double quotes, and not single quotes. there is a difference with rpl, and i'm not sure i remember which is which, but, i think it is so that you can use shell variables in your texts - who knows - just remember that there are a few characters that f*ck up your game if you dont use the right quotes with them. pay attention to the first line of output "replacing 'xxx' with 'yyy' ..." - that part will tell you exactly what it's about to do - which is why i ALWAYS run a command with an "s" flag first, to make damned sure what it's going to do, and what files are replaced (it never tells you which files are modified unless you are in "simulation mode" with the "s" flag) - so get in the habit of using the "s" flag with every command, to cover your ass, and then removing it to actually run the command.

oh, and, if you use KDE, you can do a search without rpl, right from the file manager (dolphin) via [ctrl][f] ;)