Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,730,444 Members 44,261 Now Online
XDA Developers Android and Mobile Development Forum

[Test][Kernel] -fox 2.6.27 kernel for RHOD Only!

Tip us?
 
Starfox
Old
(Last edited by Starfox; 20th August 2011 at 06:29 PM.)
#1  
Senior Member - OP
Thanks Meter 88
Posts: 257
Join Date: Jun 2007

 
DONATE TO ME
Default [Test][Kernel] -fox 2.6.27 kernel for RHOD Only!

I pulled the latest kernel tarball, fixed and tweaked a few things, then compiled it on my Rhodium. Although it works well on my Rhodium, I cannot guarantee that it will work on yours. In addition, it is guaranteed NOT to work on any other since I disabled support for it in .config.

You can install this kernel just like the one you would off the autobuild. The kernel is named -fox-YYDDMM where the date is when I pulled the tarball. While suggestions and feature request are welcome, it takes me ~2.5hr to go through one compile, so don't expect a new build very often.

You need the patched haret.exe as well as an additional line in startup.txt to boot this kernel. Instructions for that can be found at http://forum.xda-developers.com/show...08&postcount=1.

Latest (8/20) at http://db.tt/OeRyLYu

Changelog:

8/20 http://db.tt/OeRyLYu
microp: Upstream version of LED patch from Detule. Please note the requirement of updated lights.msm7k.so still applies.

8/16 http://db.tt/3UWBs3y
microp: Updated microp LED patch from Detule, now with more blinkenlights goodness (and yes, it even blinks). In order to use this, however, you need an updated liblights from http://db.tt/ZUjymT9. The file should be bind-mounted on startup in your froyo.user.conf, ie: mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so

8/15
microp: Proposed LED patch from Detule, mailing list has instruction on how to play with the blinkenlights.
.config:
Enabled IP_NF_TARGET_REDIRECT as a module because it's needed for certain app.
Started from clean source to get rid of any residuals.

8/11
Compcache: Included 0.5.4, patched kernel to support the swap notify
clock-wince: Added a debug output that shows freq requested, closest set, and the calc, without needing clock_wince.debug_mask=15.
.config notes:
LZOCOMPRESS/DECOMPRESS is built-in to the kernel. Therefore if you want compcache, you just need to insmod xvmalloc.ko and ramzswap.ko.

8/9
Upstream: htc_headset_microp fix
acpuclock: Changed turbo mode+20mhz only when acpuclock.force_turbo=2 is set. Also, overclock by 20mhz for any bus speed >100MHz.
modules: Use strip --strip-unneeded.

8/6
acpuclock: Change turbo mode t->axiclk_khz from 160000 to 180000. AXI clock control the bus freq, and upping it should make overall performance better.
clock-wince: Add supposed support for 48Mhz SD clock from .35. HOWEVER the kernel claims calc_freq is 61.44Mhz according to clock_wince.debug_mask=15. You also need to add msmsdcc_fmax=48000000 in order to use this clock anyway.
proc_comm_wince: Fix long-standing issue with msm_proc_comm_wince_pending_ints & DEX_INT_VBUS check which clobbered pending_int. You should no longer have a SoD during transition changes to/from suspending while inserting/removing the USB cable.
microp-k*: Got rid of the printk spam of backlight/keyled status changes.
.config changes:
1) Change default I/O scheduler to deadline. Our kernel does not do well with noop.
2) Change default AMSS firmware interface to 6125 which is what I have on my RHOD400. You can check yours (which is in the modem) by running dmesg | grep AMSS.
3) Change kernel default sleep_mode from CONFIG_MSM7X00A_SLEEP_MODE_POWER_COLLAPSE_SUSPEND to POWER_COLLAPSE. This is usually overridden but makes pm.sleep_mode=1 unnecessary.
4) Change CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN from 128MHz to 112Mhz. This meant that the kernel never used the 112MHz clock because it was below the ondemand minimum. No-frills CPU can confirm this.
5) arm6k support enabled. Not sure if it makes a difference but the kernel hasn't complained.
6) Conservative and Powersave governor enabled.
7) CONFIG_INPUT_TABLET disabled, nothing was enabled in there anyway and ours uses TOUCHSCREEN.
8) CONFIG_USB_ANDROID_RNDIS_WCEIS enabled, supposedly makes Windows think it's dealing with a NDIS ICS device.
9) Enabled ext4 and disabled yaffs2. Ted T'so backported fixes for ext4 for .27 release. This contains all the patches available on his ext4 git for the 2.6.27 kernel, but still should be considered EXPERIMENTAL.

