Forums - Open Redstone Engineers
Firmwares, Kernels, Drivers, OS'es, im lost :O - Printable Version

+- Forums - Open Redstone Engineers (https://forum.openredstone.org)
+-- Forum: Off-Topic (https://forum.openredstone.org/forum-4.html)
+--- Forum: Off-Topic Discussion (https://forum.openredstone.org/forum-5.html)
+--- Thread: Firmwares, Kernels, Drivers, OS'es, im lost :O (/thread-1050.html)



Firmwares, Kernels, Drivers, OS'es, im lost :O - EDevil - 09-24-2013

EPIC SPOILER ALERT! Dont think for a minute that i want to try extreme forms of coding or anything (making my own os or something), im just curious.

So, here in MC is very simple. Each of our "computers" work with machine code, and a bunch of rom. Thats it. But after going on the beloved place called the internet, i found a bunch of terms (that i already know) but now want to learn more of. So, simple first question, what comes first, 2nd, last etc.? Like, you start with your ROM & machine code, and end with your complete OS (correct me here if im wrong), and somewhere you got drivers, kernels (i think) and firmware stuffs(once again, not sure about this. Thats why im asking you! Yes, you! Sitting on your fancy chair in front of your computaa). Ow, and did i miss some other things, that aren't highlighted in the title? Thanks in advance!


RE: Firmwares, Kernels, Drivers, OS'es, im lost :O - tokumei - 09-24-2013

I'll try to explain how it all works for you.
In a real computer, the whole system is run by the motherboard and the processor. The motherboard has BIOS software in a ROM databank, which essentially tells it how to run everything and boot the operating system.

On the motherboard there usually are sockets for PCI(e) cards, hard drives, USB devices, graphics/sound ports, and of course the CPU. Most of the time, the motherboard will read the boot data (can come from CDs/floppys, hard drives or USB storage devices) and send it to the CPU.

From there, the CPU will take control and can use the motherboard to communicate to the other components. The CPU uses a library of files called 'drivers' that tells it how to communicate with different USB and PCI devices, since they all that've their own functions. (I don't know anything about kernels, so don't ask me.)

From there, the processor can load other files with machine code in an attempt to make an operating system if that's what's in the boot code.

That's my take on it, it might be a bit different, but that's the closest I can get. Hope this helps!