yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] k4mik4z:
can someone mirror the kernel it in other filehost the download linking isnt loading..probably due to over load...

if its fine with hillbeast thankyou...

im just a lurker following but great work man..definiteyl checking it out..
[Samsung Galaxy SL i9003] djynns:
First of all, thanks for your effort

I downloaded your kernel but I have a question

In other message you said that Linaro seemed not compatible whith our phone but now you say that one of your few tweaks is Linaro compiled.

So, Linaro is now compatible with our phone?

In this case, this does mean that de battery life will be increased with your kernel?

Thanks again
[Samsung Galaxy SL i9003] ynshetty:
@djynns yes he has compiled it using linaro;linaro is a tool chain that is used to compile stuff;It tweaks the android to improve PERFORMANCE without compromising battery life....please Google ur queries before posting it here

Thank u :)
[Samsung Galaxy SL i9003] marshygeek:
i think he sound like this "when will it be?.. the kernel 3.0?" he asks when will 3.0 be ok. :)
[Samsung Galaxy SL i9003] k4mik4z:
ok i tried the "gingerbread kernel"

its buggy..theres this command line interface coming up when you boot just after samsung logo..showing some errors ? i dont know..

but it boots anyway..

may be you might have enabled it by default..i wonder..

and it has some problem waking up after locking

for eg: if you lock screen while playing music..when you press the power button or home

just the backlight lights up nothing else..the music keeps playing though

sorry no log cat since i use the phone daily ..i immediately flashed back bam kernel as the bug persisted after rebooting twice..

other wise i didnt see much improvement..thought temple run ran a bit better..

still spoiled my runs though :(

keep up the work man
[Samsung Galaxy SL i9003] jayharper08:
Guys, I just deleted 40 posts of clutter that were not at all Development related. Keep the "OMG Thank you" and "I can't wait!" comments for the discussion thread. This is DEV ONLY!
[Samsung Galaxy SL i9003] hillbeast:
I put that there. That's a debug console for me. They aren't errors, just information.
[Samsung Galaxy SL i9003] methril:
Hi hillbeast,

count me in.

@dhiru, did you rebase against omap3-3.0 branch?

I tryied to port a clean board to omap-3.0, but it's plenty of OMAP4 commits that breaks omap3 board. I'm sad about this because we couldn't upgrade to kernel 3.4 & above till the omap3 get merged to the linux kernel.

BTW, hillbeast, could you put the resistors values on the front page? Iḿ going to buy some resistors & miniUSB-A connector next week :)

See u soon.
[Samsung Galaxy SL i9003] hillbeast:
http://xdaforums.com/showthread.php?t=1713404 <- details for UART
[Samsung Galaxy SL i9003] crackerizer:
Hello Hillbeast,

I have add initial mach code for latona based on Zoom board (sent a pull request). I'm now initially customizing the codes using some info from Samsung 2.6 kernel. I'm wondering whether we should port the LCD panel driver or writing a new one. I also customize the local defconfig file specifically for OMAP3 soc (removed OMAP2 & 4 dependencies), in case you need this, I'll commit it to the branch.
[Samsung Galaxy SL i9003] hillbeast:
I will merge it when I get home. Have been sick for the last two days and having to work and its drained all my energy.
[Samsung Galaxy SL i9003] methril:
Communication

Hi guys, i don't know how much free time for working on the project, but we could met from time to time on IRC freenode @ #i9003-ics or #teamhacksung for commenting some dev issues.
[Samsung Galaxy SL i9003] crackerizer:
I'm rewriting the LCD panel driver and looking for NT35510 (LCD controller) datasheet.

Googled for it but can not find one. I found out that lot of codes from Samsung does not make sense to me. If you have it, please share. :cowboy:
[Samsung Galaxy SL i9003] frapeti:
NT35510 (LCD controller) datasheet

Dont't know if it's really usefull but maybe you want to take a look

http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDMxNDI=

---------- Post added at 02:29 PM ---------- Previous post was at 01:39 PM ----------

