Having difficulty applying BFS patch... - G1 Android Development

I am trying to apply the BFS patch from here:
http://ck.kolivas.org/patches/bfs/
When I try to apply it, these are the errors that I get:
[email protected]:~/Desktop/test/msm$ patch -p1 < 2.6.31-sched-bfs-222.patch
patching file Documentation/sysctl/kernel.txt
Hunk #1 succeeded at 25 (offset -2 lines).
Hunk #2 succeeded at 45 (offset -5 lines).
Hunk #3 succeeded at 167 (offset -6 lines).
Hunk #4 succeeded at 329 (offset -16 lines).
patching file fs/pipe.c
Hunk #1 succeeded at 42 with fuzz 2 (offset -36 lines).
patching file include/linux/init_task.h
Hunk #1 succeeded at 124 with fuzz 2 (offset 8 lines).
patching file include/linux/sched.h
Hunk #2 succeeded at 140 with fuzz 1 (offset -7 lines).
Hunk #3 succeeded at 152 (offset -7 lines).
Hunk #4 FAILED at 243.
Hunk #5 FAILED at 1010.
Hunk #6 succeeded at 887 (offset -139 lines).
Hunk #7 succeeded at 921 (offset -139 lines).
Hunk #8 succeeded at 984 (offset -147 lines).
Hunk #9 succeeded at 1174 (offset -182 lines).
Hunk #10 succeeded at 1449 with fuzz 1 (offset -198 lines).
2 out of 10 hunks FAILED -- saving rejects to file include/linux/sched.h.rej
patching file kernel/sched.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched.c.rej
patching file kernel/sysctl.c
Hunk #1 FAILED at 86.
Hunk #2 FAILED at 102.
Hunk #3 FAILED at 241.
Hunk #4 succeeded at 587 (offset -87 lines).
3 out of 4 hunks FAILED -- saving rejects to file kernel/sysctl.c.rej
patching file kernel/workqueue.c
Hunk #1 succeeded at 322 (offset 5 lines).
patching file kernel/sched_fair.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_fair.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_fair.c.rej
patching file kernel/sched_idletask.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_idletask.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_idletask.c.rej
patching file kernel/sched_rt.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_rt.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_rt.c.rej
patching file kernel/sched_bfs.c
patching file kernel/Makefile
Hunk #2 succeeded at 95 (offset -12 lines).
patching file kernel/kthread.c
Hunk #1 succeeded at 14 with fuzz 2 (offset -2 lines).
Hunk #2 succeeded at 179 with fuzz 1 (offset 9 lines).
patching file kernel/posix-cpu-timers.c
Hunk #1 FAILED at 249.
Hunk #2 succeeded at 466 (offset -50 lines).
Hunk #3 FAILED at 476.
Hunk #4 FAILED at 967.
Hunk #5 succeeded at 1020 (offset -13 lines).
Hunk #6 succeeded at 1028 (offset -13 lines).
Hunk #7 FAILED at 1344.
4 out of 7 hunks FAILED -- saving rejects to file kernel/posix-cpu-timers.c.rej
patching file kernel/exit.c
Hunk #1 succeeded at 122 (offset 2 lines).
Hunk #2 FAILED at 144.
1 out of 2 hunks FAILED -- saving rejects to file kernel/exit.c.rej
patching file kernel/fork.c
Hunk #1 succeeded at 1169 (offset -24 lines).
patching file mm/oom_kill.c
Hunk #1 succeeded at 333 (offset -5 lines).
patching file init/Kconfig
Hunk #1 FAILED at 441.
Hunk #2 FAILED at 505.
2 out of 2 hunks FAILED -- saving rejects to file init/Kconfig.rej
patching file kernel/delayacct.c
Hunk #1 FAILED at 127.
1 out of 1 hunk FAILED -- saving rejects to file kernel/delayacct.c.rej
patching file kernel/trace/trace.c
Hunk #1 succeeded at 160 (offset -115 lines).
patching file fs/proc/base.c
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file fs/proc/base.c.rej
patching file kernel/sched_debug.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_debug.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_debug.c.rej
patching file include/linux/ioprio.h
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file kernel/Kconfig.preempt
patching file kernel/timer.c
Hunk #1 succeeded at 973 (offset -180 lines).
Click to expand...
Click to collapse
Any ideas about what could be causing these errors?