GPL availability notice:
kernel source as available from http://gitorious.org/linux-on-qualco...htc-msm-2.6.27
compcache module+patch from http://code.google.com/p/compcache/d...e-0.5.4.tar.gz
.config used to compile available from within /proc/config.gz
Minor patches to the kernel source can be made against the git tree upon request. Please PM me if you are in need of that.

-- Starfox
The Following 5 Users Say Thank You to Starfox For This Useful Post: [ Click to Expand ]
 
gro▀a
Old
(Last edited by gro▀a; 7th August 2011 at 09:18 PM.)
#2  
Senior Member
Thanks Meter 21
Posts: 147
Join Date: Sep 2009
Hmm haret freezes with your kernel on my rhod100_de.
(pm.sleep_mode=1 is deleted in startup.txt / no difference with pm.sleep_mode=1 not deleted)
GT-i9100 | SlimBean latest | DorimanX latest | modem XXMS2

Protou | stock ROM | Infinity kernel
 
Starfox
Old
#3  
Senior Member - OP
Thanks Meter 88
Posts: 257
Join Date: Jun 2007

 
DONATE TO ME
Put sleep_mode back, and if it still doesn't boot, it's possible that the axi bus is too high. I'm looking to make it a kernel parameter in the next compile.

-- Starfox
The Following User Says Thank You to Starfox For This Useful Post: [ Click to Expand ]
 
arrrghhh
Old
#4  
Retired Forum Moderator / Recognized Developer
Thanks Meter 3371
Posts: 11,036
Join Date: Feb 2007

 
DONATE TO ME
So far so good.

Couple of things - first, it seems you didn't strip the modules...? There's no way they should be 7+mb .

Second, of all the things you've put in this kernel, one really stood out to me:

Quote:
Originally Posted by Starfox
proc_comm_wince: Fix long-standing issue with msm_proc_comm_wince_pending_ints & DEX_INT_VBUS check which clobbered pending_int. You should no longer have a SoD during transition changes to/from suspending while inserting/removing the USB cable.
If that's true ^^ (and works) why not submit a patch to mainline? Or is this your testbed for patch submission?

Good work, I'll see what I can make blow up. Only just booted... doesn't seem faster, but it's still settling methinks.
 
Starfox
Old
(Last edited by Starfox; 11th August 2011 at 06:14 PM.)
#5  
Senior Member - OP
Thanks Meter 88
Posts: 257
Join Date: Jun 2007

 
DONATE TO ME
Please use the posted kernel/modules combo from the OP. I support 2 most recent revisions.

-- Starfox
 
anish88
Old
#6  
Senior Member
Thanks Meter 5
Posts: 129
Join Date: Mar 2008
i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?
 
arrrghhh
Old
#7  
Retired Forum Moderator / Recognized Developer
Thanks Meter 3371
Posts: 11,036
Join Date: Feb 2007

 
DONATE TO ME
Quote:
Originally Posted by anish88 View Post
i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?
What device, build?
 
anish88
Old
(Last edited by anish88; 8th August 2011 at 12:39 AM.)
#8  
Senior Member
Thanks Meter 5
Posts: 129
Join Date: Mar 2008
Rhod400, frx07

maybe a sample of the startup.txt would be appreciated too

also where am i suppossed to put msmsdcc_fmax=48000000 maybe im putting it in the wrong spot?
 
odz
Old
#9  
Member
Thanks Meter 17
Posts: 67
Join Date: Feb 2007
Running 8/6 here on rhod400. It seems just a tad bit faster/smoother.
 
arrrghhh
Old
#10  
Retired Forum Moderator / Recognized Developer
Thanks Meter 3371
Posts: 11,036
Join Date: Feb 2007

 
DONATE TO ME
Quote:
Originally Posted by anish88 View Post
Rhod400, frx07

maybe a sample of the startup.txt would be appreciated too

also where am i suppossed to put msmsdcc_fmax=48000000 maybe im putting it in the wrong spot?
Did you just assume where the msmsdcc command goes? lol.

It goes in the "cmdline" between the quotes - where pm.sleep_mode is, etc. Make sure there's at least one space between each entry.

I'd imagine that's your issue, as I have the same phone/build and it works great for me.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes