parse-edid : parsing edid 255 byyte 資料的程式

是屬於 read-edid 這個 package，
裝完後，用 parse-edid 讀取 edid 的 255 byte bin file，就會顯示內容，
以 xmbc wiki 裡的 samsung tv example : http://wiki.xbmc.org/index.php?title=Creating_and_using_edid.bin_via_xorg.conf

parse-edid 讀出來的結果是：

parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.

 # EDID version 1 revision 3
Section "Monitor"
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 Identifier "SAMSUNG"
 VendorName "SAM"
 ModelName "SAMSUNG"
 # Block type: 2:0 3:fd
 HorizSync 26-76
 VertRefresh 23-61
 # Max dot clock (video bandwidth) 230 MHz
 # Block type: 2:0 3:fc
 # DPMS capabilities: Active off:no  Suspend:no  Standby:no

 Mode  "1920x1080" # vfreq 60.000Hz, hfreq 67.500kHz
  DotClock 148.500000
  HTimings 1920 2008 2052 2200
  VTimings 1080 1084 1089 1125
  Flags "+HSync" "+VSync"
 EndMode
 Mode  "1360x768" # vfreq 60.015Hz, hfreq 47.712kHz
  DotClock 85.500000
  HTimings 1360 1424 1536 1792
  VTimings 768 771 777 795
  Flags "+HSync" "+VSync"
 EndMode
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
EndSection

diff two source folders

因為 vendor patch 過的 source code 沒有完整的 repo project 資訊，所以只好用 diff 來找出後來自己修改過的地方。

因為 build 過的 source folder 包含一堆不是 source code 的東西，還有一些 git folder 都不要加入 比較，所以要用一些 option 來排除

大概是參考 http://blog.chinaunix.net/space.php?uid=20564848&do=blog&cuid=489391

所以我用的 command 是：

diff -x '.*' -r --brief -x 'out' -x 'kernel_imx' -x 'bootable' --exclude='*.ko' --exclude='*.o' --exclude='*.a' --exclude='*.mod' --exclude='*.cmd' myandroid91 myandroid9.1local 2>&1 | tee difflog

說明：

-r 是 recursive 的意思

-x 是 ignore folder 的意思

--brief 是只要報告不一樣就可以，不必列出不同的內容

--exclude 是排除 xxx

參考 diff help : http://linux.die.net/man/1/find

---

很慘，因為 diff 連 folder attribute 都會compare，而 main trunk 因為大家還不會用 git remote 作 merge ，所以修改了fild attribe 讓所有人都可以 access，導致 diff 的內容整個都...

所以還是要咧出內容 (取消 --brief )，這樣才可以看出真正 source code 的修改。

openocd : target_scrupt , target configure -event

以前的 opencoded 操作範例 都又 target_script 0 .. 但是現在做起來卻說不認識 target_script_0，google 說 target_script 已經被 event 機制取代 這一篇也有說 target_script 已經淘汰了，由 targget event 取代 target_script <target#> <eventname> <scriptname> use <target_name> configure -event <eventname> "script <scriptname>" 至於 event 有哪些，要看 opencod 的 user manual:

The following target events are defined:

• debug-halted The target has halted for debug reasons (i.e.: breakpoint)
• debug-resumed The target has resumed (i.e.: gdb said run)
• early-halted Occurs early in the halt process
• gdb-attach When GDB connects. This is before any communication with the target, so this can be used to set up the target so it is possible to probe flash. Probing flash is necessary during gdb connect if gdb load is to write the image to flash. Another use of the flash memory map is for GDB to automatically hardware/software breakpoints depending on whether the breakpoint is in RAM or read only memory.
• gdb-detach When GDB disconnects
• gdb-end When the target has halted and GDB is not doing anything (see early halt)
• gdb-flash-erase-start Before the GDB flash process tries to erase the flash
• gdb-flash-erase-end After the GDB flash process has finished erasing the flash
• gdb-flash-write-start Before GDB writes to the flash
• gdb-flash-write-end After GDB writes to the flash
• gdb-start Before the target steps, gdb is trying to start/resume the target
• halted The target has halted
• reset-assert-pre Issued as part of reset processing after reset_init was triggered but before either SRST alone is re-asserted on the scan chain, or reset-assert is triggered.
• reset-assert Issued as part of reset processing after reset-assert-pre was triggered. When such a handler is present, cores which support this event will use it instead of asserting SRST. This support is essential for debugging with JTAG interfaces which don't include an SRST line (JTAG doesn't require SRST), and for selective reset on scan chains that have multiple targets.
• reset-assert-post Issued as part of reset processing after reset-assert has been triggered. or the target asserted SRST on the entire scan chain.
• reset-deassert-pre Issued as part of reset processing after reset-assert-post has been triggered.
• reset-deassert-post Issued as part of reset processing after reset-deassert-pre has been triggered and (if the target is using it) after SRST has been released on the scan chain.
• reset-end Issued as the final step in reset processing.
• reset-init Used by reset init command for board-specific initialization. This event fires after reset-deassert-post.

  This is where you would configure PLLs and clocking, set up DRAM so you can download programs that don't fit in on-chip SRAM, set up pin multiplexing, and so on. (You may be able to switch to a fast JTAG clock rate here, after the target clocks are fully set up.)

• reset-start Issued as part of reset processing before reset_init is called.

  This is the most robust place to use jtag_rclk or adapter_khz to switch to a low JTAG clock rate, when reset disables PLLs needed to use a fast clock.

• resume-start Before any target is resumed
• resume-end After all targets have resumed
• resume-ok Success
• resumed Target has resumed

---

event script 可以寫 echo "ok ok ok". 這樣可以確認什麼時候script被 run 到。