在design house做了三年的DV,才疏學淺,但希望能夠將DV學完整,並有所發揮。目前大概就摸了半顆ic的程度。心得也只是在公司看到的狀況,不代表整個園區,觀念也不一定正確
很感謝當初找我進來的主管還有罩我的學長,不然以我講話很直的狀況,應該會一直被打槍吧。
未來不是現在,看看有沒有軟體部門要收留我吧,感覺os和compiler、fw那裡還滿有趣的
| Column name | Description |
|---|---|
| CRn | Register number within the system control coprocessor |
| Op1 | Opcode_1 value for the register |
| CRm | Operational register number within CRn |
| Op2 | Opcode_2 value for the register |
| Name | Short form architectural, operation, or code name for the register |
| Reset | Reset value of register |
| Description | Cross-reference to register description |
| Function | CP15 Registers |
| System Configuration | c0 |
| System Control | c1 |
| Translation Base Control | c2 |
| Domain Access Control | c3 |
| Faults | c5/c6 |
| Cache Operations | c7 |
| TLB Operations | c8/c10 |
| Performance Monitor | c9 |
| L2 Control | c9 |
| Pre-load Engine | c11 |
| Interrupts | c12 |
| Process ID | c13 |
| Memory Arrays | c15 |
DMB instruction are observed before any explicit memory accesses that appear in program order after the DMB instruction. It does not affect the ordering of any other instructions executing on the processor.ISB are fetched from cache or memory, after the instruction has been completed. It ensures that the effects of context altering operations, such as changing the ASID, or completed TLB maintenance operations, or branch predictor maintenance operations, as well as all changes to the CP15 registers, executed before the ISB instruction are visible to the instructions fetched after the ISB.ISB instruction ensures that any branches that appear in program order after it are always written into the branch prediction logic with the context that is visible after the ISB instruction. This is required to ensure correct execution of the instruction stream.