found it :p

http://www.mediafire.com/?mh38lmkv96262gi
[Samsung Galaxy SL i9003] crackerizer:
Ahh, Thank you for the datasheet. It led me out of misery!! :D
[Samsung Galaxy SL i9003] hillbeast:
Right so after a bit of poking around, I've been trying to figure out what the exact device is that external UART uses. It's really frustrating not knowing this because it means I can't figure out why there is no output (or at least legible output after the UART drivers start), so I tried sending 'hi' to ttyS0, S1 and S2, and nothing came up, so I assumed that they must be locked or something. I then noticed after doing that, nothing was coming up on the UART at all. Before, I would get all sorts of garbage, but after that, I got nothing. I then tried one by one to see which device did this, and I found it was ttyS2: after sending 'hi' to ttyS2, it would stop showing stuff on the UART. This told me that external UART must be connected to ttyS2.

Now I then tan stty -F /dev/ttyS2 (to find the tty settings for this port), and got this output:

speed 9600 baud;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V;
flush = ^O; min = 1; time = 0;
-brkint -imaxbel

That first line, speed 9600 baud is a problem for me, as it should be 115200. I'm going to do more testing and see if it is outputting at 9600.

EDIT: Nope. Changing PuTTY to baud 9600 still shows garbage:

¨Ôþ°üýxÍùøXýñ±¥õÔþýMþå±¡ÈÙÑ°ÑéÀÙi
ÐuÑÕ´üÔôÐÜ´ÀôÜ©Ñ ùªô(üÌù,Äü ÜÅuðÜå
øà°ù¡ùý ùåñ¤@è*EÐiáÅüÑôÐ&ôåå¤Ì ÝðØ*ñÿÄÿÁÀÐÀøüù
-Å©E*ÅùÔqÄÿYÕÀÁý±ÿ±ØôÀôÑôÑðÀôÑüÀøÑøÀøÑüÀøÀøÑøµÐø©ð¹ÌùÝôåþé°ÀñÜÑø½è*ÐÅ
ÿùøýõÈðýñÑØá*µÙñð´¦ÑÐØá°aÕáÑýÉØÐuÁÑ_´)Ôô
Üù¬üýÑØåýáÁØñ*¡Éññ¡_ÑÐÑÉÍÐ
Ø¾àyÐõ
Ø
ùµþ(,¨ý`
[Samsung Galaxy SL i9003] hillbeast:
YES! SUCCESS! By forcing the boot command line to 'console=ttyS2,115200' I managed to get to the UART console. This is much more useful than just like 20 lines of output then nothing. However, there is a problem with this: with this change, I don't have the normal commands coming through and they are important. They set stuff like the framebuffer RAM, what bootmode to be using, etc. Without that, the phone is kind of a rock.

I will see if I can backport the function from newer kernels that allows you to combine the provided commands from the bootloader with your own commands.
[Samsung Galaxy SL i9003] hillbeast:
Okay so I backported the new CMDLINE functions from kernel 3.x and it works sweet. Great to FINALLY see a proper UART output on this device. I need to make a few touch-ups, namely to giving UART console root access. And I need to charge the phone up... I haven't charged it all weekend and the battery is really flat.
[Samsung Galaxy SL i9003] anuraagkochar:
u mean 3.0 kernel is booting now ??
[Samsung Galaxy SL i9003] shriom_manerker:
AMAZING :D congratulations !!!!! cant believe kernel 3.x is so close now :D all the best :)
[Samsung Galaxy SL i9003] hillbeast:
No, but it does mean I know what settings I should be putting into kernel 3.0.
[Samsung Galaxy SL i9003] emptyragnarok:
Great Work bro :-)

Great work Man!! Congrats for your dedication and hard work!! Salute from bottom of heart :)
[Samsung Galaxy SL i9003] crazbanditz:
Hmmm... Is it possible to compile Linaro optimizations along? Not Linaro Toolchain.
[Samsung Galaxy SL i9003] hillbeast:
Well the thing is, what we are making here is basically a new stock kernel. It won't support overclocking, it won't have any fancy bits and pieces, it'll just be what is needed for daily usage. All these sorts of things are more tweaks which kernel developers and ROM cookers can add themselves once this is done. Those are not really priorities.

Down the road, some of this phones ROM cookers (I'm not familiar with who are all the kernel developers, only really know of Vurrut and Bam. sorry that I didn't mention anyone else, I haven't been in this community long and only mentioned the custom kernels I've used) can do those sorts of things.
[Samsung Galaxy SL i9003] crazbanditz:
Okay I think I understand now... Sorry if I am abit slow. :)
[Samsung Galaxy SL i9003] anuraagkochar:
You mean there wont be any overclocking in the kernel ?
[Samsung Galaxy SL i9003] crazbanditz:
Yes, its just stock kernel. We would have to wait for others to build a kernel with 3.x kernel base and tweaks such as OC.

Press Thanks if I helped :)
[Samsung Galaxy SL i9003] marshygeek:
I can feel it.. :) a new era for i9003 after the release of stock kernel 3.x :))
[Samsung Galaxy SL i9003] Adi_Pat:
Waiting to compile stock 3.0.y kernel! Nice work congrats!
[Samsung Galaxy SL i9003] TheDarkLord1997:
Hilibeast Already said that there will be no overclocking..... Please read the thread before posting

Please post all this on the discussion thread and keep the development thread clean
[Samsung Galaxy SL i9003] anuraagkochar:
So can vurrut or uc team can take 3.0 as base and put oc /uc/uv cpu and other fancy feauters ?
[Samsung Galaxy SL i9003] bscraze:
Yes after stock 3.x has been released. It has been mentioned.

Cheers:)

Sent from my GT-i9003 with Vurrut's AOKP Rom!
[Samsung Galaxy SL i9003] hillbeast:
Yes. Once the solid base is complete and stable enough, I encourage the kernel developers to do their work on it. I might make my own kernel on it too (Kyorakernel) if I feel like it. People usually liked my Kyorakernel on G3.
[Samsung Galaxy SL i9003] crazbanditz:
Hope u do work on ur kernel for our community. Thanks :)
[Samsung Galaxy SL i9003] crackerizer:
์Nice to hear that :D. I just finished rewriting the panel's driver today. Still need a little clean up. Hopefully, we will be able to compile and debug the kernel soon. ;)
[Samsung Galaxy SL i9003] TheDarkLord1997:
Surely i would love a kyorakernel for the i9003..... A kyorarom could do as well(if you feel like) :)
[Samsung Galaxy SL i9003] Wahaha123:
Exellent Work!

This is exellent news. we are very close to experience ICS on this wonderful phone... as well as rubbing this to samsung's faces, that they were wrong about this phone being uncompatible to ics... :)
[Samsung Galaxy SL i9003] frapeti:
Ics? It will be compatible with jelly bean and cm10 :D :D :D
[Samsung Galaxy SL i9003] hillbeast:
So I was just identifying what all the partitions on the OneNAND are (BML/TFSR) and this is what I have concluded is the partition structure of the device:

bml0	onenand
bml1	PBL
bml2	pit?
bml3	stl3	efs
bml4	SBL
bml5	SBL Backup?
bml6	stl6	.lfs
bml7	kernel
bml8	recovery
bml9	stl9	system
bml10	stl10	dbdata
bml11	stl11	cache
bml12	blank 512KB partition
bml13	modem

Interestingly, I found two blank partitions: bml8 and bml12. I assume bml8 was going to be the recovery partition (which Samsung don't use despite allocating 8MB for it, the exact size of the kernel, hence why I believe it is recovery), but I'm not sure what bml12 is. Seeing it's only 512KB, it can't really be used for anything. Perhaps you could hide one porn JPEG in there? I dunno, but it's a blank partition anyway.

The good thing is that the partitions that I need to play with (system and cache) are all clustered together and it means I can adjust the size of, for example dbdata and cache to give more room to /system or something along those lines, and also take advantage of the mystery partition and allocate it to something. This is the advantage of using MTD over STL/BML/TFSR, and it's also part of the reason we won't be able to use ODIN: the partition layout will be different.

EDIT: Also, bml4 and 5, they both contain the SBL, but it's two different versions of it. I assume that one is a backup version should the first one fail. I would test that but don't want to brick the phone so I won't. If someone has a phone with a smashed screen or something though then I could test my theory on that.

EDIT 2: What is DBDATA for?
[Samsung Galaxy SL i9003] alfrix:
if you choose MTD, will it be YAFFS2 or UBIFS?
[Samsung Galaxy SL i9003] hillbeast:
I haven't decided yet. I will most likely implement my fsdetect system from the Galaxy 3.
[Samsung Galaxy SL i9003] frapeti:
DBDATA is for data bases such as SMS, MMS
[Samsung Galaxy SL i9003] hillbeast:
Might as well get rid of that partition. Its not on any other Samsung device I've dealt with. Might as well give system or cache an extra 60MB.
[Samsung Galaxy SL i9003] dhiru1602:
/dbdata is faster and hence all the application databases are stored there. Getting rid of it would be a bad idea.
[Samsung Galaxy SL i9003] Skander1998:
I think the Galaxy S i9000/Captivate have it too, SMS/MMS/Contacts/Call History etc.
[Samsung Galaxy SL i9003] crk1995:
I would suggest u to add lil more memory to internal sdcard of the phone..
[Samsung Galaxy SL i9003] Silentkiller101197:
+1 for that :D
[Samsung Galaxy SL i9003] hillbeast:
Does DBDATA even get used in CM9? It seems to me to be a Samsung only feature. I'm probably wrong on that, but it seems kind of redundant. The OneNAND isn't that much faster than an MMC chip. It only seems to hold databases for Samsung applications. I just edited the init.rc to not mount it and all it lost was Samsung application data. My Google data and all that was still there.

If that's all it holds then it might as well go on the MMC partition. Even using that space for swap would be more beneficial to the system.

I can't. It's a different chip. There are two NANDs inside this phone: the OneNAND which holds system, cache and dbdata, and all the boot stuff like bootloaders and kernels, and then there is the eMMC which holds data and the internal SD card.

Really I think this 60MB is best used for something other than application databases.
[Samsung Galaxy SL i9003] arindammanidas:
60 mb of swap space is a good idea! :)
[Samsung Galaxy SL i9003] o0Arthas0o:
@hillbeasy can this kernel works in Jelly Bean?
[Samsung Galaxy SL i9003] Skander1998:
Ask such questions in the discussion thread.

And the answer is probably yes.
[Samsung Galaxy SL i9003] hillbeast:
I don't know. Google haven't released the source code for it yet, and only the Nexus will get it for starters, and it may be a few months before the source is released. Once I see people talking about it on their Nexus then I will look into what kernel it uses, but most likely it'll be 3.0, 3.1, 3.2 or 3.3.
[Samsung Galaxy SL i9003] Mamica:
only our phone will have kernel 3.0??:cyclops:
[Samsung Galaxy SL i9003] Skander1998:
Most phones that have CM9 have it already.

Ask such questions in the discussion thread.
[Samsung Galaxy SL i9003] Mamica:
when kernel 3.x will be ready? :D
[Samsung Galaxy SL i9003] loneagl:
Be ready for a lashing from the devs:p

Swyped from my RemICS powered sl
[Samsung Galaxy SL i9003] hpog:
Mamica, dude, you're doing it again. Dont ask for ETAs. Just give the devs space to work. It will come. There's a discussion thread for 3.x in gen section. Ask there if you're enjoying yourself. But dont spam here with your one liners...
[Samsung Galaxy SL i9003] crackerizer:
One question, what is the .lfs partition? It is a j4fs partition contain some images used by samsung (I guess). I tried to convert it to ext4 but the phone didn't even show samsung logo at boot. Edit the init script not to mount it seems to be ok, however. :confused:

Anyway, JB is awesome. Hopefully, It will get to this phone.
[Samsung Galaxy SL i9003] samisax:
Ah man you really have a twisted sense of humor. Torturing people with these questions that you know have no answers. I don't think anyone realizes how funny you are.

People, we need to understand that he's joking. Don't bash this comedian. He's a genius. He's an artist.

Bravo!
[Samsung Galaxy SL i9003] rockyseenu:
By the look of the Nexus threads - it looks like the kernel version is 3.0 only :good:
[Samsung Galaxy SL i9003] jayharper08:
I don't want to see anymore off topic discussion in this thread.

If you ask for eta you will get an infraction. Period.

I will be on here later to clean up the mess. First and final warning.

---Jay--- From the Nexus
[Samsung Galaxy SL i9003] hillbeast:
Cheers. And in addition, if people ask these sorts of questions I have already answered a million times, just ignore it. Less mess for the mods to clean up, and less chatter for me to read through. I do actually read every single post on every thread I created.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] hillbeast:
Not surprising. JB is more a fix up version, kind of like Windows 7 was to Vista. Not really there to revolutionise Android, just speed it up.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] Adi_Pat:
Galaxy Nexus w/ Jelly Bean came with 3.0.33 Kernel. So I guess with stable CM9 / ICS and compatible kernel.. JB shud be possible,,
[Samsung Galaxy SL i9003] crackerizer:
I got a trouble and need help. I previously converted the efs partition to ext4 which was working good. The problem is, I have to edit the init script to mount the efs partition as ext4 everytime I reflash a firmware. Could somebody here create an image of efs in rfs for me to download? Thank you in advance.
[Samsung Galaxy SL i9003] hillbeast:
Um... you realise that if someone gives you their efs, they are giving you their IMEI number,right? It's really not a good idea for someone to hand out their IMEI on the internet.

Also why did you convert efs for?
[Samsung Galaxy SL i9003] crackerizer:
That is true, my fault, I forgot to do an image backup. Is there any way I can create an rfs partition? I did convert it because I want to get rid of RFS support in the new kernel. EFS is the only RFS partition left using RFS. :eek:

---------- Post added at 06:56 PM ---------- Previous post was at 06:33 PM ----------

I forgot to mention one thing, dhiru1602's CyanogenMod 9 does not use /dbdata partition (it is left blank). So, we probably use this space for other purposes.
[Samsung Galaxy SL i9003] hillbeast:
I would make a tarball of efs, and then format it as vfat and mount as rfs, then extract the tarball.

As for dbdata, that is what I suspected. I see no difference in performance from using a symlink to /data/dbdata that I did.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] crackerizer:
Thanks for the hint ;). I forgot the fact that rfs is based on fat.

EDIT: Tried it and didn't work. My options are now edit the init script or find a blank efs partition image, if somebody would create that for me. :(
[Samsung Galaxy SL i9003] hillbeast:
I will try making an image tonight and delete the files so it will just be a blank rfs formatted partition.

When I make kernel 3, I will use virtual efs, so I will just mount an image of the efs partition stored somewhere like the internal SD card or maybe one of the blank partitions that way the old efs doesn't get harmed.

Probably you shouldn't have jumped ahead of yourself and formatted it.

Sent from my Serenity Galaxy S2
[Samsung Galaxy SL i9003] cdesai:
Better make a new partition (like on the Aries / epic / p1) and mount it as efs, leaving the original partition untouched.

That if you ever get to porting MTD :-)

We use a script to do the initial migration (updater.sh in p1-common device, at github.com/CyanogenMod)
[Samsung Galaxy SL i9003] dhiru1602:
Maybe we need to concentrate on getting the kernel booting on the latona board. If it does, I could jump into the driver porting because atleast I would have something to work with and I could help you guys.
[Samsung Galaxy SL i9003] crackerizer:
I agree with you. I think the first shot we should try is after the new partition scheme and probably your ICS is ready with the new scheme. I already ported some drivers but I guess we should try to make it boot before pushing this to github.
[Samsung Galaxy SL i9003] hillbeast:
I'm currently just going through board-latona.c from top to bottom getting everything right. It's not that I'm jumping back and forth, I just want all of board-latona.c there.
[Samsung Galaxy SL i9003] anuraagkochar:
@Hillbeast

This might help you

http://xdaforums.com/showthread.php?t=1546102
[Samsung Galaxy SL i9003] hillbeast:
That's what I'm already using.
[Samsung Galaxy SL i9003] dhiru1602:
Development for 3.0 Kernel

Okay guys, I have been getting a lot of PMs and mails about the 3.0 kernel about what is the progress, who is working on it and how could they join the development. Hence, I wanted to take the initiative to put forth a development plan so that we could share the work equally and speed up the development.

The development process will consists of the following milestones.

Milestone - 1 (Low Level Development - Needs UART)

Objective: Get the OMAPZOOM kernel to boot on the Latona board.

Contents:

Implement a Partitioning system - Mostly MTD/YAFFS

Port over board data with reference to zoom2 board data that is already present in the 3.0 kernel.

Get the MMC to work so that developers without external UART logging are able to access the log data via adb.

Developers:

hillbeast

Milestone - 2

Objective: Implement Device specific device drivers and GPIOs.

Contents:

Work on the Panel and get the display system working.

Implement ATMEL Touchscreen.

Implement TWL4030 audio with MAX97000 power management.

Samsung modemctl driver (Preferably from OMAP4).

Samsung Battery driver

Sharp GP2A Proximity Sensor/Light Sensor

Bosch BMA023 Accelerometer

Orientation Support

GPS Driver

OMAP Vibrator

wl12xx Wifi driver with mac80211

wl12xx BT driver (rfkill)

Camera ISP [Fixup for new V4L2 on 3.0 kernel]

Let me know if I missed anything.

Developers:

dhiru1602,crackerizer, hillbeast,Adi_Pat, XDA_BAM*,vurrut*

(*) Haven't asked for a confirmation.

Milestone - 3

Objective: More fixes and optimizations

At this point, we could concentrate on optimizing the kernel and adding fancy stuff like governors and other tweaks.

Also, at this point, the kernel is ready for preliminary user testing.

Source Code

Basically, all our device repos are on the Teamhacksung github (The ones that I work on). I have uploaded the source from OMAPZOOM to my github account here: https://github.com/dhiru1602/android_kernel_samsung_latona

Hillbeast is working on a fork and once when he is done with the Milestone-1, His work will be added to my repo and will be made available for other developers.

Lets use this thread as a reference to plan our work. If you are willing to work on porting a driver, please notify in this thread so that the other developers are aware that there is someone working on a specific driver. Once you have tested the driver, please send back a pull request. I will test the kernel and merge it to the upstream.

Once the kernel is most functional, we will move the sources to the teamhacksung repo under a new branch.

Please be advised that since we are working on a kernel, we should be bound by GPL and we would be making all the sources public for all the changes that we make. Also, please use proper naming conventions and descriptions for commits so that other developers are aware of the change specifics.

Do let me know if you have any clarifications to make.
[Samsung Galaxy SL i9003] hillbeast:
We're not even at milestone 1. We're all waiting for me to figure out why I can't see the decompression debugging messages on UART. I just went through 20,000 lines of code differences between Samsungs kernel and the standard mainline Linux kernel 2.6.35.7 to find what they have done to UART, but I don't think I've found what I want. I know I'm getting close because it has to be in /arch/arm/boot/compressed/*, or arch/arm/mach-omap2/include/mach/debug* or arch/arm/plat-omap/include/plat/serial.h. It's one of those, and I am going through all of them, but for the next 3 days I will be busy with work so I won't be able to do much.
[Samsung Galaxy SL i9003] jayharper08:
You are a senior member and should be aware of not quoting the OP and asking for ETA's. Please don't do it again.