yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] marchusar:
Wifi N for couttstech-2.6.32.28_OC1190_HAVS@925mV_BFS_BFQ_SLQB

Hi,

is it possible to get a Wifi N patch for your kernel?

Thanks a lot.

--

Device: HTC Desire AMOLED, S-ON

Rom: 1.72.405.2 The Z ROM v0.6 A2SD+

Android: 2.2.1

Radio: 32.54.00.32U_5.14.05.17 + RIL

Kernel: 2.6.32.28 couttstech-2.6.32.28_OC1190_HAVS@925mV_BFS_BFQ_SLQB

microSDHC-Card: ADATA 16GB Class6

A2SD: 1GB
[Desire Android Development] marchusar:
Having Problems with actual version.

Quadrant closes while running 3D graphics benchmark. Don't know if there are other problems.

Going back to couttstech-2.6.32.26_OC1190_LeeDroidv2.2f_HAVS@925mV_CMBattFix_BFS_BFQ

--

Device: HTC Desire AMOLED, S-ON

Rom: 1.72.405.2 The Z ROM v0.6 A2SD+

Android: 2.2.1

Radio: 32.54.00.32U_5.14.05.17 + RIL

Kernel: 2.6.32.27-froyo-bravoV5-couttstech.com HAVS@925mV_CMBattFix_BFS_BFQ

microSDHC-Card: ADATA 16GB Class6

A2SD: 1GB
[Desire Android Development] melethron:
That is pretty sure undervolting related. What version did you use?

Quadrant also closes for me too if i run it at 1113 oc with the default 1275mV. After i changed it too 1300 mV (on 998 - 1113) it was stable. No Closes of quadrant and 15 min stresstest of setcpu doesn't freeze.
[Desire Android Development] Anakha56:
No idea what was changed after the 9th but I downloaded the 925HAVS_BFS kernel (yesterday evening @ about 20:00 South african time) again, flashed it and am having much better battery life today. Starting from 100% this morning at 5am and after many phone calls, SMS's and push email for gmail and Exchange I am now sitting on 62%. :)
[Desire Android Development] coutts99:
I'm going to change the default voltages in SVS version.

Can you send me whats stable for you please mate?
[Desire Android Development] melethron:
cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
128000: 975
245000: 1000
384000: 1025
422400: 1050
460800: 1050
499200: 1075
537600: 1075
576000: 1100
614400: 1100
652800: 1125
691200: 1150
729600: 1175
768000: 1200
806400: 1225
844800: 1250
883200: 1275
921600: 1275
960000: 1275
[COLOR="Red"] 998400: 1300
1036800: 1300
1075200: 1300
1113600: 1300[/COLOR]
1152000: 1300
1190400: 1300

I just changed the 998-1113 values to "stock voltage". This table should be stable on almost all cpu's (i doubt it can be worse than mine ;) ). Ill check voltages of latest leedroid later. Many people use that ROM and since lee changed the voltage table everytime someone had issue the voltage table of that rom should be "rock solid".
[Desire Android Development] coutts99:
Voltages altered on SVS version so should be stable for more people.

Thanks Melethron :)
[Desire Android Development] kraml:
Thanks, downloaded and trying the CFS version, hope it will stable on my phone...
[Desire Android Development] beanbean50:
battery life has improved dramatically since flashing yesterday's bfs kernel, my battery widget on full charge used to report 2 days 2 hours, now 3 days 12 hours.

I thought yeah right, but returning home from work (10 hours from start to finish) with mild usage used to drain at about 2% per hour, now it's only 1%....

....that's gonna be hard to improve some more unless you can get it down to 0% per hour?...hehe

notice the battery widget
[Desire Android Development] Terepin:
melethron, is possible to get batter life with HAVS@875mV when I use SetCPU with profile Screen off - 245MHz - powersave? Most time is my phone running in indle.
[Desire Android Development] melethron:
I have to thank you :) . Your the one who compiles kernels with all the stuff want included ;) .

In theory yes. Since the cpu clock might jump up if its on smartass/interactive/ondemand and only a tiny increase in load (from a sync etc). But it will be a bit slower on wakeup since it needs to switch scheduler/clock first so check if you can live with the tiny lags.

