Instruction Set - Printable Version +- Forums - Open Redstone Engineers (https://forum.openredstone.org) +-- Forum: ORE General (https://forum.openredstone.org/forum-39.html) +--- Forum: Projects & Inventions (https://forum.openredstone.org/forum-19.html) +---- Forum: In Progress (https://forum.openredstone.org/forum-20.html) +---- Thread: Instruction Set (/thread-10324.html) Pages:
1
2
|
RE: Instruction Set - Koyarno - 07-18-2016 last question: What kind of instruction memory do you use? i myself got a cache system and tuchi if you want to look up some. I'm on vacation on my laptop so i'm a bit handicapped right now. Also you can re arrange that immidiate control bit to right after the opcode, It makes the last 8 bits clean for a immidiate. Operand D seems to be just miscelanious to the opcode. Oh nevermind i saw the constant opcode, it seems fine really RE: Instruction Set - MW3_587786 - 07-25-2016 k den RE: Instruction Set - LordDecapo - 07-28-2016 (07-17-2016, 03:49 PM)Koyarno Wrote: 1. the units are physically separate except for storage, I/O and they do not share the same address space (im talking von neumann ofc). Pst, that's multi CPU not Multicore Your 2 was spot on tho (07-17-2016, 06:54 PM)Matthijs de bruijn* Wrote: My idea behind more cores was you can run an os and an other program on the same time, but if i only do one core wich is simpler, i have to multitask, it wil be done by the os, and it is basicaly calling subroutines wich are programs. And i also am going to make my cpu pipelined wich make it much faster. do i need extra instructions for that? Advice: don't limit yourself to 1 IS, don't be afraid to realize u messed something up and change it or start from scratch in between CPUs. Read bottom of reply for stuff on ur OS ideas. (07-17-2016, 07:12 PM)Koyarno Wrote: Don't overdo it one step at a time plz YES^^ before you jump right into making a multicore pipeline system with an OS... make sure you can make a basic CPU, then one tthat is Pipelined, then learn cache and cache coherency. Lastly, get a basic Kernel (lower level name/system of an OS) that works on a single pipelined core well before you think of making a multicore kernel system. There are so many things you haven't gotten to yet that are critical to multicore functionality which have a basis in single core kernel functions I.E. Thread scheduling, memory protection, exception handling etc. PS. Hi, I'm the LordDecapo that was mentioned. I'm currently working on my 21st CPU architecture using my like 100th IS. And am just now trying to get into kernel/OS development, it's a lot more complex then you may be thinking it is. Reply to this aasking about Minora if you are interested in my current design and why I'm approaching it the way I am. (07-18-2016, 06:14 AM)Matthijs de bruijn* Wrote: https://docs.google.com/spreadsheets/d/1YrQRyKM3jy-w2YQJn46C-PnkPU55uEjxiy5ThXXFHwo/edit?usp=sharing As I mentioned above, learning about thread scheduling, pipelines, and other things like Interrupts and types of intterupts would help you tremendously in these endeavours of yours. Abstracting a user interface that is even remotely user friendly can be a very tedious task. Involving making many many different sub functions in the kernel to handle the vast amounts of situations tthat can arise dduring normal system operations. |