yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] arindammanidas:
The Korean optimus black variant ICS source code is out : http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGKU5900

Sent from my Samsung Galaxy SL on CyanogenMod 9 !
[Samsung Galaxy SL i9003] hillbeast:
I'll download them after work and start working on it.
[Samsung Galaxy SL i9003] cdesai:
https://github.com/CyanogenMod/lge-kernel-sniper/tree/android-omap3-3.0

:)

Sadly OMX for the p970 is closed-source, but you might wanna try those blobs.

Ping me somewhere private for a link ;)
[Samsung Galaxy SL i9003] Adi_Pat:
Downloading the source...
[Samsung Galaxy SL i9003] hillbeast:
It has come to my attention that I have had some reports laid against me for my lack of progress so I feel the need to explain myself once again to you guys.

As you should all know already, I do have a real life. I have a full time job and I have a personal life. My life isn't all development all the time, especially when my personal or work life gets busy, and when it does get busy like it is at the moment, I usually spend my spare time relaxing by playing a few games. If you look at my recent posts on the XDA, you can see I haven't done any development for probably the last two weeks, maybe even more. The biggest thing I did was my Nexus 7 720p mod, and that was a tiny little change I did which took my all of 10 minutes before I went to bed one night. It's not a matter of I am ignoring this device, or that I don't care, because it's neither of them. I actually feel guilty that I haven't put more effort into this device seeing it was a community funded device. I try where I can to help out even while I'm tired and exhausted but it's not enough.

So this is my formal apology for the lack of effort I have put into my development for everything I work on. I'll try harder to make some time for you guys.

In other news, I've downloaded the kernel 3.0 sources from the OB. I haven't had time to look through them just yet as I have been sleeping this afternoon as I was exhausted after work.
[Samsung Galaxy SL i9003] hillbeast:
Isn't patience a virtue...?

Uncompressing Linux... done, booting the kernel.
<6>Initializing cgroup subsys cpu
<5>Linux version 3.0.8+ (hillbeast@kyorabuilder-vm) (gcc version 4.4.3 (GCC) ) #Test PREEMPT Mon Sep 24 11:09:01 NZST 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: LGE Hub board
<6>Reserving 4194304 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
<6>OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
<6>SRAM: Mapped pa 0x40208000 to va 0xfe408000 size: 0x7000
<7>On node 0 totalpages: 62976
<7>free_area_init_node: node 0, pgdat c06cbb8c, node_mem_map c083f000
<7> Normal zone: 512 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 62464 pages, LIFO batch:15
<6>Clocking rate (Crystal/Core/MPU): 26.0/400/800 MHz
<6>Reprogramming SDRC clock to 400000000 Hz
<7>pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
<7>pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 62464
<5>Kernel command line: console=ttyS2,115200 videoout=omap_vout omap_vout.video1_numbuffers=6 omap_vout.vid1_static_vrfb_alloc=y omapfb.vram="0:4M" version=Sbl(1.0.0) 2011-03-21 10:46:47 androidboot.mode=jig bootmode=0 androidboot.current_panel=0
<6>PID hash table entries: 1024 (order: 0, 4096 bytes)
<6>Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>Memory: 246MB = 246MB total
<5>Memory: 238620k/238620k available, 23524k reserved, 0K highmem
<5>Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003d000 ( 212 kB)
.text : 0xc003d000 - 0xc0674d5c (6368 kB)
.data : 0xc0676000 - 0xc06cc500 ( 346 kB)
.bss : 0xc06cc524 - 0xc083ed88 (1483 kB)
<6>Preemptible hierarchical RCU implementation.
<6>NR_IRQS:410
<6>IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
<6>Total of 96 interrupts on 1 active controller
<6>OMAP clockevent source: GPTIMER1 at 32768 Hz
<6>sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
<6>Console: colour dummy device 80x30
<6>Calibrating delay loop... <c>798.24 BogoMIPS (lpj=3117056)
<6>pid_max: default: 32768 minimum: 301
<6>Mount-cache hash table entries: 512
<6>Initializing cgroup subsys debug
<6>Initializing cgroup subsys cpuacct
<6>Initializing cgroup subsys freezer
<6>CPU: Testing write buffer coherency: ok
<4>omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_core
<4>omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per
<4>omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup
<4>omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ohci
<4>omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ehci
<4>omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck.
[Samsung Galaxy SL i9003] mikef:
Thread cleaned of non-dev related posts.
[Samsung Galaxy SL i9003] Skander1998:
Some explanation on what stage we're at with this?
[Samsung Galaxy SL i9003] vseehua:
I believe it means he is able to get the UART to work properly.
[Samsung Galaxy SL i9003] samisax:
To me, that looks like kernel 3.0 booting. Cheers!