I myself use conservative with 128-245. This way it will stay most time on 128 (conservative jumps MUCH slower to higher clocks) and when i listen music with screen off (128 can be to slow then) it goes up to 245 if its needed.
[Desire Android Development] marchusar:
Hi,

stable was with 1190 oc: couttstech-2.6.32.26_OC1190_LeeDroidv2.2f_HAVS@925mV_CMBattFix_BFS_BFQ.zip

unstable on 1190 oc: couttstech-2.6.32.28_OC1190_HAVS@925mV_BFS_BFQ_SLQB.zip from yesterday.

Now I tried the same kernel with 245-1152 smartass scaling and it runs stable. Quadrant gives me a score of 1893 to 1939 points. I think that this is very nice.

With root-explorer I don't find the voltage-settings. Where can I change them if I want to? Only in adb?

What about my question about support for Wifi-N? Is it possible in this kernel? What do I have to do?

Thanks,

Marc

--

Device: HTC Desire

AMOLED, S-ON

Rom: 1.72.405.2 The Z ROM v0.6 A2SD+

Android: 2.2.1

Radio: 32.54.00.32U_5.14.05.17 + RIL

Kernel: 2.6.32.28 couttstech_OC1190_HAVS@925mV_BFS_BFQ_SLQB OC smartass 245-1152

microSDHC-Card: ADATA 16GB Class6

A2SD: 1GB
[Desire Android Development] spooky75:
Am I right, that files

http://mirror.couttstech.com/androi...-2.6.32.28_OC1190_HAVS@875mV_CFS_BFQ_SLQB.zip

and

http://mirror.couttstech.com/androi...-2.6.32.28_OC1190_HAVS@925mV_CFS_BFQ_SLQB.zip

was not changed since yesterday?
[Desire Android Development] fischauge69:
i need wifi-n. is it possible to built in?

thx
[Desire Android Development] ssauger:
same here, is there any solution for wifi-N with this fantastic kernel?

thx
[Desire Android Development] dj-darkside:
I have a Problem with your Kernel:

(couttstech-2.6.32.28_OC1190_HAVS@875mV_BFS_BFQ_SLQB)

With the Stock Kernel from baadnwz 1.7:

With your Kernel :(

Why is that?

Otherwise is your Kernel Top. With 998mhz i have on Quadrant 1750 Points.
[Desire Android Development] melethron:
@ coutts

Your kernel also works nice if packed in recovery. Reiserfs support .... and completly smooth :D
[Desire Android Development] theooo:
Hello guys, just tested 925 HAVS both for BFS and CFS, my impresion after doing some test with quadrant is

CFS 925 HAVS with ondemand > average ~1500

CFS 925 HAVS with smartass > average ~1600

BFS 925 HAVS with ondemand > average ~1550

BFS 925 HAVS with smartass > average ~1650-1700 (much better 3D test fps than other configuration)

Its only me or the smartass governor are better than ondemand??

Thanx dude, your kernel is awesome! :D :D
[Desire Android Development] kraml:
Follow up: still not stable with the CFS SVS kernel.....
[Desire Android Development] yukkio:
I get the same result with CFS or BFS (smartass and Aurax 8.2). So cfs and bfs have a similar performance.
[Desire Android Development] Terepin:
But with HAVS ondemand should be better, no?
[Desire Android Development] yukkio:
For me, equal.

BR.
[Desire Android Development] Ninsassin:
coutts you make amazing kernels, dont stop =D

This CFS is really smooth and can compete really well against the BFS.
[Desire Android Development] Anakha56:
Wow. Thanks for the awesome read :). It explains so much and allows me to understand the workings a little better, thank you :). I will try the default SVS + smartass option because I do feel "lag" every now and then but its not bad only happens on a few areas eg: on wake up to unlock.

I cant say it enough but one more for the road :p. Thank you melethron! :)
[Desire Android Development] Hammerhand.17:
Thanks Melethron, now I know a little bit more about kernel, but, reading you, I still have a doubt. What about CFS and BFS? What's the difference between them?
[Desire Android Development] melethron:
Not really sure. Im not into "cpu scheduler" workway. I just had the impression that BFS was slower, but my issue with BFS where most likely because of ck2 patch and swap. I want to test the non ck2 version with swap first.

