PXA310 USB register 設定

Init:
1. reset
2. switch to sync mode
3. set SE0
4. 中斷開起
連起:
1. Set 3319 to Peripheral HS
2. clean XLLP_U2DOTGCR_UTMID
3. Start
4. 連的一開始3319 會變成low power mode(可能是controller 設的?)
此時如果 set XLLP_U2DOTGCR_UTMID，這次連線就是full speed, 可能是斷了chip JK的訊號

---

XLLP_U2DOTGCR_UTMID 和 XLLP_U2DOTGCR_ULE 有點搞不清礎

XLLP_U2DOTGCR_UTMID 感覺像是個開關, controller to 3319 這條路的開關
SPEC 說 set它是防止U2DC 的UTMI的register 去寫3319的ULPI 的register.
但要連起時卻又要clean 掉?

UDE | XLLP_U2DOTGCR_ULE
---------------------------
0 0 hold reset
0 1 can commulicate to 3319
1 0 can commulicate to 3319?
1 1 can commulicate to 3319?

ActiveSync plugin/out

plug out
03/19/2009 21:43:51.735 - UsbComm: Change DTR to 0.
03/19/2009 21:43:51.735 - UsbComm: Closed device.
03/19/2009 21:43:51.767 - USB: Event 32772, name \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
03/19/2009 21:43:51.767 - USB: Device Remove Complete notification
03/19/2009 21:43:52.001 - USB: RNDIS device id \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{a5dcbf10-6530-11d2-901f-00c04fb951ed}

plug in
03/19/2009 21:44:13.622 - USB: RNDIS device id \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
03/19/2009 21:44:13.825 - USB: Event 32768, name \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
03/19/2009 21:44:13.825 - USB: Device Arrival notification
03/19/2009 21:44:13.825 - UsbComm: Open device .
03/19/2009 21:44:13.825 - UsbComm: Change DTR to 1.
03/19/2009 21:44:13.840 - Serial: Starting device detection at 115200.
03/19/2009 21:44:13.840 - UsbComm: Change DTR to 1.

ActiveSync 的log

記錄一下Activesync 切換模式的log

//////////////////////////////Rndis to Serial @WCESCOMM.log