As to if it's booting properly (complete Milestone 1), I don't have the knowledge to judge. Care to clarify, Hillbeast?
[Samsung Galaxy SL i9003] hillbeast:
The device is starting to boot kernel 3.0. We can see it initialise the RAM (albeit the incorrect amount, that's an easy fix), it calibrates the delay loop (tells it how fast the processor is so it can perform timed operations), and it's starting to initialise a bunch of OMAP related hardware before it crashes. Most likely it's loading up OB addresses and interrupts which obviously won't work.

But as it stands, it's major progress.
[Samsung Galaxy SL i9003] Adi_Pat:
So our first objective here would be to port over board latona to the Optimus Black Source.. Correct? A systematic plan can make things more clear. I am ready to help out.

Thanks.
[Samsung Galaxy SL i9003] ooikaisheng529:
Count me in also. But since I dont have a UART console, I can't help much.:(
[Samsung Galaxy SL i9003] hillbeast:
Yes. Stage 2 consists of getting latona mach code on this kernel. I was touching on it last night but ran into trouble. Will try again this afternoon.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] dj_stikes:
:good: Thanks for keeping us informed
[Samsung Galaxy SL i9003] Adi_Pat:
Keep us informed about it. And let me know if any part of the work can be distributed amongst us.. Will try my best to do it.
[Samsung Galaxy SL i9003] Mamica:
found it on kernel 3.0.8 port for galaxy i9001.Don't know if it can help....

https://github.com/bhundven/android...0-ics/arch/arm/mach-s5pv210/mach-aries.c#L261
[Samsung Galaxy SL i9003] BassBlaster:
Totally different hardware - I strongly doubt it will be of any help.
[Samsung Galaxy SL i9003] Keinbockwurst:
Thats just a Github from a kernel of the Galaxy S to show the settings of the FIQ debugger. ;) That wont help this port in any way, sadly.
[Samsung Galaxy SL i9003] LoLaTiOn:
I have a friend who has a I9001 CM10 does not work very well on this device and it is a kernel 3 !!!
[Samsung Galaxy SL i9003] hillbeast:
Firstly the 9001 has a retard Qualcomm chip which shares absolutely no hardware with this phone. It might as well be an iFail its that dissimilar.

Second, we have a kernel that works. We don't need any more other devices to help us.

Sent from my Galaxy S2
[Samsung Galaxy SL i9003] ooikaisheng529:
Hillbeast, I'm sorry to tell you that I don't think Adi_Pat or me can help in this kernel due to the lack of a UART setup. I think it is better for you to get some kind of log working such as fbcon and dmesg before we can help you debug futher.
[Samsung Galaxy SL i9003] cdesai:
Have you guys looked at Android RAM console yet?

That + kexec will make debugging without UART much more easy.

Sent from my GT-P1000
[Samsung Galaxy SL i9003] hillbeast:
I can look into that once drivers actually load.
[Samsung Galaxy SL i9003] Adi_Pat:
I backported OMAP Ram Console into 2.6.35 ;) .. Dont know much about kexec though..

(Offtopic)

EDIT: @cdesai Y U No reply on fb man? :D
[Samsung Galaxy SL i9003] wrishaba:
kernel 3x optimus black

look at this

http://xdaforums.com/showthread.php?t=1907255
[Samsung Galaxy SL i9003] Adi_Pat:
1)They have working Linux 3.0

2) Once you have Linux 3.0.y you can easily apply most* upstream patches (related to 3.0 tree) from kernel.org and they will work fine.

We still don't have working Linux 3.0 .. so this is not of any use now.
[Samsung Galaxy SL i9003] crk1995:
UART guide

ignore if already known.
[Samsung Galaxy SL i9003] hillbeast:
I already have UART, but this info is good for other developers. I have provided my own information on it, but it's a little finicky getting it to work right on the SL. If you have trouble, ask me.
[Samsung Galaxy SL i9003] mikef:
Thread Cleaned

Thread cleaned. No ETA requests please. Really, people who are not directly related to this project have no reason to post in here. It is not the same as a ROM thread.

Thank you,

mf2112
[Samsung Galaxy SL i9003] hillbeast:
Thanks for cleaning the thread. I have now seen the same question asked twice by two different people that basically consist of 'how long will you be to finish kernel 3.0? We need it now!'.