From what i have read so far i think that BFS "should" be better in theory because it is made for single core cpus. The intention of con kovalis (the devs) was a sheduler for cpu's like the one used in the desire. But:

(source)

If i dont have issue with swap on the normal BFS kernel (without ck2 patch) then i use BFS if it feels the same ... simply because it has the cooler name:

"brain ****" > "completly fair" :D :D :D
[Desire Android Development] Terepin:
For me, BFS has smoother scrolling.
[Desire Android Development] Hammerhand.17:
:D :D

Thanks again, it's clar for me now.
[Desire Android Development] theooo:
Wow, Epic Explanation Sir! Very helpful to understand those governor! :D :D

But like my post on previous page, 3d performance are far better with smartass than ondemand, is this caused by those 20ms sampling??

And if smartass would not jumps to max clock everytime, would it be better with HAVS since HAVS may gave lower voltage level depending on CPU load and clock compare to SVS?

Sorry im newb to this thing, but im very interested in this. :D

Thanx Melethron!
[Desire Android Development] melethron:
Most likely the better smartass performance is because of this.

I used "adb shell /system/bin/dmesg | grep avs" to check the voltages that HAVS sets and most time the highest lvl (for the clock) was set. Really few times when the voltages was lower. Since Havs needs cpu on its own I think the benefit is negated. If there is a benefit then I didnt notice it on daily use.
[Desire Android Development] theooo:
okay, i got it. :) Thanx sir. But can you tell me maximum voltage level on every clockin havs? :D :D
[Desire Android Development] yukkio:
I think I will probe SVS version! Thanks dude!
[Desire Android Development] melethron:
Quote from git:

8 99 struct clkctl_acpu_speed acpu_vdd_tbl[] = { 100 { 19200, VOLTAGE_MIN, VOLTAGE_MIN }, 101 { 128000, VOLTAGE_MIN, VOLTAGE_MIN }, 102 { 245000, VOLTAGE_MIN, 925 }, 103 /* Remove 256 as is commented out of acpuclock-scorpion.c, this was causing setcpu to be out by one when clock to speed above this 104 { 256000, VOLTAGE_MIN, 1000 }, */ 105 { 384000, VOLTAGE_MIN, 975 }, 106 { 422400, VOLTAGE_MIN, 975 }, 107 { 460800, VOLTAGE_MIN, 1000 }, 108 { 499200, VOLTAGE_MIN, 1025 }, 109 { 537600, VOLTAGE_MIN, 1025 }, 110 { 576000, VOLTAGE_MIN, 1050 }, 111 { 614400, VOLTAGE_MIN, 1075 }, 112 { 652800, VOLTAGE_MIN, 1100 }, 113 { 691200, VOLTAGE_MIN, 1125 }, 114 { 729600, VOLTAGE_MIN, 1150 }, 115 { 768000, VOLTAGE_MIN, 1175 }, 116 { 806400, 1175, 1200 }, 117 { 844800, 1200, 1250 }, 118 { 883200, 1200, 1250 }, 119 { 921600, 1200, 1250 }, 120 { 960000, 1200, 1250 }, 121 { 998400, 1225, 1250 }, 122 #ifdef USE_OVERCLOCKING 123 { 1036800, 1225, 1275 }, 124 { 1075200, 1225, 1275 }, 125 { 1113600, 1250, 1300 }, 126 #endif 127 #ifdef USE_EXTREMEOVERCLOCKING 128 { 1152000, 1300, 1325 }, 129 { 1190400, 1300, 1325 }, 130 #endif 131 { 0 },
[Desire Android Development] Nekromantik:
im getting battery drain on alex v HD rom with CFS non HAVS kernal using smart ass :(
[Desire Android Development] theooo:
Wow, it seems on few clock HAVS got higher voltage level than SVS. And like u said before, HAVS mean more calculation than SVS, so i guess ill try SVS BFS + Smartass like your suggestion sir! :D :D Thanx again.
[Desire Android Development] coutts99:
Yes, I do need to go through and check havs voltages again :)
[Desire Android Development] melethron:
Was the quote even right? Arch/arm/board-msm?
[Desire Android Development] coutts99:
Arch arm mach-msm avs.c
[Desire Android Development] melethron:
Meant "mach" ;)
[Desire Android Development] woti23:
nice stats how long cpu is in various frequencies

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
[Desire Android Development] mobilkungen78:
i use this kernel couttstech-2.6.32.28_OC1190_CFS_BFQ_SLQB and battery life on the RCMixHD v0.15 1.72.405.3 A2SD+ Internal Core is exellent..Thanx
[Desire Android Development] melethron:
Info tab in setcpu shows it also....
[Desire Android Development] woti23:
same here, excellent battery with vdd levels customized set, powersave/ondemand gov, cfs/gcs, deadline (bfq not compiled in), a2sd+, datadata2ext4syncloopfileonext4sd, slab (slqb not compiled in) and very fast 1.72.405.3 with libsqlitepatch

