Guessing from the title you probably know what this is about. I have recently designed my own motherboard layout in Paint.NET. With that said, it needs something to program it with, right? So I came up with a language that I call OOPL, an acronym for Object Oriented Processor Language. It's one step higher than Assembly, and not nearly as confusing as its procedural counter-part. The language, on current platforms and actual hardware, will compile to assembly, then down to binary. Put quite simply, the mother board does not use a CPU, it uses a Central Data Hub, and within are some registers that regulate, where the data should go. The Generic Processing Unit is customizable via firmware that can be accessed from the pre-installed firmware. You can't really call it a CPU because it isn't the Central Processing Unit, it just moves things from one place to another using four DBIs (Data Bus Interfaces) which are a configurable firmware. Just like a CPU, the GePU(GPU would be confusing) can be overclocked. Now I've named this motherboard EvilMotherboard. I'll tell you why: there are four sections on the motherboard, each devoted to doing a specific task: Memory, Graphics, HCI, and IO. The memory consists of SSD and HDD interfaces, different kinds to maximize modularity. The graphics consists of four GPU slots. The IO contains drivers for HCI as well as other peripherals. The HCI contains the Operating System. It is a RAM Disc containing whichever OS you decide to put on it. The OS has to recognize the kernel which is in the Central Data Hub. Otherwise you can manually configure the kernel to the specifications of the OS or the OS can automatically configure the kernel firmware (in all honesty, Im trying to make a motherboard that is modular in both hardware AND software). Hopefully I find a better blogging area other than pastebin because that's just a pain. This is all speculation right now, but I have a motherboard layout that I speculated and drew in Paint.NET(TM).
Comments