03/19/2009 13:56:22.199 - USB: RNDIS device id \\?\USB#Vid_05e0&Pid_200d#2f5b1900-11fe-0801-4d4f-303937303863#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
03/19/2009 13:56:22.433 - USB: found RNDIS device id USB\Vid_05e0&Pid_200d&Rev_0000
03/19/2009 13:56:22.433 - USB RNDIS: Device Removal notification
03/19/2009 13:56:23.543 - USB: RNDIS device id \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
03/19/2009 13:56:23.699 - USB: Event 32768, name \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
03/19/2009 13:56:23.715 - USB: Device Arrival notification
03/19/2009 13:56:23.715 - UsbComm: Open device .
03/19/2009 13:56:23.715 - Serial: Starting device detection at 115200.
03/19/2009 13:56:23.715 - UsbComm: Change DTR to 1.
03/19/2009 13:56:23.715 - UsbComm: Change DTR to 1.
03/19/2009 13:56:24.230 - AutobaudDetect: Found character .
03/19/2009 13:56:24.230 - AutobaudDetect: Found character .
03/19/2009 13:56:24.230 - AutobaudDetect: Found character I.
03/19/2009 13:56:24.230 - AutobaudDetect: Found character .
03/19/2009 13:56:24.230 - AutobaudDetect: Found character .
03/19/2009 13:56:24.230 - AutobaudDetect: Found character .
03/19/2009 13:56:24.230 - Serial: Unimodem handshake at 115200.
03/19/2009 13:56:24.230 - Proxy: Change connection state 1.
03/19/2009 13:56:24.230 - Proxy: Created dynamic proxy on port 5655.
03/19/2009 13:56:24.246 - Proxy: Created dynamic proxy on port 3000.
03/19/2009 13:56:24.246 - Proxy: Created dynamic proxy on port 3001.
03/19/2009 13:56:24.246 - Proxy: Created dynamic proxy on port 3002.
03/19/2009 13:56:24.246 - Proxy: Created dynamic proxy on port 3003.
03/19/2009 13:56:24.246 - Proxy: Created dynamic proxy on port 3004.
03/19/2009 13:56:24.246 - Proxy: Created dynamic proxy on port 3005.
03/19/2009 13:56:24.246 - Proxy: Created dynamic proxy on port 3006.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3007.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3008.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3009.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3010.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3011.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3012.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3013.
03/19/2009 13:56:24.261 - Proxy: Created dynamic proxy on port 3014.
03/19/2009 13:56:24.277 - Proxy: Created dynamic proxy on port 3015.
03/19/2009 13:56:24.277 - Proxy: Created dynamic proxy on port 3016.
03/19/2009 13:56:24.277 - Proxy: Created dynamic proxy on port 3017.
03/19/2009 13:56:24.277 - Proxy: Created dynamic proxy on port 3018.
03/19/2009 13:56:24.277 - Proxy: Created dynamic proxy on port 3019.
03/19/2009 13:56:24.277 - Proxy: Created dynamic proxy on port 3020.
03/19/2009 13:56:24.277 - Proxy: Created dynamic proxy on port 3021.
03/19/2009 13:56:24.293 - Proxy: Created dynamic proxy on port 3022.
03/19/2009 13:56:24.293 - Proxy: Created dynamic proxy on port 3023.
03/19/2009 13:56:24.293 - Proxy: Created dynamic proxy on port 3024.
03/19/2009 13:56:24.293 - Proxy: Created dynamic proxy on port 3025.
03/19/2009 13:56:24.293 - Proxy: Created dynamic proxy on port 3026.
03/19/2009 13:56:24.293 - Proxy: Created dynamic proxy on port 3027.
03/19/2009 13:56:24.293 - Proxy: Created dynamic proxy on port 3028.
03/19/2009 13:56:24.308 - Proxy: Created dynamic proxy on port 3029.
03/19/2009 13:56:24.308 - Proxy: Created dynamic proxy on port 3030.
03/19/2009 13:56:24.308 - Proxy: Created dynamic proxy on port 3031.
03/19/2009 13:56:24.308 - Proxy: Created dynamic proxy on port 6510.
03/19/2009 13:56:24.308 - Proxy: Created dynamic proxy on port 6511.
03/19/2009 13:56:24.308 - Proxy: Created dynamic proxy on port 6512.
03/19/2009 13:56:24.308 - Proxy: Created dynamic proxy on port 6513.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6514.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6515.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6516.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6517.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6518.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6519.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6520.
03/19/2009 13:56:24.324 - Proxy: Created dynamic proxy on port 6521.
03/19/2009 13:56:24.340 - Proxy: Created dynamic proxy on port 6522.
03/19/2009 13:56:24.340 - Proxy: Created dynamic proxy on port 6523.
03/19/2009 13:56:24.340 - Proxy: Created dynamic proxy on port 6524.
03/19/2009 13:56:24.340 - Proxy: Created dynamic proxy on port 6525.
03/19/2009 13:56:24.340 - Proxy: Created dynamic proxy on port 6526.
03/19/2009 13:56:24.340 - Proxy: Created dynamic proxy on port 6527.
03/19/2009 13:56:24.340 - Proxy: Created dynamic proxy on port 6528.
03/19/2009 13:56:24.355 - Proxy: Created dynamic proxy on port 6529.
03/19/2009 13:56:24.355 - Proxy: Created dynamic proxy on port 6530.
03/19/2009 13:56:24.355 - Proxy: Created dynamic proxy on port 6531.
03/19/2009 13:56:24.355 - Proxy: Created dynamic proxy on port 6532.
03/19/2009 13:56:24.355 - Proxy: Created dynamic proxy on port 6533.
03/19/2009 13:56:24.355 - Proxy: Created dynamic proxy on port 6534.
03/19/2009 13:56:24.355 - Proxy: Created dynamic proxy on port 6535.
03/19/2009 13:56:24.371 - Proxy: Created dynamic proxy on port 6536.
03/19/2009 13:56:24.371 - Proxy: Created dynamic proxy on port 6537.
03/19/2009 13:56:24.371 - Proxy: Created dynamic proxy on port 6538.
03/19/2009 13:56:24.371 - Proxy: Created dynamic proxy on port 6539.
03/19/2009 13:56:24.371 - Proxy: Created dynamic proxy on port 6540.
03/19/2009 13:56:24.371 - Proxy: Created dynamic proxy on port 6541.
03/19/2009 13:56:24.371 - Proxy: Created dynamic proxy on port 1026.
03/19/2009 13:56:27.840 - TCP: ....S., 192.168.55.101(1035) => 192.168.55.100(7438) Seq=12347588-12347588 Ack=0 Win=32768 Len=48
03/19/2009 13:56:27.840 - Proxy: Connection Attempt on port 7438, dest ip 0x6437a8c0
03/19/2009 13:56:27.840 - TCP: .A..S., 192.168.55.100(7438) => 192.168.55.101(1035) Seq=17445625-17445625 Ack=12347589 Win=8760 Len=44
03/19/2009 13:56:27.933 - TCP: ....S., 192.168.55.101(1036) => 192.168.55.100(990) Seq=12367730-12367730 Ack=0 Win=32768 Len=48
03/19/2009 13:56:27.933 - Proxy: Connection Attempt on port 990, dest ip 0x6437a8c0
03/19/2009 13:56:27.949 - TCP: .A..S., 192.168.55.100(990) => 192.168.55.101(1036) Seq=17445734-17445734 Ack=12367731 Win=8760 Len=44
03/19/2009 13:56:28.824 - CesProxy: Accept on port 7438, IsWinsock 0, hResult 0
03/19/2009 13:56:28.824 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
03/19/2009 13:56:28.918 - TCP: ....S., 192.168.55.101(1037) => 192.168.55.100(990) Seq=12668475-12668475 Ack=0 Win=32768 Len=48
03/19/2009 13:56:28.933 - TCP: .A..S., 192.168.55.100(990) => 192.168.55.101(1037) Seq=17446718-17446718 Ack=12668476 Win=8760 Len=44
03/19/2009 13:56:29.918 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
03/19/2009 13:56:29.918 - TCP: ....S., 192.168.55.101(1039) => 192.168.55.100(990) Seq=12958012-12958012 Ack=0 Win=32768 Len=48
03/19/2009 13:56:29.918 - TCP: .A..S., 192.168.55.100(990) => 192.168.55.101(1039) Seq=17447703-17447703 Ack=12958013 Win=8760 Len=44
03/19/2009 13:56:31.011 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0
03/19/2009 13:56:31.027 - TCP: ....S., 192.168.55.101(1040) => 192.168.55.100(990) Seq=13270839-13270839 Ack=0 Win=32768 Len=48
03/19/2009 13:56:31.027 - TCP: .A..S., 192.168.55.100(990) => 192.168.55.101(1040) Seq=17448812-17448812 Ack=13270840 Win=8760 Len=44
03/19/2009 13:56:31.027 - CesProxy: Accept on port 990, IsWinsock 0, hResult 0