Which ROM are you applying this to?

You have to do a lot of other stuff. Your best bet is to checkout android-2.6.29-bfs from android.git.kernel.org under experimental.

hey Cyanogen, would you mind telling me some of the specifics for the backport
Trying to test out the new BFS 310

Ok, pulled the .31 kernel from android git - apply bfs batch
All good with one error trying to figure out
patching file linux-2.6.31-bfs/kernel/posix-cpu-timers.c
Hunk #3 FAILED at 526.
Reject file info:
*************** void posix_cpu_timers_exit_group(struct
*** 526,532 ****
cleanup_timers(tsk->signal->cpu_timers,
cputime_add(tsk->utime, sig->utime),
cputime_add(tsk->stime, sig->stime),
- tsk->se.sum_exec_runtime + sig->sum_sched_runtime);
}
static void clear_dead_task(struct k_itimer *timer, union cpu_time_count now)
--- 526,532 ----
cleanup_timers(tsk->signal->cpu_timers,
cputime_add(tsk->utime, sig->utime),
cputime_add(tsk->stime, sig->stime),
+ tsk->sched_time + sig->sum_sched_runtime);
}
static void clear_dead_task(struct k_itimer *timer, union cpu_time_count now)
Going to try to compile with reject and see how it goes

Is there not a pre patched file we can just flash for 4.2.5?

Funkstar De Luxe said:
Is there not a pre patched file we can just flash for 4.2.5?
Click to expand...
Click to collapse
Compiling a patched version of AOSP experimental bfs .29 with bfs310 (versus the original 230) now

Great, hopefully it's an easy install proceedure

Anyone managed this yet? Eager to test

got bfs 311 working on 2.6.29.6. Seems to work fine.
Code:
uname -a
Linux localhost 2.6.29.6-cm42-bfs311-farmatito9 #20 PREEMPT Mon Nov 23 22:46:22 CET 2009 armv6l GNU/Linux
Code:
# dmesg | grep BFS
[ 7.187500] BFS CPU scheduler v0.311 by Con Kolivas.

farmatito said:
got bfs 311 working on 2.6.29.6. Seems to work fine.
Code:
uname -a
Linux localhost 2.6.29.6-cm42-bfs311-farmatito9 #20 PREEMPT Mon Nov 23 22:46:22 CET 2009 armv6l GNU/Linux
Code:
# dmesg | grep BFS
[ 7.187500] BFS CPU scheduler v0.311 by Con Kolivas.
Click to expand...
Click to collapse
Is there a file you can upload from your build so I can use it on mine? Or do I need to patch my own install?

I could upload the full source...but where to?
or maybe a diff but against which kernel version?
Can't figure out a solution....

Related

Having difficulty applying BFS patch...