vdd

128000: 925

245000: 925

384000: 925

422400: 950

460800: 950

499200: 975

537600: 1000

576000: 1000

614400: 1025

652800: 1025

691200: 1050

729600: 1075

768000: 1100

806400: 1125

844800: 1150

883200: 1175

921600: 1200

960000: 1225

998400: 1250

1036800: 1275

1075200: 1300

1113600: 1300

1152000: 1300

1190400: 1300
[Desire Android Development] melethron:
lol: datadata2ext4syncloopfileonext4sd ... make a script thats called that and add all mountoptions to it:

datadata2ext4syncloopfileonext4noatimenodiratimenosuidnodevnoautodaallocsd :D

short question about 1.72. Did you port it yourself. If yes pm me .... my 1.72 port is running nice but maybe you have some tipps for me.
[Desire Android Development] Schwarz33:
Using latest SVS_CFS build. No problem except a strange CPU clock behavior. Max CPU frequency 960 Mhz according SetCPU info page by default. :confused:
[Desire Android Development] b-george:
Here is my log from setcpu

Kernel

Linux version 2.6.32.28-ck2-froyo_bravoV5-couttstech.com (stevec@europa) (gcc version 4.4.0 (GCC) ) #38 PREEMPT Tue Jan 11 13:06:36 GMT 2011

Battery

Battery Temp: 30.0° C (86.0° F)

Battery Level: 86%

CPU

Frequency: 245000 kHz

Load Average: 1.89 6.25 9.22 1/645 6701

Processor	: ARMv7 Processor rev 2 (v7l)

BogoMIPS	: 162.54

Features	: swp half thumb fastmult vfp edsp thumbee neon

CPU implementer	: 0x51

CPU architecture: 7

CPU variant	: 0x0

CPU part	: 0x00f

CPU revision	: 2

Hardware	: bravo

Revision	: 0081

Serial	: 0000000000000000

Time in State

128000 73074

245000 410159

384000 23381

422400 354

460800 312

499200 267

537600 240

576000 174

614400 100966

652800 195

691200 157

729600 191

768000 179

806400 243

844800 100

883200 190

921600 147

960000 229

998400 418379

1036800 0

1075200 0

1113600 0

1152000 0

1190400 0

Memory

MemTotal: 425180 kB

MemFree: 45588 kB

Buffers: 220 kB

Cached: 65752 kB

SwapCached: 0 kB

Active: 190484 kB

Inactive: 140412 kB

Active(anon): 166672 kB

Inactive(anon): 115928 kB

Active(file): 23812 kB

Inactive(file): 24484 kB

Unevictable: 11208 kB

Mlocked: 10916 kB

HighTotal: 303104 kB

HighFree: 27232 kB

LowTotal: 122076 kB

LowFree: 18356 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 276132 kB

Mapped: 44768 kB

Shmem: 6468 kB

Slab: 11664 kB

SReclaimable: 3072 kB

SUnreclaim: 8592 kB

KernelStack: 5160 kB

PageTables: 17472 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 212588 kB

Committed_AS: 7737496 kB

VmallocTotal: 778240 kB

VmallocUsed: 163660 kB

VmallocChunk: 536580 kB

I don't know if it is normal, but my time in state is very hight?

I'm using desire HD port 1.72 base by baadnewz.
[Desire Android Development] woti23:
depends on your usage and your powerstate settings (setcpu, /system/bin/ssts, ....)