////////////////////////////////////Serial to Rndis @WCESCOMM.log
03/19/2009 13:58:09.806 - UsbComm: Change DTR to 0.
03/19/2009 13:58:09.806 - UsbComm: Closed device.
03/19/2009 13:58:09.806 - Proxy: Change connection state 0.
03/19/2009 13:58:09.806 - CesProxy: Close PPP socket 990
03/19/2009 13:58:09.821 - CesProxy: Accept on port 990, IsWinsock 0, hResult 80072714
03/19/2009 13:58:09.821 - CesProxy: Close PPP socket 7438
03/19/2009 13:58:09.821 - CesProxy: Accept on port 7438, IsWinsock 0, hResult 80072714
03/19/2009 13:58:09.821 - CesProxy: Close Win socket 1026
03/19/2009 13:58:09.821 - CesProxy: Accept on port 1026, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.821 - CesProxy: Close Win socket 6541
03/19/2009 13:58:09.821 - CesProxy: Accept on port 6541, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.837 - CesProxy: Close Win socket 6540
03/19/2009 13:58:09.837 - CesProxy: Accept on port 6540, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.837 - USB: Event 32772, name \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
03/19/2009 13:58:09.837 - CesProxy: Close Win socket 6539
03/19/2009 13:58:09.852 - USB: Device Remove Complete notification
03/19/2009 13:58:09.852 - CesProxy: Accept on port 6539, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.852 - CesProxy: Close Win socket 6538
03/19/2009 13:58:09.852 - CesProxy: Accept on port 6538, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.852 - CesProxy: Close Win socket 6537
03/19/2009 13:58:09.852 - CesProxy: Accept on port 6537, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.852 - CesProxy: Close Win socket 6536
03/19/2009 13:58:09.868 - CesProxy: Accept on port 6536, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.868 - CesProxy: Close Win socket 6535
03/19/2009 13:58:09.868 - CesProxy: Accept on port 6535, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.868 - CesProxy: Close Win socket 6534
03/19/2009 13:58:09.868 - CesProxy: Accept on port 6534, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.868 - CesProxy: Close Win socket 6533
03/19/2009 13:58:09.868 - CesProxy: Accept on port 6533, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.884 - CesProxy: Close Win socket 6532
03/19/2009 13:58:09.884 - CesProxy: Accept on port 6532, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.884 - CesProxy: Close Win socket 6531
03/19/2009 13:58:09.884 - CesProxy: Accept on port 6531, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.884 - CesProxy: Close Win socket 6530
03/19/2009 13:58:09.884 - CesProxy: Accept on port 6530, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.884 - CesProxy: Close Win socket 6529
03/19/2009 13:58:09.899 - CesProxy: Accept on port 6529, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.899 - CesProxy: Close Win socket 6528
03/19/2009 13:58:09.899 - CesProxy: Accept on port 6528, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.899 - CesProxy: Close Win socket 6527
03/19/2009 13:58:09.899 - CesProxy: Accept on port 6527, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.899 - CesProxy: Close Win socket 6526
03/19/2009 13:58:09.899 - CesProxy: Accept on port 6526, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.915 - CesProxy: Close Win socket 6525
03/19/2009 13:58:09.915 - CesProxy: Accept on port 6525, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.915 - CesProxy: Close Win socket 6524
03/19/2009 13:58:09.915 - CesProxy: Accept on port 6524, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.915 - CesProxy: Close Win socket 6523
03/19/2009 13:58:09.915 - CesProxy: Accept on port 6523, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.915 - CesProxy: Close Win socket 6522
03/19/2009 13:58:09.915 - CesProxy: Accept on port 6522, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.915 - CesProxy: Close Win socket 6521
03/19/2009 13:58:09.931 - CesProxy: Accept on port 6521, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.931 - CesProxy: Close Win socket 6520
03/19/2009 13:58:09.931 - CesProxy: Accept on port 6520, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.931 - CesProxy: Close Win socket 6519
03/19/2009 13:58:09.931 - CesProxy: Accept on port 6519, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.931 - CesProxy: Close Win socket 6518
03/19/2009 13:58:09.931 - CesProxy: Accept on port 6518, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.931 - CesProxy: Close Win socket 6517
03/19/2009 13:58:09.946 - CesProxy: Accept on port 6517, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.946 - CesProxy: Close Win socket 6516
03/19/2009 13:58:09.946 - CesProxy: Accept on port 6516, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.946 - CesProxy: Close Win socket 6515
03/19/2009 13:58:09.946 - CesProxy: Accept on port 6515, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.946 - CesProxy: Close Win socket 6514
03/19/2009 13:58:09.946 - CesProxy: Accept on port 6514, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.946 - CesProxy: Close Win socket 6513
03/19/2009 13:58:09.946 - CesProxy: Accept on port 6513, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.962 - CesProxy: Close Win socket 6512
03/19/2009 13:58:09.962 - CesProxy: Accept on port 6512, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.962 - CesProxy: Close Win socket 6511
03/19/2009 13:58:09.962 - CesProxy: Accept on port 6511, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.962 - CesProxy: Close Win socket 6510
03/19/2009 13:58:09.962 - CesProxy: Accept on port 6510, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.977 - CesProxy: Close Win socket 3031
03/19/2009 13:58:09.977 - CesProxy: Accept on port 3031, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.977 - CesProxy: Close Win socket 3030
03/19/2009 13:58:09.977 - CesProxy: Accept on port 3030, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.977 - CesProxy: Close Win socket 3029
03/19/2009 13:58:09.977 - CesProxy: Accept on port 3029, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.977 - CesProxy: Close Win socket 3028
03/19/2009 13:58:09.977 - CesProxy: Accept on port 3028, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.993 - CesProxy: Close Win socket 3027
03/19/2009 13:58:09.993 - CesProxy: Accept on port 3027, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.993 - CesProxy: Close Win socket 3026
03/19/2009 13:58:09.993 - CesProxy: Accept on port 3026, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.993 - CesProxy: Close Win socket 3025
03/19/2009 13:58:09.993 - CesProxy: Accept on port 3025, IsWinsock 1, hResult 80072714
03/19/2009 13:58:09.993 - CesProxy: Close Win socket 3024
03/19/2009 13:58:10.009 - CesProxy: Accept on port 3024, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.009 - CesProxy: Close Win socket 3023
03/19/2009 13:58:10.009 - CesProxy: Accept on port 3023, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.009 - CesProxy: Close Win socket 3022
03/19/2009 13:58:10.009 - CesProxy: Accept on port 3022, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.009 - CesProxy: Close Win socket 3021
03/19/2009 13:58:10.024 - CesProxy: Accept on port 3021, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.024 - CesProxy: Close Win socket 3020
03/19/2009 13:58:10.024 - CesProxy: Accept on port 3020, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.024 - CesProxy: Close Win socket 3019
03/19/2009 13:58:10.024 - CesProxy: Accept on port 3019, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.024 - CesProxy: Close Win socket 3018
03/19/2009 13:58:10.024 - CesProxy: Accept on port 3018, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.040 - CesProxy: Close Win socket 3017
03/19/2009 13:58:10.040 - CesProxy: Accept on port 3017, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.040 - CesProxy: Close Win socket 3016
03/19/2009 13:58:10.040 - CesProxy: Accept on port 3016, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.040 - CesProxy: Close Win socket 3015
03/19/2009 13:58:10.040 - CesProxy: Accept on port 3015, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.040 - CesProxy: Close Win socket 3014
03/19/2009 13:58:10.040 - CesProxy: Accept on port 3014, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.056 - CesProxy: Close Win socket 3013
03/19/2009 13:58:10.056 - CesProxy: Accept on port 3013, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.056 - CesProxy: Close Win socket 3012
03/19/2009 13:58:10.056 - CesProxy: Accept on port 3012, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.056 - CesProxy: Close Win socket 3011
03/19/2009 13:58:10.056 - CesProxy: Accept on port 3011, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.056 - CesProxy: Close Win socket 3010
03/19/2009 13:58:10.056 - CesProxy: Accept on port 3010, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.071 - CesProxy: Close Win socket 3009
03/19/2009 13:58:10.071 - CesProxy: Accept on port 3009, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.071 - CesProxy: Close Win socket 3008
03/19/2009 13:58:10.071 - CesProxy: Accept on port 3008, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.071 - CesProxy: Close Win socket 3007
03/19/2009 13:58:10.071 - CesProxy: Accept on port 3007, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.071 - CesProxy: Close Win socket 3006
03/19/2009 13:58:10.071 - CesProxy: Accept on port 3006, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.087 - CesProxy: Close Win socket 3005
03/19/2009 13:58:10.087 - CesProxy: Accept on port 3005, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.087 - CesProxy: Close Win socket 3004
03/19/2009 13:58:10.087 - CesProxy: Accept on port 3004, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.087 - CesProxy: Close Win socket 3003
03/19/2009 13:58:10.087 - CesProxy: Accept on port 3003, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.087 - CesProxy: Close Win socket 3002
03/19/2009 13:58:10.087 - CesProxy: Accept on port 3002, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.087 - CesProxy: Close Win socket 3001
03/19/2009 13:58:10.102 - CesProxy: Accept on port 3001, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.102 - CesProxy: Close Win socket 3000
03/19/2009 13:58:10.102 - CesProxy: Accept on port 3000, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.102 - CesProxy: Close Win socket 5655
03/19/2009 13:58:10.102 - CesProxy: Accept on port 5655, IsWinsock 1, hResult 80072714
03/19/2009 13:58:10.102 - CesProxy: Close PPP socket 990
03/19/2009 13:58:10.102 - CesProxy: recv failed on PPP socket 990, err = 10053
03/19/2009 13:58:10.102 - CesProxy: Close Win socket 990
03/19/2009 13:58:10.102 - CesProxy: recv failed on Win socket 990, err = 10053
03/19/2009 13:58:10.118 - CesProxy: Close PPP socket 990
03/19/2009 13:58:10.118 - CesProxy: recv failed on PPP socket 990, err = 10053
03/19/2009 13:58:10.118 - CesProxy: Close Win socket 990
03/19/2009 13:58:10.118 - CesProxy: recv failed on Win socket 990, err = 10053
03/19/2009 13:58:10.118 - CesProxy: Close PPP socket 990
03/19/2009 13:58:10.118 - CesProxy: recv failed on PPP socket 990, err = 10053
03/19/2009 13:58:10.118 - CesProxy: Close Win socket 990
03/19/2009 13:58:10.118 - CesProxy: recv failed on Win socket 990, err = 10053
03/19/2009 13:58:10.118 - CesProxy: Close PPP socket 990
03/19/2009 13:58:10.134 - CesProxy: recv failed on PPP socket 990, err = 10053
03/19/2009 13:58:10.134 - CesProxy: Close Win socket 990
03/19/2009 13:58:10.134 - CesProxy: recv failed on Win socket 990, err = 10053
03/19/2009 13:58:10.134 - CesProxy: Close PPP socket 7438
03/19/2009 13:58:10.134 - CesProxy: recv failed on PPP socket 7438, err = 10053
03/19/2009 13:58:10.134 - CesProxy: Close Win socket 7438
03/19/2009 13:58:10.134 - CesProxy: recv failed on Win socket 7438, err = 10053
03/19/2009 13:58:10.243 - USB: RNDIS device id \\?\USB#Vid_05e0&Pid_2000#2f5b1900-11fe-0801-4d4f-303937303863#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
03/19/2009 13:58:11.931 - USB: RNDIS device id \\?\USB#Vid_05e0&Pid_200d#2f5b1900-11fe-0801-4d4f-303937303863#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
03/19/2009 13:58:12.087 - USB: found RNDIS device id USB\Vid_05e0&Pid_200d&Rev_0000
03/19/2009 13:58:20.493 - USB RNDIS: Device Arrival notification