I am trying to apply the BFS patch from here:
http://ck.kolivas.org/patches/bfs/
When I try to apply it, these are the errors that I get:
[email protected]:~/Desktop/test/msm$ patch -p1 < 2.6.31-sched-bfs-222.patch
patching file Documentation/sysctl/kernel.txt
Hunk #1 succeeded at 25 (offset -2 lines).
Hunk #2 succeeded at 45 (offset -5 lines).
Hunk #3 succeeded at 167 (offset -6 lines).
Hunk #4 succeeded at 329 (offset -16 lines).
patching file fs/pipe.c
Hunk #1 succeeded at 42 with fuzz 2 (offset -36 lines).
patching file include/linux/init_task.h
Hunk #1 succeeded at 124 with fuzz 2 (offset 8 lines).
patching file include/linux/sched.h
Hunk #2 succeeded at 140 with fuzz 1 (offset -7 lines).
Hunk #3 succeeded at 152 (offset -7 lines).
Hunk #4 FAILED at 243.
Hunk #5 FAILED at 1010.
Hunk #6 succeeded at 887 (offset -139 lines).
Hunk #7 succeeded at 921 (offset -139 lines).
Hunk #8 succeeded at 984 (offset -147 lines).
Hunk #9 succeeded at 1174 (offset -182 lines).
Hunk #10 succeeded at 1449 with fuzz 1 (offset -198 lines).
2 out of 10 hunks FAILED -- saving rejects to file include/linux/sched.h.rej
patching file kernel/sched.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched.c.rej
patching file kernel/sysctl.c
Hunk #1 FAILED at 86.
Hunk #2 FAILED at 102.
Hunk #3 FAILED at 241.
Hunk #4 succeeded at 587 (offset -87 lines).
3 out of 4 hunks FAILED -- saving rejects to file kernel/sysctl.c.rej
patching file kernel/workqueue.c
Hunk #1 succeeded at 322 (offset 5 lines).
patching file kernel/sched_fair.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_fair.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_fair.c.rej
patching file kernel/sched_idletask.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_idletask.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_idletask.c.rej
patching file kernel/sched_rt.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_rt.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_rt.c.rej
patching file kernel/sched_bfs.c
patching file kernel/Makefile
Hunk #2 succeeded at 95 (offset -12 lines).
patching file kernel/kthread.c
Hunk #1 succeeded at 14 with fuzz 2 (offset -2 lines).
Hunk #2 succeeded at 179 with fuzz 1 (offset 9 lines).
patching file kernel/posix-cpu-timers.c
Hunk #1 FAILED at 249.
Hunk #2 succeeded at 466 (offset -50 lines).
Hunk #3 FAILED at 476.
Hunk #4 FAILED at 967.
Hunk #5 succeeded at 1020 (offset -13 lines).
Hunk #6 succeeded at 1028 (offset -13 lines).
Hunk #7 FAILED at 1344.
4 out of 7 hunks FAILED -- saving rejects to file kernel/posix-cpu-timers.c.rej
patching file kernel/exit.c
Hunk #1 succeeded at 122 (offset 2 lines).
Hunk #2 FAILED at 144.
1 out of 2 hunks FAILED -- saving rejects to file kernel/exit.c.rej
patching file kernel/fork.c
Hunk #1 succeeded at 1169 (offset -24 lines).
patching file mm/oom_kill.c
Hunk #1 succeeded at 333 (offset -5 lines).
patching file init/Kconfig
Hunk #1 FAILED at 441.
Hunk #2 FAILED at 505.
2 out of 2 hunks FAILED -- saving rejects to file init/Kconfig.rej
patching file kernel/delayacct.c
Hunk #1 FAILED at 127.
1 out of 1 hunk FAILED -- saving rejects to file kernel/delayacct.c.rej
patching file kernel/trace/trace.c
Hunk #1 succeeded at 160 (offset -115 lines).
patching file fs/proc/base.c
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file fs/proc/base.c.rej
patching file kernel/sched_debug.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Patch attempted to create file kernel/sched_debug.c, which already exists.
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched_debug.c.rej
patching file include/linux/ioprio.h
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file kernel/Kconfig.preempt
patching file kernel/timer.c
Hunk #1 succeeded at 973 (offset -180 lines).
Click to expand...
Click to collapse
Any ideas about what could be causing these errors?
I'm kind of confused, shouldn't you be flashing a BFS enabled kernel?
33K said:
I'm kind of confused, shouldn't you be flashing a BFS enabled kernel?
Click to expand...
Click to collapse
I'm trying to make my own kernel with BFS.
Hotweiss, the problem with this patch is that it was made for a 2.6.31 kernel and you are trying to patch a 2.6.29 kernel.
Cyanogen had to backport it to work on 2.6.29 from 2.6.31.
So I would recommend you either ask Cyanogen for a kernel patch or back-port it yourself.
TigerTael said:
Hotweiss, the problem with this patch is that it was made for a 2.6.31 kernel and you are trying to patch a 2.6.29 kernel.
Cyanogen had to backport it to work on 2.6.29 from 2.6.31.
So I would recommend you either ask Cyanogen for a kernel patch or back-port it yourself.
Click to expand...
Click to collapse
I just downloaded the 2.6.31 kernel and it patched perfectly. I will try to patch it manually today.

USB Host For Desire S - Need Help

