Difference between revisions of "User:JSharp"
Jump to navigation
Jump to search
m (+samsung memory size) |
m (%s/mendax/verus) |
||
| (21 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* twitter.com/justinrwlynn | * twitter.com/justinrwlynn | ||
| − | == | + | == .plan == |
| − | + | * Mine/Review [https://openpowerfoundation.org/openpower-summit-2016/] for additional documentation | |
| + | * Also Mine/Review [http://developercongress2017.openpowerfoundation.org/presentations/] | ||
| + | ** Especially [http://developercongress2017.openpowerfoundation.org/wp-content/uploads/2017/05/Part3-On-Chip-Controller-OCC-Tutorial-1.pdf OCC Tutorial](!) Heaps of good stuff there. | ||
| − | + | === Projects (in order of interest/work likelihood) === | |
| − | + | * [[User:JSharp/Verax|Verax T2 Cluster System (w/ Coreboot-powered x86 Isolated Acceleration)]] | |
| − | + | * [[User:JSharp/Verus|Verus OpenPOWER POWER9 Portable Workstation]] | |
| − | * | + | * [[User:JSharp/oVRMc|oVRMc Open Source Multiphase PMBus/AVSBus POWER9-compatible Voltage Regulation Module Controller (open VRM controller)]] |
| − | + | * [[User:JSharp/PowerLine|cycle/bus/transaction accurate simulation of the (POWER9/T2 SoC IPL) for FW development/verification]] | |
| − | + | ** Design, Implementation and Verification of a cycle/bus accurate simulation of the POWER9/T2 IPL for use in systems firmware development and verification. I haven't been able to find an existing method for fully simulating systems firmware deployment and execution not involving actual hardware and support infrastructure. Ideally, physical hardware would be used only for model verification. More research on exist methods of development required. | |
| − | + | * [[User:JSharp/Durania|formally verified re-implementation of OpenPOWER equivalent P9 SoC firmware]] | |
| − | * | + | ** Formal verification of low-level systems firmware is vital for stability, security and algorithm correctness. Do so via re-implementation of OpenPOWER provided firmware equivalent POWER9 SoC firmware specifications/build systems using Ivory/Tower eDSL Models enhanced with LiquidHaskell refinement type system. Use Simulation to validate equivalent initialisation and run-time behaviour versus OpenPOWER provided firmwares. |
| − | * | ||
| − | * | ||
| − | * | ||
| − | * | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | * | ||
| − | |||
| − | ** | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 02:40, 20 November 2018
Hi There. I'm a Systems Engineer and Hobbyist.
My other social media accounts
- twitter.com/justinrwlynn
.plan
- Mine/Review [1] for additional documentation
- Also Mine/Review [2]
- Especially OCC Tutorial(!) Heaps of good stuff there.
Projects (in order of interest/work likelihood)
- Verax T2 Cluster System (w/ Coreboot-powered x86 Isolated Acceleration)
- Verus OpenPOWER POWER9 Portable Workstation
- oVRMc Open Source Multiphase PMBus/AVSBus POWER9-compatible Voltage Regulation Module Controller (open VRM controller)
- cycle/bus/transaction accurate simulation of the (POWER9/T2 SoC IPL) for FW development/verification
- Design, Implementation and Verification of a cycle/bus accurate simulation of the POWER9/T2 IPL for use in systems firmware development and verification. I haven't been able to find an existing method for fully simulating systems firmware deployment and execution not involving actual hardware and support infrastructure. Ideally, physical hardware would be used only for model verification. More research on exist methods of development required.
- formally verified re-implementation of OpenPOWER equivalent P9 SoC firmware
- Formal verification of low-level systems firmware is vital for stability, security and algorithm correctness. Do so via re-implementation of OpenPOWER provided firmware equivalent POWER9 SoC firmware specifications/build systems using Ivory/Tower eDSL Models enhanced with LiquidHaskell refinement type system. Use Simulation to validate equivalent initialisation and run-time behaviour versus OpenPOWER provided firmwares.