////////////////////////////////RNDIS to SErial @WCESMgr
03/19/2009 14:01:32.122 **************** Logging Started ****************
03/19/2009 14:01:32.122 Process C:\Program Files\Microsoft ActiveSync\WCESMgr.exe p(3032)
03/19/2009 14:01:32.122 ActiveSync second instance started, Cmd line: '/onconnect'
03/19/2009 14:01:32.122 ActiveSync second instance exiting
03/19/2009 14:01:32.122 **************** Logging Stopped ****************
03/19/2009 14:01:34.153 Creating new partnership for device 0x0 (Pocket_PC, PocketPC).
03/19/2009 14:01:35.481 p(3472) t(2672) TraceToFile -> ERROR in CCSP::ParseNodes : hr = 0x80140507 - Devicecm.cpp(1598)
03/19/2009 14:01:35.481 Found PIM at 'C:\PROGRA~1\MICROS~3\Office12\OUTLOOK.EXE'
03/19/2009 14:01:35.481 Found PIM at 'C:\PROGRA~1\MICROS~3\Office12\OUTLOOK.EXE'
03/19/2009 14:01:37.981 DTPT: Setting DTPT network to {18AD9FBD-F716-ACB6-FD8A-1965DB95B814}
03/19/2009 14:01:37.981 DTPT: Incomming proxy server string: proxy.iec2.iac:80
03/19/2009 14:01:37.981 DTPT: Setup proxy to send to server. Src={18AD9FBD-F716-ACB6-FD8A-1965DB95B814} Dest={436EF144-B4FB-4863-A041-8F905A62C572} Proxy=proxy.iec2.iac:80 Socks=proxy.iec2.iac:1080 HR=0x00000000
03/19/2009 14:01:37.981 DTPT: Send DTPT Network={18AD9FBD-F716-ACB6-FD8A-1965DB95B814}. Result=0x00000000
03/19/2009 14:01:37.981 DTPTMultiHoming: Send Value=0 Result=0x00000000

