[android-porting] Re: Cursor.patch fails

2009-05-21 Thread Chen Yang
hi Mathias: Would you like to give some suggestions if you can? Thanks a lot. -- Chen On Thu, May 21, 2009 at 12:40 PM, Yi Sun beyo...@gmail.com wrote: Not sure if the hardware cursor would solve the problem or not. the intelfb driver has hw cursor support. Let see if I can find a time

[android-porting] Re: Cursor.patch fails

2009-05-20 Thread Chen Yang
The mouse cursor works! Thanks to Yi for your great work! :) I also observed the same as Chih-wei, if there are some dialog appears, the mouse cursor responds very slowly. To have a try, you can just try in the home screen, long press the mouse and then one dialog will pop up, then you can try

[android-porting] Re: Cursor.patch fails

2009-05-20 Thread Yi Sun
This code is wrong (Ya, I did it). But, it should not be the reason of the slowness. The position convert should not happen here. Otherwise, the event batch will crew up the position value in the original event. Even after I fixed it, the slowness is still there. One thing I have observed is that

[android-porting] Re: Cursor.patch fails

2009-05-20 Thread Chen Yang
My guess is the surface transaction related handling caused the recomputation of the whole screen. I have observed with the diaglo on, system_server used lots of cpu time. So we may need to find some better approach in drawing the cursor. Can some one from google give some comments? Thanks. --

[android-porting] Re: Cursor.patch fails

2009-05-20 Thread Yi Sun
On Thu, 2009-05-21 at 10:19 +0800, Chen Yang wrote: The mouse cursor works! Thanks to Yi for your great work! :) I also observed the same as Chih-wei, if there are some dialog appears, the mouse cursor responds very slowly. To have a try, you can just try in the home screen, long press

[android-porting] Re: Cursor.patch fails

2009-05-20 Thread Yi Sun
Not sure if the hardware cursor would solve the problem or not. the intelfb driver has hw cursor support. Let see if I can find a time to try it out. Yi On Thu, 2009-05-21 at 12:24 +0800, Chen Yang wrote: My guess is the surface transaction related handling caused the recomputation of the whole

[android-porting] Re: Cursor.patch fails

2009-05-08 Thread Yi Sun
CHih-wei, Could you document the test results in the project wiki? THanks Yi On Fri, 2009-05-08 at 00:40 -0700, Chih-Wei wrote: I've done more tests on all EeePC I can access, including 701/701SD/900/900A/901/904HD/1000/1000HD. (using the same kernel image, of course) The touchpad works for

[android-porting] Re: Cursor.patch fails

2009-05-07 Thread Chih-Wei
Hi Yi, Indeed I took that configuration (plus some additional drivers). The following options are enabled: CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y

[android-porting] Re: Cursor.patch fails

2009-05-07 Thread Chih-Wei
I noticed a more serious problem. The EeePC will become suspend for a period of time, and cannot resume back. Actually when I pressed the power button, it tried to resume (can see some console messages), but then enter suspend mode immediately again. On 5月7日, 下午2時29分, Chih-Wei

[android-porting] Re: Cursor.patch fails

2009-05-07 Thread Yi Sun
A. I don't know :-). Ok, let me try to find a 701, If I can get one, I will try it out. At the meanwhile, I will post the new patch. Yi On Wed, 2009-05-06 at 23:29 -0700, Chih-Wei wrote: Hi Yi, Indeed I took that configuration (plus some additional drivers). The following options are

[android-porting] Re: Cursor.patch fails

2009-05-07 Thread Yi Sun
Yes, I'm seeing the same problem... If you enabled wake_lock and fixed all the power related entries in init.rc, your power sleep feature will start to work but no wake up. Currently, you need to set screen timeout to never in setup-sound and display On Thu, 2009-05-07 at 01:45 -0700, Chih-Wei

[android-porting] Re: Cursor.patch fails

2009-05-06 Thread Chih-Wei
I just tested it under a real Eee PC 701. Strangely, when I use the touchpad, I can't see the mouse cursor. But I can scroll the screen. If I use an external usb mouse, the mouse cursor appear and I can use it normally. On 5月6日, 上午10時56分, Chih-Wei cwhu...@linux.org.tw wrote: Hi Yi, I've tried