you have about 4/9 of time in powersave, 1/9 of time at medium freq, 4/9 at highest (not overclocked) freq
[Desire Android Development] b-george:
Ok, but why is my state is so hight @ (128000 73074) (245000 410159) (998400 418379) (384000 23381) (614400 100966)? I can see other members log as high as my log.
[Desire Android Development] woti23:
128000Mhz lowest voltage for cpu - less battery

998400 Mhz (1190400 when overclocked) - more battery

so more higher values of time in state at lower MhZ -> moer powersave, better battery

time in state = how much time cpu is running with the frequency in the left column
[Desire Android Development] b-george:
Thank you i got it now :)
[Desire Android Development] melethron:
I dont think its high. Mine is:

128000 258153
245000 257892
384000 25320
422400 2
460800 2
499200 0
537600 0
576000 1722
614400 48888
652800 12096
691200 0
729600 8803
768000 19
806400 0
844800 0
883200 0
921600 2
960000 8790
998400 193875
1036800 25887
1075200 0
1113600 130305
1152000 0
1190400 0

If i summ up that values i get: 971 756 . The times there are in 10ms (source).

So thats 9717,56 s = 161,9 min = 2h 41 min. But my phone was on for 8 h 33 min... but it was only 2h min 41 active ;) (The last 2 values can be seen in battery stats. ).

So its only counting when the phone isn't "sleeping".
[Desire Android Development] b-george:
Thank you i see you are the guru of kenels and helps many members :), nice to hear it's normal.

What is your experience in OC how much shorter is the battery life?

My battery drain is very good while the phone is on sleep mode, but when i use the browser internet it drains ~20% i a hour.
[Desire Android Development] woti23:
no, think it counts only usertime, also when sleeping (as in screen state off)

"which will mean this CPU spent <time> usertime units of time at <frequency>."
[Desire Android Development] melethron:
Im definitely not a "guru. I cant even read to source. I only look at the manuals. (RTFM you know ;) )

Never really noticed more battery drain from OC. Not sure if its only affected by voltage (1300mv for 998 and 1113 for me) or also by actuall clock. I make a stress test (100% cpu) on OC.

Hmm but i wonder than if a an app with wakelock (i have a samba server running - my phone is not in "proper sleep" most time) wouldn't count as "usertime"?!
[Desire Android Development] woti23:
"The term 'user CPU time' can be a bit misleading at first. To be clear, the total time (real CPU time) is the combination of the amount of time the CPU spends performing some action for a program and the amount of time the CPU spends performing system calls for the kernel on the program's behalf. When a program loops through an array, it is accumulating user CPU time. Conversely, when a program executes a system call such as exec or fork, it is accumulating system CPU time." (wiki unix time)
[Desire Android Development] woti23:
george clooney would say: data2whatelse ;-)
[Desire Android Development] Schwarz33:
Kernel

Linux version 2.6.32.28-froyo_bravoV5-couttstech.com (stevec@europa) (gcc version 4.4.0 (GCC) ) #39 PREEMPT Tue Jan 11 13:14:34

Time in State

128000 2

245000 441297

384000 89424

422400 10282

460800 9920

499200 7329

537600 9410

576000 9089

614400 5782

652800 7496

691200 6671

729600 5502

768000 5248

806400 4562

844800 3583

883200 3565

921600 4529

960000 343608

998400 0

1036800 0

1075200 0

1113600 0

1152000 0

1190400 0

Why only 960?

Sent from my HTC Desire
[Desire Android Development] melethron:
@ coutts: I tested the non ck2 BFS kernel you made and swap behaviour is absolutly normal as expected (and configured). This way it is (with swap enabled at least) a tiny bit faster than CFS and

MUCH

faster than BFS +ck2 .

I read a bit stuff of con kolivas and found that this patch is made for a

desktop

environment. To make some "swap out" on only 100mb Ram free may be a good on a Desktop maschine but it sucks HEAVY on a phone like the desire.

Im not sure about the other stuff the patch does so i wanted to ask you if you really think that the other things improve the behaviour on a phone. If the swap behaviour sucks that much there may be other stuff that is not intended for a phone. Im not sure if this the case on other stuff but im ABSOLUTLY sure that memory management considering swap is AWFUL.
[Desire Android Development] coutts99:
Ill compile the bfs ones without the ck patches. Will be tomorrow now though
[Desire Android Development] melethron:
Thanks again :)