//////////////////////////////Serial to RNDIS @WCESMgr
03/19/2009 14:03:12.770 **************** Logging Started ****************
03/19/2009 14:03:12.770 Process C:\Program Files\Microsoft ActiveSync\WCESMgr.exe p(4468)
03/19/2009 14:03:12.770 ActiveSync second instance started, Cmd line: '/onconnect'
03/19/2009 14:03:12.770 ActiveSync second instance exiting
03/19/2009 14:03:12.770 **************** Logging Stopped ****************
03/19/2009 14:03:13.223 Creating new partnership for device 0x0 (Pocket_PC, PocketPC).
03/19/2009 14:03:14.270 p(3472) t(4796) TraceToFile -> ERROR in CCSP::ParseNodes : hr = 0x80140507 - Devicecm.cpp(1598)
03/19/2009 14:03:14.270 Found PIM at 'C:\PROGRA~1\MICROS~3\Office12\OUTLOOK.EXE'
03/19/2009 14:03:14.270 Found PIM at 'C:\PROGRA~1\MICROS~3\Office12\OUTLOOK.EXE'
03/19/2009 14:03:15.910 DTPT: Setting DTPT network to {18AD9FBD-F716-ACB6-FD8A-1965DB95B814}
03/19/2009 14:03:15.910 DTPT: Incomming proxy server string: proxy.iec2.iac:80
03/19/2009 14:03:15.910 DTPT: Setup proxy to send to server. Src={18AD9FBD-F716-ACB6-FD8A-1965DB95B814} Dest={436EF144-B4FB-4863-A041-8F905A62C572} Proxy=proxy.iec2.iac:80 Socks=proxy.iec2.iac:1080 HR=0x00000000