Seriously there is a perfectly clear statement on the FIRST POST ON THE FIRST PAGE! I made it very clear that your posts will be removed if you are asking for ETAs. If you want to ask these questions I also made it perfectly clear that you should use the discussion thread I linked.

I will answer your questions there.
[Samsung Galaxy SL i9003] issobuddy:
@HillBeast,

I've downloaded your repo, and I saw it build using P970 defconfig. Is that uart boot log in OP using this defconfig?

I am a noob here but instead of annoying hb with ETA, better learn about kenel. At least we can value the hardwork of hb and other team. IMHO.

---------- Post added at 07:52 AM ---------- Previous post was at 07:46 AM ----------

@HillBeast,

I've downloaded your repo, and I saw it build using P970 defconfig. Is that uart boot log in OP using this defconfig?

I am a noob here but instead of annoying hb with ETA, better learn about kenel. At least we can value the hardwork of hb and other team. IMHO.
[Samsung Galaxy SL i9003] hillbeast:
I've updated the repo to use latona_defconfig. Do a git pull to update it on your end.
[Samsung Galaxy SL i9003] issobuddy:
Ah thx HB. May I suggest latest UART boot log uploaded to github so we can track against kernel build?
[Samsung Galaxy SL i9003] sachin sharma:
lol he dont hav tym to do so !!

u noe uploading log to github takes too much tym!!!!!!! so may be forget about it for couple of months
[Samsung Galaxy SL i9003] hillbeast:
I could but the problem there is that my build server is different to the computer I use for flashing and debugging (I connect into the build server remotely and compile that way rather than doing it off the same computer). I'd have to FTP the log to the server, send a GIT commit and it would get really ugly and make the GIT commit log really long and it's hard to find what changed where. I'd rather keep the changelog tidy.

It's best if I put the logs here on the XDA and then we can discuss it here using quotes.
[Samsung Galaxy SL i9003] Hetalk:
Do you have UART setup?

If no, I don't think you can do much (any?) without UART setup. There a few other experienced developers who tried and couldnt help much.

@Hillbeast ... I want to get UART setup, but am not sure what card (level convertor) to buy ... can you suggest something that would be the bare minimum board?

Or else, if you get a board schematic(layout would be better) of only the required design, I can get a few boards built and assembled, for others to use as well.
[Samsung Galaxy SL i9003] hillbeast:
Of course I have UART. It's what has helped me get this far on the SL and the G3.

A level converter like this would be suitable. It's roughly what I used in my v2 debug system I have. I cracked open a microUSB cable, attached the resistor to the ID pin, and just soldered the wires onto the end of it. I need to resolder them though and put some heat shrink on because I use it so much the wires are breaking. Either that or make a case for it.
[Samsung Galaxy SL i9003] Hetalk:
^^ If you look again, the UART message was for the other user issobuddy, who was keen on forking your repo and working on it. :D

Thanks for the link, I'll see if i can find it in India.

I was also looking for a schematic, as I got access to PCB manufacturing and assembly facilities, where I can get a few boards for less or none.
[Samsung Galaxy SL i9003] hillbeast:
Okay continuing from the last post I made, I have successfully changed it to no longer use any of LGs board code. We are now working off of the 3630SDP code and it's still booting to the same place before dying.

Reason I wanted to use different code as a base other than the LG code: 1: LGs code was ugly. It had comments all through it and really annoyed the hell out of me, and 2: It's best to base it off a development board like Samsung did than it is to base it off another phone and have random bits of LG showing up in the kernel. The kernel still has heaps of LG code through it, namely throughout the drivers, but it's cleaner than it was.
[Samsung Galaxy SL i9003] hillbeast:
So I'm looking at old logs from 2.6.35, and it has a similar message about 'cannot find clock domain blah blah blah'...

And I confirmed in the code that this error isn't an error, rather a critical warning, so it can't be killing it.

That means whatever kills it isn't telling me what it is... great... Time to dig through code like the dark ages.
[Samsung Galaxy SL i9003] Hetalk:
^^ I guess our device is still in dark ages. :D

On Topic: Do you happen to have a schematic or something for the level converter board for the UART setup?
[Samsung Galaxy SL i9003] hillbeast:
There are millions. It uses the same system as the Galaxy S.