I still wonder if it improves things without swap. I read some stuff and download a ck2 version and test it later with swap disabled.
[Desire Android Development] melethron:
@all:

Here is some interesting stuff from the BFS dev:

http://ck-hack.blogspot.com/2010/12/queuing-theory-and-bfs.html

Check the video he linked. From a mathematical point of view i completly aggree with him. For the same reason of queuing theory i use "deadline" scheduler for the sdcard.

Check the "supermarket" example in the video and consider this example:

The persons in the queue are of "mixed" age. And old person would need much more time to move to the outer cashiers. For this the supermarket manager uses a person to sort the queue by age. If the first (next) person in the queue is young and can move fast and the second person is old and moves slow and the cashier in the middle is free then the person (aka the IO scheduler) will let the old person go to the middle cashier first because everthing will be speed up then in a "whole".

This example applies to a normal harddisk. A normal harddisk has mechanical parts (the arm with the read/write head) that needs to seek a different position (thats called seek time). Moving the arm and go to another position on the disk is slow and consumes much time. The intention of scheduler like cfq/bfq is to minimize those seek times.

But an sd-card is no harddisk and the nand inside isn't rotating ;) . This means for the example that every person has the same speed to move to a cashier. Now sorting the queue in this case would lead to unnecessary cost for the manager (aka more cpu time but not much). And sorting them by age (still diferent age aka sectors to write to - but it dosnt matter) can lead to a delay for some persons.

EDIT: An sd-card has up to 4 internal channels (according to official specification) this means there are up to 4 "cashiers" inside the sd-card.
[Desire Android Development] woti23:
but your are talking about BFQ i/o sched not BFS, which is a cpu scheduler, that he talks about?

he talks about cpu as checkout, eg, not harddisk or sd
[Desire Android Development] Terepin:
coutts, does your kernel support BTRFS?
[Desire Android Development] coutts99:
# CONFIG_BTRFS_FS is not set
[Desire Android Development] melethron:
@ coutts: Is there a default "sleeping" profile for governor and max clock?

Of course... but my thoughts about I/O scheduler were the same.

I said: "For the same reason of

queuing theory

i use "deadline" scheduler for the sdcard."

I cant give a statement about cpu scheduling because i dont know enough of it. But from a mathematical point of view he seems to be right on this.

The reason i used "noop" as i/o sched at first that it is a simple "FIFO" (first in first out) algorithm. FIFO is not a proplem if "I" (in) is lower than "O"(out), but if the "cashiers" (aka the controller channels) aren't fast enough there might be issues. The reason is that the queue on more i/o request than the controller could handle is more like a "bulk" of people than a proper line and if the "cashiers" are to slow some people (aka I/O requests) may get "stuck" (aka dropped). This can cause slowdowns/lags.

To attend this is use "deadline". This is almost like "pulling a number" to sort the queue (with a slight difference). While "deadline" will still be FIFO in general the "pulled number" (deadline) will at least assure that no "customer" (I/O request) will be ignored (dropped). So its like FIFO for number 1-10, 11-20, 21-31,.... etc. This assures that costumer 7 will be handled before customer 2x while still giving the advantages of FIFO scheduling on a sd-card.
[Desire Android Development] Terepin:
Could you build one for me (SVS, BFS), please? I wan't to try it if it is better on my card than ReiserFS.
[Desire Android Development] melethron:
And if you are at it include JFS also please :D

BTW: if all those request stress you to much i can do it myself but my PC is broken and compiling on my laptop is so awfully slow (espacially if i "renice" to use it in the meantime)

EDIT: @Terepin: Either in "adb shell" or "Terminal emulator" do:

cat /proc/filesystems

to see the available filesystems of a kernel. Coutts has:

nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev inotifyfs
nodev devpts
reiserfs
ext3
ext2
ext4
nodev ramfs
vfat
yaffs
yaffs2

EDIT2: @Terepin: Avaritia v0.5 has a "btrfs" kernel already included. Its a slightly older SVS BFS kernel that coutts compiled for me. I attached the Kernel ("melethron.zip") in case you already flashed another one.
[Desire Android Development] Terepin:
Yeah, well, asking for kernel with Btrfs support is one thing, finding that GParted can't format Btrfs is another. Damn.
[Desire Android Development] coutts99:
Ill add btrfs and jfs