CHAPTER 1An Introduction to Device Drivers @Linux device drivers 3rd

最近開始要study Linux 的東西, 先從這本Linux device drivers 3rd開始看
順便練一下英文。

---

CHAPTER 1An Introduction toDevice Drivers

第一章 Device driver 的介紹

One of the many advantages of free operating systems, as typified by Linux, is that their internals are open for all to view.

免費的OS,像Linux, 的眾多優點之一就是code 都是開放的.

The operating system, once a dark and mysterious area whose code was restricted to a small number of programmers, can now be readily examined, understood, and modified by anybody with the requisite skills.

OS, 一個黑暗又神祕的領域,這個領域總是被掌握在少數幾位工程師身上，如今可以容易的被任何有能力的人，檢視、了解及修改.

Linux has helped to democratize operating systems.

Linux 已經成為大眾化的OS.

The Linux kernel remains a large and complex body of code, however, and would-be kernel hackers need an entry point where they can approach the code without being overwhelmed by complexity. Often, device drivers provide that gateway.

Linux kernel 總是很複雜的，對於那些想要成為kernel 專家的人，需要一個起點來了解kernel是比較容易的，而通常這個點就是device drivers.

Device drivers take on a special role in the Linux kernel.

在Linux kernel 裡 Device drivers 扮演了一個特別的角色.

They are distinct “blackboxes” that make a particular piece of hardware respond to a well-defined internal programming interface; they hide completely the details of how the device works.

它們跟所謂的"黑盒子"不同，它們讓一個特定的硬體對應到定義的好的內部程式介面; 它們能夠完全的穩藏硬體的動作。

User activities are performed by means of a set of standardized calls that are independent of the specific driver; mapping those calls to device-specific operations that acton real hardware is then the role of the device driver.

上層的使用者可以在一系列標準的function calls 上運作，而每一個function call 則是對印到獨立的且特定的硬體; 這也就是device driver所做的事。

This programming interface is such that drivers can be built separately from the rest of the kernel and “plugged in”at runtime when needed.

這個programming interface 可以分別build. 當需要時只要 "plugged in"就可. 即使是在rumtmie的時候。

This modularity makes Linux drivers easy to write, to the point that there are now hundreds of them available.

在這樣的模組化情況下，linux drivers 就很容易的去寫它。到目前為止已有幾百個drivers 可用了.

There are a number of reasons to be interested in the writing of Linux device drivers.

有很多理由讓你對設計Linux device drivers 有興趣 。

The rate at which new hardware becomes available (and obsolete!) alone guarantees that driver writers will be busy for the foreseeable future.

硬體不斷的出新換舊，更顯示出可預期的未來，driver 工程師們會一直很忙。

Individuals may need to know about drivers in order to gain access to a particular device that is of interest to them.

他們需要了解drivers ，才能對他們有興趣的device，進行存取

Hardware vendors, by making a Linux driver available for their products, can add the large and growing Linux user base to their potential markets.

讓想要支援Linux的硬體製造商，可以將那些使用Linux 的人，加入他們的潛在市場。

And the opensource nature of the Linux system means that if the driver writer wishes, the source to a driver can be quickly disseminated to millions of users.

而Linux 系統的opensource意謂著driver source 可以快速的散播給幾百萬人，如果driver設計師希望的話。

This book teaches you how to write your own drivers and how to hack around in related parts of the kernel.