[android-porting] Re: Cursor.patch fails

2009-05-06 Thread Yi Sun
I have seen this before, your mouse driver is not enabled correctly in the kernel On Wed, 2009-05-06 at 03:06 -0700, Chih-Wei wrote: I just tested it under a real Eee PC 701. Strangely, when I use the touchpad, I can't see the mouse cursor. But I can scroll the screen. If I use an external

[android-porting] Re: Cursor.patch fails

2009-05-06 Thread Chih-Wei
Which option should be enabled for EeePC touchpad? I've check my kernel config, all mouse related options are enabled. (compare to the default eeepc config) On 5月7日, 上午12時16分, Yi Sun beyo...@gmail.com wrote: I have seen this before, your mouse driver is not enabled correctly in the kernel

[android-porting] Re: Cursor.patch fails

2009-05-06 Thread Caesar
Try to enable ps2 mouse support in kernel. On 5月7日, 上午10時19分, Chih-Wei cwhu...@linux.org.tw wrote: Which option should be enabled for EeePC touchpad? I've check my kernel config, all mouse related options are enabled. (compare to the default eeepc config) On 5月7日, 上午12時16分, Yi Sun

[android-porting] Re: Cursor.patch fails

2009-05-06 Thread Yi Sun
BTW- you can take the kernel configuration in my original patch. It has all the options enabled. On Wed, May 6, 2009 at 9:41 PM, Yi Sun beyo...@gmail.com wrote: I memember, I enabled serio and PS2. In the worst case, we can enabled the debug in WindowManagerService to see when happened. You

[android-porting] Re: Cursor.patch fails

2009-05-05 Thread Ravishankar Haranath
Both the patches got applied properly. Need to check the cursor working after building the installer.img. Rgds, Ravi On Mon, May 4, 2009 at 10:40 PM, Yi Sun beyo...@gmail.com wrote: try attached. And let me know if it works. If it is ok, then I will upload it. BTW--- you need to make sure

[android-porting] Re: Cursor.patch fails

2009-05-05 Thread adhi
Hi ! I have some doubts. 1) the new Mouse-cursor-patch is okay . So I guess we should undo the old patches cursor.patch since some of then went through ? 2) Since I am doing manually I need to CD to the proper directory. The second patch 0001-1.-new-kernel.config-to-enabled-mouse-and-vesa-fb-

[android-porting] Re: Cursor.patch fails

2009-05-05 Thread Ravishankar Haranath
You are suggested to apply the patches on a fresh source. 1. cursor patch is for android-src/frameworks/base directory 2. 2nd one is for init.rc file. You need to cd into android-src/vendor/asus/eee_701 On Tue, May 5, 2009 at 1:16 PM, adhi rad.naraya...@gmail.com wrote: Hi ! I have some

[android-porting] Re: Cursor.patch fails

2009-05-05 Thread Yi Sun
Ravi, THanks, please do let me know the test result. Yi On Tue, 2009-05-05 at 12:19 +0530, Ravishankar Haranath wrote: Both the patches got applied properly. Need to check the cursor working after building the installer.img. Rgds, Ravi On Mon, May 4, 2009 at 10:40 PM, Yi Sun

[android-porting] Re: Cursor.patch fails

2009-05-05 Thread Chih-Wei
Hi Yi, I've tried the patches, and tested the installed.img by qemu. The mouse works. :) On 5月6日, 上午12時31分, Yi Sun beyo...@gmail.com wrote: Ravi, THanks, please do let me know the test result. Yi --~--~-~--~~~---~--~~ unsubscribe:

[android-porting] Re: Cursor.patch fails

2009-05-04 Thread Yi Sun
You need to merge cursor.patch manually. During the development, my xemacs changed indent and caused these conflicts in the WindowManagerService.java with new checkouts. You can look at the patch and merge them manually. I will create new patch as soon as I got free time. On Sun, 2009-05-03 at

[android-porting] Re: Cursor.patch fails

2009-05-04 Thread Yi Sun
try attached. And let me know if it works. If it is ok, then I will upload it. BTW--- you need to make sure that your kernel has wake_lock enabled otherwise, current cursor patch will not work. Yi On Sun, 2009-05-03 at 23:45 -0700, adhi wrote: Hi ! I am following the steps mentioned in this