hi. i want to compile a kernel with usb host function for my ds
i get kernel source from htcdev and vivo-usb-host.path from here
and made some change, replace "vivo" with "saga" and "VIVO" with "SAGA" in patch file, but when i want to patch it i get some error:
Code:
[email protected]:~/Desktop/yaghoub/saga$ patch -p1 < saga-usb-host.patch
patching file arch/arm/mach-msm/andcommon.c
patching file arch/arm/mach-msm/htc_battery.c
Hunk #2 FAILED at 436.
Hunk #3 FAILED at 483.
Hunk #7 succeeded at 1856 (offset 18 lines).
2 out of 7 hunks FAILED -- saving rejects to file arch/arm/mach-msm/htc_battery.c.rej
patching file arch/arm/mach-msm/include/mach/board.h
Hunk #1 FAILED at 297.
Hunk #2 FAILED at 313.
2 out of 2 hunks FAILED -- saving rejects to file arch/arm/mach-msm/include/mach/board.h.rej
patching file arch/arm/mach-msm/include/mach/msm_hsusb.h
Hunk #1 succeeded at 194 with fuzz 1 (offset 106 lines).
patching file arch/arm/mach-msm/Makefile
Hunk #1 FAILED at 191.
1 out of 1 hunk FAILED -- saving rejects to file arch/arm/mach-msm/Makefile.rej
patching file arch/arm/mm/dma-mapping.c
patching file drivers/i2c/chips/tps65200.c
Hunk #1 succeeded at 400 with fuzz 2 (offset 82 lines).
patching file drivers/input/touchscreen/atmel.c
Hunk #1 succeeded at 1241 with fuzz 1 (offset 284 lines).
Hunk #2 succeeded at 1584 with fuzz 2 (offset 294 lines).
Hunk #3 FAILED at 1565.
1 out of 3 hunks FAILED -- saving rejects to file drivers/input/touchscreen/atmel.c.rej
patching file drivers/net/usb/asix.c
patching file drivers/net/usb/asix.h
patching file drivers/net/usb/axusbnet.c
patching file drivers/net/usb/axusbnet.h
patching file drivers/net/wireless/bcm4329_204/dhd_cdc.c
Hunk #3 succeeded at 1344 (offset 19 lines).
patching file drivers/usb/gadget/android.c
Hunk #2 succeeded at 472 (offset 47 lines).
Hunk #3 succeeded at 483 (offset 47 lines).
Hunk #4 succeeded at 604 (offset 81 lines).
Hunk #5 FAILED at 564.
Hunk #6 succeeded at 691 (offset 115 lines).
1 out of 6 hunks FAILED -- saving rejects to file drivers/usb/gadget/android.c.rej
patching file drivers/usb/gadget/f_mass_storage.c
Hunk #1 succeeded at 425 (offset 8 lines).
Hunk #2 succeeded at 3165 (offset 31 lines).
patching file drivers/usb/gadget/msm72k_udc.c
Hunk #1 succeeded at 167 (offset 6 lines).
Hunk #2 FAILED at 273.
Hunk #3 FAILED at 2748.
2 out of 3 hunks FAILED -- saving rejects to file drivers/usb/gadget/msm72k_udc.c.rej
patching file drivers/usb/host/ehci-hcd.c
patching file drivers/usb/host/ehci-msm7201.c
patching file drivers/usb/host/ehci-msm7201.h
patching file drivers/usb/host/Kconfig
patching file drivers/usb/Kconfig
patching file drivers/video/console/fbcon.c
i hope someone help me with that
and sorry for my eng
O.O i hope some of the awesome developers here help, this feature would be a really nice addition to our arsenal <3 but idk if simply doing that would do it, because:
One does not simply port an awesome feature.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(one is very bored)
zacthespack said:
(one is very bored)
Click to expand...
Click to collapse
Y U READ MY THOUGHTS!? (the ones i'm too lazy to do lmao)
Bewinxed said:
Y U READ MY THOUGHTS!? (the ones i'm too lazy to do lmao)
Click to expand...
Click to collapse
Or did you read mine
I don't think it's that simple... Need to overcome hardware limitations as the USB needs to supply enough power to the flash drive to be able to R/W data. Unless there is enough juice flowing out the micro-USB port, there isn't much you can do about this... Just my two cents... I could be wrong, but that's what I've gathered from reading about USB host functionality so far...
i'm keep working on it
enigmaamit said:
I don't think it's that simple... Need to overcome hardware limitations as the USB needs to supply enough power to the flash drive to be able to R/W data. Unless there is enough juice flowing out the micro-USB port, there isn't much you can do about this... Just my two cents... I could be wrong, but that's what I've gathered from reading about USB host functionality so far...
Click to expand...
Click to collapse
You can use usb host mode when phone is in dock station , so output power from micro usb is not a problem ... And something like dvb-t stick plugged in DS would be awesome
i tried to apply sven killing patch manually but i get this when i start compiling:
Code:
drivers/usb/host/ehci-hcd.c: In function 'ehci_hcd_init':
drivers/usb/host/ehci-hcd.c:1192: error: 'ehci_debug_root' undeclared (first use in this function)
drivers/usb/host/ehci-hcd.c:1192: error: (Each undeclared identifier is reported only once
drivers/usb/host/ehci-hcd.c:1192: error: for each function it appears in.)
drivers/usb/host/ehci-hcd.c: In function 'ehci_hcd_cleanup':
drivers/usb/host/ehci-hcd.c:1278: error: 'ehci_debug_root' undeclared (first use in this function)
make[3]: *** [drivers/usb/host/ehci-hcd.o] Error 1
make[2]: *** [drivers/usb/host] Error 2
make[2]: *** Waiting for unfinished jobs....
any idea?!
jacob73 said:
make[2]: *** Waiting for unfinished jobs....
[/CODE]
any idea?!
Click to expand...
Click to collapse
Finish the job!
sorry for this nonsense.. Could not stand it
Sent by my fingers to your head.
jacob73 said:
i tried to apply sven killing patch manually but i get this when i start compiling:
Code:
drivers/usb/host/ehci-hcd.c: In function 'ehci_hcd_init':
drivers/usb/host/ehci-hcd.c:1192: error: 'ehci_debug_root' undeclared (first use in this function)
drivers/usb/host/ehci-hcd.c:1192: error: (Each undeclared identifier is reported only once
drivers/usb/host/ehci-hcd.c:1192: error: for each function it appears in.)
drivers/usb/host/ehci-hcd.c: In function 'ehci_hcd_cleanup':
drivers/usb/host/ehci-hcd.c:1278: error: 'ehci_debug_root' undeclared (first use in this function)
make[3]: *** [drivers/usb/host/ehci-hcd.o] Error 1
make[2]: *** [drivers/usb/host] Error 2
make[2]: *** Waiting for unfinished jobs....
any idea?!
Click to expand...
Click to collapse
i fix this, but i still get error:
Code:
CC [M] drivers/usb/host/ehci-hcd.o
cc1: warnings being treated as errors
drivers/usb/host/ehci-dbg.c:44: error: 'dbg_hcs_params' defined but not used
drivers/usb/host/ehci-dbg.c:88: error: 'dbg_hcc_params' defined but not used
drivers/usb/host/ehci-hub.c:109: error: 'ehci_adjust_port_wakeup_flags' defined but not used
drivers/usb/host/ehci-q.c:146: error: 'ehci_clear_tt_buffer_complete' defined but not used
drivers/usb/host/ehci-hcd.c:614: error: 'ehci_run' defined but not used
drivers/usb/host/ehci-hcd.c:1048: error: 'ehci_endpoint_reset' defined but not used
make[3]: *** [drivers/usb/host/ehci-hcd.o] Error 1
make[2]: *** [drivers/usb/host] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2
jacob73 said:
i fix this, but i still get error:
Code:
CC [M] drivers/usb/host/ehci-hcd.o
cc1: warnings being treated as errors
drivers/usb/host/ehci-dbg.c:44: error: 'dbg_hcs_params' defined but not used
drivers/usb/host/ehci-dbg.c:88: error: 'dbg_hcc_params' defined but not used
drivers/usb/host/ehci-hub.c:109: error: 'ehci_adjust_port_wakeup_flags' defined but not used
drivers/usb/host/ehci-q.c:146: error: 'ehci_clear_tt_buffer_complete' defined but not used
drivers/usb/host/ehci-hcd.c:614: error: 'ehci_run' defined but not used
drivers/usb/host/ehci-hcd.c:1048: error: 'ehci_endpoint_reset' defined but not used
make[3]: *** [drivers/usb/host/ehci-hcd.o] Error 1
make[2]: *** [drivers/usb/host] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
Did you see this?
http://forum.xda-developers.com/showthread.php?t=1468531
Anybody can confirm it working? i would advice you to try asking this in another thread that has USB host working on an HTC device, maybe they can help you better?
Bewinxed said:
Did you see this?
http://forum.xda-developers.com/showthread.php?t=1468531
Anybody can confirm it working? i would advice you to try asking this in another thread that has USB host working on an HTC device, maybe they can help you better?
Click to expand...
Click to collapse
it's not working without a kernel with usb host function, we need a usb host enabled kernel for ds before we can use that app
jacob73 said:
i tried to apply sven killing patch manually but i get this when i start compiling:
Code:
drivers/usb/host/ehci-hcd.c: In function 'ehci_hcd_init':
drivers/usb/host/ehci-hcd.c:1192: error: 'ehci_debug_root' undeclared (first use in this function)
drivers/usb/host/ehci-hcd.c:1192: error: (Each undeclared identifier is reported only once
drivers/usb/host/ehci-hcd.c:1192: error: for each function it appears in.)
drivers/usb/host/ehci-hcd.c: In function 'ehci_hcd_cleanup':
drivers/usb/host/ehci-hcd.c:1278: error: 'ehci_debug_root' undeclared (first use in this function)
make[3]: *** [drivers/usb/host/ehci-hcd.o] Error 1
make[2]: *** [drivers/usb/host] Error 2
make[2]: *** Waiting for unfinished jobs....
any idea?!
Click to expand...
Click to collapse
You missed a dependency or a header file I guess.
Gesendet von meinem Desire S mit Tapatalk
Tectas said:
You missed a dependency or a header file I guess.
Gesendet von meinem Desire S mit Tapatalk
Click to expand...
Click to collapse
thanks, when i enable usb debug it fixed, what about this?! :
jacob73 said:
i fix this, but i still get error:
Code:
CC [M] drivers/usb/host/ehci-hcd.o
cc1: warnings being treated as errors
drivers/usb/host/ehci-dbg.c:44: error: 'dbg_hcs_params' defined but not used
drivers/usb/host/ehci-dbg.c:88: error: 'dbg_hcc_params' defined but not used
drivers/usb/host/ehci-hub.c:109: error: 'ehci_adjust_port_wakeup_flags' defined but not used
drivers/usb/host/ehci-q.c:146: error: 'ehci_clear_tt_buffer_complete' defined but not used
drivers/usb/host/ehci-hcd.c:614: error: 'ehci_run' defined but not used
drivers/usb/host/ehci-hcd.c:1048: error: 'ehci_endpoint_reset' defined but not used
make[3]: *** [drivers/usb/host/ehci-hcd.o] Error 1
make[2]: *** [drivers/usb/host] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
Desire HD have same CPU and supporting USB Host. No chance to port USB Host driver from this device?
Skijumper said:
Desire HD have same CPU and supporting USB Host. No chance to port USB Host driver from this device?
Click to expand...
Click to collapse
It can be, but we need to port this to kernel source, because devices are different, and kernel file (zimage) is close,,, dhd have same cpu , but no lcd or touch or other stuff
maybe Lowveld will give us a hand his kernels and roms are great!
i did it
wow
Congratulations mate - hope you can find some use for this and the ability to port it to other ROMs as this could be a useful for future builds.

[Q] Pdroid patch for MildWild 5 rom

I recently installed a new rom on my HTC Desire. MildWild V5
Now I'm trying to get Pdroid installed on it, but I can't get the ROM patched with the patcher (haven't tried the auto patcher, since I don't have a virtual machine at hand a.t.m.)
Since I haven't made enough posts to reply in the development section I ask it here.
Below is the log file of the 1.32 patcher
Code:
PDroid Patcher v0.321 - Patch v1.32
Patching C:\Users\BlaBla\Downloads\MildWild CM-5.0.zip
Extracting framework files from ROM
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
inflated: META-INF/com/google/android/updater-script
inflated: META-INF/com/google/android/update-binary
Decompiling original files
I: Baksmaling...
I: Copying assets and libs...
I: Baksmaling...
I: Copying assets and libs...
I: Baksmaling...
I: Copying assets and libs...
Cleaning up smali
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" framework.mod.jar.out\smali\android\app\ContextImpl.smali 1>framework.mod.jar.out\smali\android\app\ContextImpl.smali.new
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>move /Y framework.mod.jar.out\smali\android\app\ContextImpl.smali.new framework.mod.jar.out\smali\android\app\ContextImpl.smali
1 bestand(en) zijn verplaatst.
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" framework.mod.jar.out\smali\android\content\ContentResolver.smali 1>framework.mod.jar.out\smali\android\content\ContentResolver.smali.new
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>move /Y framework.mod.jar.out\smali\android\content\ContentResolver.smali.new framework.mod.jar.out\smali\android\content\ContentResolver.smali
1 bestand(en) zijn verplaatst.
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" framework.mod.jar.out\smali\android\telephony\PhoneStateListener.smali 1>framework.mod.jar.out\smali\android\telephony\PhoneStateListener.smali.new
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>move /Y framework.mod.jar.out\smali\android\telephony\PhoneStateListener.smali.new framework.mod.jar.out\smali\android\telephony\PhoneStateListener.smali
1 bestand(en) zijn verplaatst.
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" framework.mod.jar.out\smali\android\telephony\PhoneStateListener$1.smali 1>framework.mod.jar.out\smali\android\telephony\PhoneStateListener$1.smali.new
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>move /Y framework.mod.jar.out\smali\android\telephony\PhoneStateListener$1.smali.new framework.mod.jar.out\smali\android\telephony\PhoneStateListener$1.smali
1 bestand(en) zijn verplaatst.
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali 1>services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali.new
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>move /Y services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali.new services.mod.jar.out\smali\com\android\server\am\ActivityManagerService.smali
1 bestand(en) zijn verplaatst.
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" services.mod.jar.out\smali\com\android\server\ServerThread.smali 1>services.mod.jar.out\smali\com\android\server\ServerThread.smali.new
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>move /Y services.mod.jar.out\smali\com\android\server\ServerThread.smali.new services.mod.jar.out\smali\com\android\server\ServerThread.smali
1 bestand(en) zijn verplaatst.
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>..\tools\sed "/^\s*\.\(line\s[0-9]\{1,\}\)\s*$/d" core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali 1>core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali.new
C:\Users\BlaBla\AppData\Roaming\PDroidPatcher\tmp>move /Y core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali.new core.mod.jar.out\smali\java\lang\ProcessManager$ProcessImpl.smali
1 bestand(en) zijn verplaatst.
Applying PDroid patches
patching file smali/android/app/ContextImpl.smali
Hunk #2 succeeded at 151 (offset 5 lines).
Hunk #3 succeeded at 683 with fuzz 3 (offset 40 lines).
Hunk #4 succeeded at 1166 with fuzz 2 (offset 61 lines).
Hunk #5 succeeded at 1190 with fuzz 3 (offset 64 lines).
Hunk #6 succeeded at 1466 (offset 123 lines).
Hunk #7 succeeded at 1714 (offset 129 lines).
patching file smali/android/content/ContentResolver.smali
Hunk #1 succeeded at 2850 with fuzz 3.
patching file smali/android/privacy/IPrivacySettingsManager.smali
patching file smali/android/privacy/IPrivacySettingsManager$Stub$Proxy.smali
patching file smali/android/privacy/IPrivacySettingsManager$Stub.smali
patching file smali/android/privacy/PrivacyFileObserver.smali
patching file smali/android/privacy/PrivacyPersistenceAdapter.smali
patching file smali/android/privacy/PrivacySettings$1.smali
patching file smali/android/privacy/PrivacySettingsManagerService.smali
patching file smali/android/privacy/PrivacySettingsManager.smali
patching file smali/android/privacy/PrivacySettings.smali
patching file smali/android/privacy/surrogate/PrivacyAccountManager$PrivacyAccountManagerFuture.smali
patching file smali/android/privacy/surrogate/PrivacyAccountManager.smali
patching file smali/android/privacy/surrogate/PrivacyActivityManagerService.smali
patching file smali/android/privacy/surrogate/PrivacyContentResolver.smali
patching file smali/android/privacy/surrogate/PrivacyCursor.smali
patching file smali/android/privacy/surrogate/PrivacyLocationManager$PrivacyLocationUpdater.smali
patching file smali/android/privacy/surrogate/PrivacyLocationManager.smali
patching file smali/android/privacy/surrogate/PrivacyTelephonyManager.smali
patching file smali/android/telephony/PhoneStateListener$1.smali
patching file smali/android/telephony/PhoneStateListener.smali
Hunk #2 succeeded at 64 (offset 1 line).
Hunk #3 succeeded at 173 with fuzz 1 (offset 23 lines).
patching file smali/com/android/server/am/ActivityManagerService.smali
Hunk #1 succeeded at 13018 with fuzz 1 (offset 962 lines).
Hunk #2 succeeded at 19222 with fuzz 2 (offset 1384 lines).
patching file smali/com/android/server/ServerThread.smali
Hunk #1 succeeded at 44 (offset 4 lines).
Hunk #2 succeeded at 396 (offset 44 lines).
patching file smali/java/lang/PrivacyInputStream.smali
patching file smali/java/lang/PrivacyProcessManager$PrivacyFileReader.smali
patching file smali/java/lang/PrivacyProcessManager.smali
patching file smali/java/lang/ProcessManager$ProcessImpl.smali
Hunk #1 succeeded at 57 (offset 5 lines).
Hunk #2 succeeded at 79 (offset 5 lines).
failed to apply PDroid patches
So....
[Solved]
I got my hands on a XP pc and tried it on there. That worked just fine.
So I asume that was the problem, the patcher doesn't work correctly with win7.
:victory:

tabletUI fails on SystemUI.apk

The TabletUI mod no longer works now that the cm 10.1.1 has come out. It fails on the SystemUI.apk patch as follows:
Code:
... apply SystemUI.apk.patch ...
1 out of 1 hunk FAILED -- saving rejects to file smali/com/android/systemui/statusbar/tablet/TabletStatusBar.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/com/android/systemui/statusbar/policy/BatteryController$BatteryStateChangeCallback.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/com/android/systemui/statusbar/policy/BatteryController$SettingsObserver.smali.rej'
4 out of 5 hunks FAILED -- saving rejects to file smali/com/android/systemui/statusbar/policy/BatteryController.smali.rej
1 out of 1 hunk FAILED -- saving rejects to file 'smali/com/android/systemui/statusbar/policy/CircleBattery$SettingsObserver.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
25 out of 25 hunks ignored -- saving rejects to file smali/com/android/systemui/statusbar/policy/CircleBattery.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
6 out of 6 hunks ignored -- saving rejects to file smali/com/android/systemui/statusbar/policy/CircleDockBattery.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/com/android/systemui/statusbar/policy/DockBatteryController$DockBatteryStateChangeCallback.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file smali/com/android/systemui/statusbar/policy/DockBatteryController.smali.rej
I'd post it in its thread but I just started posting here.
loftwyr said:
The TabletUI mod no longer works now that the cm 10.1.1 has come out. It fails on the SystemUI.apk patch as follows:
..
I'd post it in its thread but I just started posting here.
Click to expand...
Click to collapse
The code in the stable build is actually like the nightlies from a few weeks ago. Because of this you have to use older tabletUI patches, like this
Code:
./auto_patcher cm-10.1.1-p5110.zip tabletUI cm 20130403

[Q] How to fix errors resulting from patching the kernel

Greetings-
I am trying to build my first Kernel, and following this tutorial http://forum.xda-developers.com/showthread.php?t=1748297 , I am getting the following errors and some success:
Code:
[email protected]:~/android/kernel/samsung/CivZ-KatTurbine-SM-N9005-900T-master# patch -p1 < kernelPatch
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/cpufreq_interactivex.c
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/cpufreq_lionheart.c
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/cpufreq_ondemandx.c
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/Kconfig
Hunk #1 succeeded at 94 with fuzz 2 (offset -5 lines).
Hunk #2 FAILED at 132.
Hunk #3 succeeded at 167 with fuzz 2 (offset -5 lines).
Hunk #4 FAILED at 244.
2 out of 4 hunks FAILED -- saving rejects to file drivers/cpufreq/Kconfig.rej
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/Makefile
Hunk #1 FAILED at 7.
1 out of 1 hunk FAILED -- saving rejects to file drivers/cpufreq/Makefile.rej
(Patch is indented 4 spaces.)
patching file include/linux/cpufreq.h
Hunk #1 FAILED at 363.
Hunk #2 FAILED at 372.
2 out of 2 hunks FAILED -- saving rejects to file include/linux/cpufreq.h.rej
As you can see I put the patch in the same directory which was result of my unpacking the source zip file from Samsung. Am I doing this wrong? Should the patch be 100% successful?

Categories

Resources