這本書教你如何寫你的driver，以及如何處理跟它有關的kernel 部份。

We have taken a device-independent approach; the programming techniques and interfaces are presented, whenever possible, without being tied to any specific device.

我們已經採用裝置獨立的方式;程式技巧和介面都不需要跟任何特定的device 綁在一起。

Each driver is different; as a driver writer, you need to understand your specific device well.

每個driver 都不同; 身為driver 設計者必需要了解你的device.

But most of the principles and basic techniques are the same for all drivers. This book cannot teach you about your device,but it gives you a handle on the background you need to make your device work.

不過對所以的drivers來說，大部份的原則和基本技巧是一樣的。這本書沒辦法告訴你,關於你的device的東西，但可以告訴你如何讓你的device動起來，所需的背景知識

The Role of the Device Driver

Device driver 的角色

As a programmer, you are able to make your own choices about your driver, and
choose an acceptable trade-off between the programming time required and the flexibility of the result.

身為程式設計師，你能夠選擇你的driver, 也能夠在程式需完成的時間及靈活性之中做一個折衷的選擇。

Though it may appear strange to say that a driver is “flexible,” we
like this word because it emphasizes that the role of a device driver is providing
mechanism, not policy.

雖然說driver 是靈活的很奇怪，但是我們喜歡這個字眼，因為這强調了device driver 是一個可以"提供"的機制而不是個方法。

The distinction between mechanism and policy is one of the best ideas behind the
Unix design.

機制和方針之間的不同正是Unix 設計的背後最好的idea.

Most programming problems can indeed be split into two parts: “what
capabilities are to be provided” (the mechanism) and “how those capabilities can be
used” (the policy).

大部份設計的問題，可以正好分成兩個部份:"什麼樣的能力可以被提供"(機制)和"哪些能力如何被使用"(方針)

If the two issues are addressed by different parts of the program,or even by different programs altogether, the software package is much easier to develop and to adapt to particular needs.

如果這兩個問題被提出來在同一個程式不同的部份，或甚至完全不同的程式，那程式就很容易去研發也容易去適應特定的需求。

For example, Unix management of the graphic display is split between the X server,
which knows the hardware and offers a unified interface to user programs, and the
window and session managers, which implement a particular policy without knowing
anything about the hardware.

舉例來說，Unix 的圖形顯示管理就分X server(知道硬體也提供一個統一的介面給用的程式)和window, 還有session managers(實現了一個特定的方法在不知道硬體的情形下)。

People can use the same window manager on different hardware, and different users can run different configurations on the same workstation.

人們可以用一樣的window manager 在不同的硬體上跑，或者是不同的user 可以跑不同的組態在同一個workstation。

Even completely different desktop environments, such as KDE and GNOME, can coexist on the same system.

或甚至完全不同的桌面環境，像是KDE和GNOME，可以共存在同一個系統。

Another example is the layered structure of TCP/IP networking: the operating system offers the socket abstraction, which implements no policy regarding the data to be transferred, while different servers are in charge of the services (and their associated policies).

另一個例子是TCP/IP 網路的分層架構: 當不同的server再提供服務時(提供和何傳送資料的方法)，作業系統就有提供socket抽像層(不提供任何方法跟被傳送的資料有關)

Moreover, a server like ftpd provides the file transfer mechanism, while users can use whatever client they prefer; both command-line and graphic clients exist, and anyone can write a new user interface to transfer files.

還有，像FTP 這樣的server 有提供檔案傳輸的機制，但是無論使用者用什麼介面都可用這個機制;command-line 和繪圖介面都可同時存在，並且任何人都可以寫個新的介面來傳送檔案

Where drivers are concerned, the same separation of mechanism and policy applies.

那drivers 要關切的,就是the same separation of mechanism and policy applies

The floppy driver is policy free—its role is only to show the diskette as a continuous array of data blocks. Higher levels of the system provide policies, such as who may access the floppy drive, whether the drive is accessed directly or via a filesystem, and whether users may mount filesystems on the drive.

軟碟 driver 不提供任何方法-它的角色就是只有顯示一個連續資料的陣列。而上層的系統則提供方法來讓任何人直接存取軟碟或通過檔案系統。

Since different environments usually need to use hardware in different ways, it’s important to be as policy free as possible.

一但在不同的環境下，用不同的方式，經常使用硬體，driver盡可能的不限制使用方法，就顯的很重要。

When writing drivers, a programmer should pay particular attention to this fundamental concept: write kernel code to access the hardware, but don’t force particular policies on the user, since different users have different needs.

當要設計drivers時，設計者們應該要特別注意這個重要的觀念: 寫一個在kernel的程式，來存取硬體，而不是要求使用者用特定的方法來用你的硬體，因為不同的使用者有不同的需要。

The driver should deal with making the hardware available, leaving all the issues about how to use the hardware to the applications.

driver 應該要讓硬體可以被使用，而不要管應用程式要如何使用硬體

A driver, then, is flexible if it offers access to the hardware capabilities without adding constraints.

然後driver也要夠靈活，如果它提供個能力來無限制的使用硬體