http://xdaforums.com/showpost.php?p=10819370&postcount=1
[Samsung Galaxy SL i9003] Hetalk:
^^ I saw these drawings, these are kind of wiring diagrams to be used with the converter. I'm looking for converter board schematic. Anyway, you continue with your work. I'll look elsewhere. Thanks for trying to help.
[Samsung Galaxy SL i9003] hillbeast:
Oh okay. I don't have those. I just use the cheapo ones off eBay. They're like $2 and most come with free shipping so I can source a million of them easily. I'm too lazy to make my own circuitry, and I lack the equipment to make PCBs.
[Samsung Galaxy SL i9003] issobuddy:
hb thanks for your patience. I am looking at omap_hwmod now, not sure what I am looking for hahaha :D

BTW is it me or I don't see any debug level log while initiate omap setup?
[Samsung Galaxy SL i9003] hillbeast:
1) That's what we're already doing

2) Depends on how different the hardware is. I doubt it though. The ROM will require different libraries for handling the hardware which I know IS different, like the WiFi, and the sound device.

Not sure which line you're referring to, but some debug code doesn't always use printk (which automatically puts a timestamp or loglevel at the start), but sometimes developers don't use it for some unknown and stupid reason. It's not an issue though. I don't think the problem is with omap_hwmod though, I think there is something missing elsewhere, namely to do with l4_core and such.
[Samsung Galaxy SL i9003] hillbeast:
I'm big enough and ugly enough now to be able to tell who does and doesn't hate me, but thanks for letting me know anyway Vishal.
[Samsung Galaxy SL i9003] pratik_s:
please don't start a fight we need development and not such ugly fights.hillbeast i think the best way to stop such comments is that we get a working kernel 3.x.people here are desperate for getting 3.x kernel and which is leading to such a situation.may be any assurance or any alpha build will help to reduce such comments.we all know that you are fully capable of creating kernel 3.x for our sl.plz take my comment in a positive way.Peace :angel: :)
[Samsung Galaxy SL i9003] Adi_Pat:
@hillbeast, regarding rewrite of board code.

Completely agree with you on this! I had difficulty understanding a lot of garbage in there, way to go! (Y)

Best of Luck.
[Samsung Galaxy SL i9003] crackerizer:
It's good to see progress here. It is sad that my phone is dead (drop it and screen cracked). I'm now waiting for a replacement to arrive. Hopefully I have a working phone again so I can help. :(
[Samsung Galaxy SL i9003] karanmirchandani96:
Check out galaxy R codes.....
[Samsung Galaxy SL i9003] issobuddy:
ok hb just slowly learn debugging in phone devices ;) quite different when debugging linux kernel in PC. Btw I've sync your git and found depedencies warning and error when compile, is there something I forgot to set ?

OS: Ubuntu Precise 64

Compiler: codesourcery gcc 4.5.1

config: latona_defconfig

warning: (ARCH_OMAP4 && ARCH_VEXPRESS_CA9X4) selects ARM_ERRATA_720789 which has unmet direct dependencies (CPU_V7 && SMP)
warning: (MACH_OMAP_4430SDP && MACH_OMAP_BLAZE) selects TWL6040_VIB which has unmet direct dependencies (MISC_DEVICES && TWL6040_CODEC && ANDROID_TIMED_OUTPUT)
warning: (ARCH_OMAP4 && ARCH_VEXPRESS_CA9X4) selects ARM_ERRATA_720789 which has unmet direct dependencies (CPU_V7 && SMP)
warning: (MACH_OMAP_4430SDP && MACH_OMAP_BLAZE) selects TWL6040_VIB which has unmet direct dependencies (MISC_DEVICES && TWL6040_CODEC && ANDROID_TIMED_OUTPUT)

<...>

arch/arm/common/fiq_debugger.c: In function 'dump_irqs':
arch/arm/common/fiq_debugger.c:378:9: error: 'irq_cpustat_t' has no member named 'local_timer_irqs'
arch/arm/common/fiq_debugger.c:379:9: error: 'irq_cpustat_t' has no member named 'local_timer_irqs'
arch/arm/common/fiq_debugger.c:382:4: error: 'irq_cpustat_t' has no member named 'local_timer_irqs'
make[1]: *** [arch/arm/common/fiq_debugger.o] Error 1

<...>