Sometimes, however, some policy decisions must be made. For example, a digital I/O driver may only offer byte-wide access to the hardware in order to avoid the extra code needed to handle individual bits.

然而，有時候有些方法是要被確定的。例如，一個數位I/O driver可能只提供byte-wide 的存取，來存取硬體來避免要額外的程式來處理獨立的bits

You can also look at your driver from a different perspective: it is a software layer
that lies between the applications and the actual device.

你也可以用不同的觀點來看你的driver: 它是一個軟體躺在應用程式跟實體device 的中間。

This privileged role of the driver allows the driver programmer to choose exactly how the device should appear: different drivers can offer different capabilities, even for the same device.

對於一個扮演有特權的角色的driver來說，允許driver 設計者可以決定device 要如何見人: 甚至於同一個device，可以有不同的drivers來提供不同的能力。

The actual driver design should be a balance between many different considerations. For instance, a single device may be used concurrently by different programs, and the
driver programmer has complete freedom to determine how to handle concurrency.

實際的driver設計應該要在許多不同的顧慮中取得平衡。舉例來說，一個單一的device可能同時被不同的程式使用，而driver 的設計者有完全的自由來決定如何處理這樣的同時發生的情況。

You could implement memory mapping on the device independently of its hardware
capabilities, or you could provide a user library to help application programmers
implement new policies on top of the available primitives, and so forth.

你可以寫個記憶體對映到一個完全跟硬體無關的device，或者你也可以提供一個user library 來幫助應用程式的設計者在可用的原素上寫些新的方法來使用，等等。

One major consideration is the trade-off between the desire to present the user with as many options as possible and the time you have to write the driver, as well as the need to keep things simple so that errors don’t creep in.

一個主要的考量就是，不但要在盡可能的給user選擇的權利和完成driver所需的時間中取得妥協，還要讓它簡單，以致於錯誤數量不會一直的上升。

Policy-free drivers have a number of typical characteristics. These include support for both synchronous and asynchronous operation, the ability to be opened multiple
times, the ability to exploit the full capabilities of the hardware, and the lack of software layers to “simplify things” or provide policy-related operations.

不含使用方法的driver 有很多特性。像是同步和非同步的運作，可以被開啟很多次，可以被盡情的使用，或是沒有軟體層讓它很簡單，或提供有特定方法的運作。

Drivers of this sort not only work better for their end users, but also turn out to be easier to write and maintain as well. Being policy-free is actually a common target for software designers.

這種特性的drivers 不只對end usres來說很好用，也容易來撰寫及維護。像這樣的不限制使用方法的driver 其實是軟體設計者的共同目標。

Many device drivers, indeed, are released together with user programs to help with
configuration and access to the target device.

透過使用者的程式幫助設定並存取目標的device,確實許多device drivers 是互相關連在一起的.

Those programs can range from simple utilities to complete graphical applications.

這些程式可以將簡單的工具延申到一個完整的圖形應用程式。

Examples include the tunelp program, which adjusts how the parallel port printer driver operates, and the graphical cardctl utility that is part of the PCMCIA driver package. Often a client library is provided as well, which provides capabilities that do not need to be implemented as part of the driver itself.

tunelp 程式就是個例子，它是用來調節並列port(印表機的運作)，及繪圖 cardctl 系統工具(PCMCIA driver 包的一部份)。像client library 也是經常被提供，這樣的library 就提供了一些不需要在driver 裡寫的一些功能

The scope of this book is the kernel, so we try not to deal with policy issues or with application programs or support libraries. Sometimes we talk about different policies and how to support them, but we won’t go into much detail about programs
using the device or the policies they enforce. You should understand, however, that
user programs are an integral part of a software package and that even policy-free
packages are distributed with configuration files that apply a default behavior to the underlying mechanisms.

這本書是範疇在kernel,所以我們試著不要處理applicantion如何用的問題或是支援資料庫。有時我們會討論到不同的方法和如何支援他們，但我們不會太仔細的討論程式如何使用device，或是他們實施什麼樣的方法。然而，你需要了解，使用者程式是整個軟體組件的一部份，就算是(不含使用方法)的組件也是有設定檔，來設定預設的行為來實現基本的的機制。

有錢人想的果然和我不一樣

前一陣子看到有人說最快賺錢的方式就是"站在巨人的肩膀上"
找個金主，他出80你出20去投資。
然後我問:金主怎麼會借錢給一個沒經驗的人
答案是：真正的大金主是不會care 借你幾百萬或是1 2千萬。因為他們一天可能就好幾億再上下。
資本愈雄厚的人，要求的報籌率愈低。

確實我沒想過有錢人能承受的風險跟一般人不一樣(因為我沒有有錢過 :P)

--------------------------------------------------------------------------------

Q: 我如何用1百萬去多賺出至少10萬元以上的獲利在一年內，透過目前我有的專業能力?
1.讓自己出名，搞一點東西post 到網路上。然後可能就有什麼機會產生。
Q: 有什麼能力是我可以培養來做到10%以上的投報率?