arch/arm/mach-omap2/omap4-common.c: In function 'omap_l2_cache_init':
arch/arm/mach-omap2/omap4-common.c:223:3: error: implicit declaration of function 'omap4_secure_dispatcher'
arch/arm/mach-omap2/omap4-common.c: At top level:
arch/arm/mach-omap2/omap4-common.c:292:5: error: conflicting types for 'omap4_secure_dispatcher'
arch/arm/mach-omap2/omap4-common.c:223:3: note: previous implicit declaration of 'omap4_secure_dispatcher' was here
arch/arm/mach-omap2/omap4-common.c: In function 'omap4_secure_dispatcher':
arch/arm/mach-omap2/omap4-common.c:321:2: error: implicit declaration of function 'omap_smc2'
make[1]: *** [arch/arm/mach-omap2/omap4-common.o] Error 1
[Samsung Galaxy SL i9003] hillbeast:
defconfig looks broken again. Lemme fix it.

EDIT: Try now. I just pushed a commit.
[Samsung Galaxy SL i9003] issobuddy:
Ok it's compiled.
[Samsung Galaxy SL i9003] dhiru1602:
Even on the Galaxy Nexus and any OMAP device, the so called "iROM" initializes in the very early boot process. There have been many questions of how it could be helpful and I remember Adam Outler actually did a video on this.

I guess when the "iROM" failes to load a bootloader either because the bootloader is corrupt or it just fails to load, the "iROM" enumerates a USB device that could be mounted to the system and from there we could actually load a bootloader into it and force the device into download mode. This also explains why some of the users who have flashed an I9000 rom onto I9003 with bootloaders had a OMAP3630 device popping up when they connect the phone to their computer, since the incompatible bootloader might have caused the "iROM" to fail, which might have started the debugging procedure and resulted in the usb device being enumerated. I guess a user who has bricked his device this way might be able to very well restore it to working condition.

Great find!
[Samsung Galaxy SL i9003] Chris089:
Hey hillbeast,

first I have to say, that I respect your work on here. YOU are great.But there is one here at the open source community that I don't like...!

....to define information as secret. The description for OmapFlash is here on xda right now.

MOD EDIT: Link removed, explanation downthread. Thank you - mf2112

Regards

CHRIS
[Samsung Galaxy SL i9003] supergaijin:
wow, that's more detailed than the one I pm'ed him.. in that case, it can't be a problem. I disagree with keeping "secrets" as well, but you saw, just as HB said, people were eager to flash a non-working kernel just to see what would happen. for people like that, it's best to avoid complaints by not steering them to other things that they might not understand either. it's like taking baby steps before walking and running. those people wanting to flash the non-working kernel are at the baby steps (or earlier) phase, users like me would be the walkers, and the runners would be those like HB and dhiru.

in case you disagree, have you read the instructions? how many here are able to use command line proficiently? that's likely the main reason ;)

now that it's out, obviously you can ignore my PM, HB.
[Samsung Galaxy SL i9003] mhajho29:
@hillbeast

since it came from you... just want to ask something... because i have a galaxy tab P1000 and its hard bricked... and i bring it on samsung and they want me to pay for replacement of the board.. and its almost the price of the tablet.. i was thinking will this help in anyway to revive my galaxy P1000.. since it was bricked already i will try any solution... since i cant find any shop here that has Jtag to revive my tab.... thanks in advance...
[Samsung Galaxy SL i9003] Chris089:
I agree and disagree with you. You and HB are right if you don`t want all people become crazy and do some low level dev on their own. For this we have the great HB to do it. But in history I liked his way to keep guys cool. Now he becomes a little bit more unlikely to me. " WHY I DONT TELL YOU....." etc. "Porting" the Kernel is not as easy as the guys think, I know. But not to tell them isn't the right way.

@ hillbeast: stay tuned, take your time. Ignore people who don't appreciate you're great work. If you want to keep things secure don't post it.

@all: let HB continue his great work his way. Don`t ask him for eta or such.... I posted the link above so you guys can see what HB is possible to do. If you think you have to proof...do...but you will brick your phone like HB told.
[Samsung Galaxy SL i9003] vishal24387:
You should look here :)

http://xdaforums.com/showthread.php?t=1869494
[Samsung Galaxy SL i9003] hillbeast:
As I explained already I am not keeping it secret because I don't want people to have this program. I didn't make it therefore I have nothing to gain from not sharing the code. I kept it secret because I don't want flashaholics to start using this potentially very dangerous program. We are dealing with direct memory access in this program and that can cause not just bricks but fried hardware. One bad push to the wrong address could kill your phone permanently.

I don't appreciate people posting links and undermining me when I am trying to protect devices. Now if someone's phone breaks because of this they're going to blame me. Thanks.