2024-03-16 16:25:48 +00:00
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="generator" content="TempleOS V5.03">
2024-03-23 15:27:10 +00:00
<meta name="viewport" content="width=device-width, initial-scale=1">
2024-03-16 16:25:48 +00:00
<link rel="stylesheet" href="/style/templeos.css">
<script src="/script/templeos.js"></script>
<style type="text/css">
.cF0{color:#000000;background-color:#ffffff;}
.cF1{color:#0000aa;background-color:#ffffff;}
.cF2{color:#00aa00;background-color:#ffffff;}
.cF3{color:#00aaaa;background-color:#ffffff;}
.cF4{color:#aa0000;background-color:#ffffff;}
.cF5{color:#aa00aa;background-color:#ffffff;}
.cF6{color:#aa5500;background-color:#ffffff;}
.cF7{color:#aaaaaa;background-color:#ffffff;}
.cF8{color:#555555;background-color:#ffffff;}
.cF9{color:#5555ff;background-color:#ffffff;}
.cFA{color:#55ff55;background-color:#ffffff;}
.cFB{color:#55ffff;background-color:#ffffff;}
.cFC{color:#ff5555;background-color:#ffffff;}
.cFD{color:#ff55ff;background-color:#ffffff;}
.cFE{color:#ffff55;background-color:#ffffff;}
.cFF{color:#ffffff;background-color:#ffffff;}
</style>
</head>
<body>
2024-03-23 13:40:50 +00:00
<pre style="font-family: courier, monospace; font-size: 10pt;">
2024-03-16 16:25:48 +00:00
<a name="l1"></a><span class=cF5> Why Not More?</span><span class=cF0>
<a name="l2"></a>
<a name="l3"></a>If a feature cannot be made to work correctly and consistently, professional
<a name="l4"></a>companies usually remove the feature. Because PC hardware is so diverse,
<a name="l5"></a>getting things to work on all people's computers is really difficult. For one
<a name="l6"></a>thing, you practically have to own all the different hardware to write drivers
<a name="l7"></a>for it. If a company wanted to sell a PC operating system, they would offer a
<a name="l8"></a>warranty and, therefore, could not get away with amateur behavior. TempleOS
<a name="l9"></a>absolutely requires 64-bit computers, so we leave behind much trouble, but
<a name="l10"></a>plenty remains.
<a name="l11"></a>
<a name="l12"></a>The PCI bus interface is what modern hardware uses. Before PCI, life was simple
2024-03-23 13:40:50 +00:00
<a name="l13"></a>and devices used I/O ports. After studying </span><a href="/Wb/Demo/Lectures/PCIInterrupts.HC#l1"><span class=cF4>PCI Interrupts</span></a><span class=cF0> and attempting to do
2024-03-16 16:25:48 +00:00
<a name="l14"></a>a HDAudio driver, I came to realize that modern PCI devices require ten times
<a name="l15"></a>more code and I cannot even come close to making them work on everyone's machine
<a name="l16"></a>because with PCI devices there are several models to worry about, unlike with
<a name="l17"></a>the older ISA bus devices which can be done with one driver.
<a name="l18"></a>
<a name="l19"></a>Currently, I have no PCI drivers. My drivers use I/O ports and operate in ISA
<a name="l20"></a>bus mode. At this point, I only have one driver for each type of device and it
2024-03-23 13:40:50 +00:00
<a name="l21"></a>is delightfully simple that way. I have one </span><a href="/Wb/Kernel/SerialDev/Keyboard.HC#l1"><span class=cF4>keyboard</span></a><span class=cF0> driver, one </span><a href="/Wb/Kernel/SerialDev/Mouse.HC#l1"><span class=cF4>mouse</span></a><span class=cF0> driver,
<a name="l22"></a>one </span><a href="/Wb/Kernel/BlkDev/DskATA.HC#l1"><span class=cF4>ATA hard drive</span></a><span class=cF0> driver, one </span><a href="/Wb/Kernel/BlkDev/DskATA.HC#l1"><span class=cF4>ATAPI CD/DVD</span></a><span class=cF0> driver, one </span><a href="/Wb/Adam/Gr/GrScrn.HC#l1"><span class=cF4>VGA 640x480 16 color</span></a><span class=cF0>
<a name="l23"></a>video driver and one </span><a href="/Wb/Kernel/KMisc.HC#l179"><span class=cF4>PC Speaker</span></a><span class=cF0> driver. I use the </span><a href="/Wb/Kernel/KMain.HC#l89"><span class=cF4>PIT and HPET timers</span></a><span class=cF0> and </span><span class=cF4>
<a name="l24"></a></span><a href="/Wb/Kernel/KInts.HC#l129"><span class=cF4>PIC Interrupt Controller</span></a><span class=cF0>. I use IRQ0 for timer, IRQ1 for keyboard, and IRQ12
2024-03-16 16:25:48 +00:00
<a name="l25"></a>for mouse. If IRQ12 is not firing, I am able to poll the mouse.
<a name="l26"></a>
2024-03-23 13:40:50 +00:00
<a name="l27"></a>In the CPU department, I have state of the art 64-bit </span><a href="/Wb/Kernel/KStart64.HC#l1"><span class=cF4>long mode</span></a><span class=cF0> with </span><a href="/Wb/Kernel/MultiProc.HC#l1"><span class=cF4>multicore</span></a><span class=cF0>
<a name="l28"></a>support. I use the </span><a href="/Wb/Kernel/MultiProc.HC#l171"><span class=cF4>APIC</span></a><span class=cF0> and start-up </span><a href="/Wb/Kernel/MultiProc.HC#l283"><span class=cF4>multicore</span></a><span class=cF0> operation.
2024-03-16 16:25:48 +00:00
<a name="l29"></a>
<a name="l30"></a>I have made an incredible accomplishment by getting it to work on practically
<a name="l31"></a>everyone's computer as long as it is 64-bit and they run inside VMware, QEMU or
<a name="l32"></a>VirtualBox.
<a name="l33"></a>
<a name="l34"></a>Adding a USB driver would be really ugly with UHCI, EHCI, OHCI, USB1, USB2,
<a name="l35"></a>USB3, ICH6, ICH7, ICH8, ICH9, ICH10, ICH11, ICH12, boot mode and regular mode
<a name="l36"></a>for keyboard/mouse and a diversity of HID reports. It's hopeless. I could
<a name="l37"></a>never offer anything but crappy, limited support and it would just add a ton of
<a name="l38"></a>crappy code that mostly didn't work. What would I gain? Nothing. A keyboard
<a name="l39"></a>or mouse would not be improved. Solid State USB drives would be really nice,
<a name="l40"></a>but it's not going to happen.
<a name="l41"></a>
<a name="l42"></a>The same story is basically true for GPUs, audio, networking and AHCI hard drive
<a name="l43"></a>drivers. God said 640x480 16 color was a covenant like circumcision, so the
2024-03-23 13:40:50 +00:00
<a name="l44"></a>video will never change, even if a </span><a href="/Wb/Doc/StdTempleOSPC.DD.HTML#l1"><span class=cF4>Standard PC</span></a><span class=cF0> was made. If you attempt
2024-03-16 16:25:48 +00:00
<a name="l45"></a>multimedia, everything will break because memory will get fragmented with huge
<a name="l46"></a>multimedia files. Some day, if super-simple high speed serial allows
<a name="l47"></a>networking, there will be no browser within the 100,000 line limit and, with
<a name="l48"></a>only 16 colors, the world wide web is not tolerable. FTP and telnet might be
<a name="l49"></a>possible, in the far distant future, if they could fit within the 100,000 line
<a name="l50"></a>limit. Currently, there are 80,849 lines of code.
<a name="l51"></a>
<a name="l52"></a>I don't stand a chance working on native hardware, anymore. I could install and
<a name="l53"></a>run natively on hardware from about 2005-2010. It requires BIOS's being nice
<a name="l54"></a>enough to write USB mode PS/2 legacy keyboard/mouse support. As it turns-out,
<a name="l55"></a>sometimes the BIOS has PS/2 drivers but purposely disables them, just to be
<a name="l56"></a>mean. The CIA and whole industry is trying to mess everything up, on purpose.
<a name="l57"></a>Perhaps, at a point of sale in a store, a thief could hack a credit card
<a name="l58"></a>machine. Therefore, the BIOS companies actually want it difficult to make
<a name="l59"></a>drivers and purposely make it broken.
<a name="l60"></a>
2024-03-23 13:40:50 +00:00
<a name="l61"></a>The ATA/ATAPI hard drives often can be run with I/O ports if you can </span><a href="/Wb/Kernel/BlkDev/DskATAId.HC#l1"><span class=cF4>find them</span></a><span class=cF0>. </span><span class=cF2>
2024-03-16 16:25:48 +00:00
<a name="l62"></a>lspci -v</span><span class=cF0> on Linux or system information on Windows can help you locate the SATA
<a name="l63"></a>IO ports the hard drive and CD/DVD have. They no longer are enabled by the
<a name="l64"></a>BIOS. It's hopeless. I'm stuck with very slow drive performance, but it works
<a name="l65"></a>for everybody.
<a name="l66"></a>
<a name="l67"></a>UEFI is pointless. If I am forced to run in VMware, QEMU or VirtualBox, they
<a name="l68"></a>will always support non-UEFI mode. Without working, native hard drive and
<a name="l69"></a>CD/DVD drivers, you can't get very far with UEFI on a native install, not to
<a name="l70"></a>mention SecureBoot. UEFI is, first of all, redundant. If non-UEFI works in a
<a name="l71"></a>virtual machine, supporting UEFI would only be redundant, ugly nasty code. My
<a name="l72"></a>compiler does not create an ELF or PE format. I would have to ruin the beauty
<a name="l73"></a>of my compiler, which would make me cry many tears.
<a name="l74"></a>
<a name="l75"></a>God talks. It seems reasonable that I will get to make the rules for the whole
<a name="l76"></a>industry, in the future when God is announced publically to the World.
<a name="l77"></a>
2024-03-23 13:40:50 +00:00
<a name="l78"></a>I made </span><a href="/Wb/Doc/Demands.DD.HTML#l1"><span class=cF4>::/Doc/Demands.DD</span></a><span class=cF0>.
2024-03-16 16:25:48 +00:00
<a name="l79"></a>
<a name="l80"></a>When the PC was created, they wanted flexibility because they did not know the
<a name="l81"></a>future. Now, the industry is mature and it is time to make a 100% standard PC
2024-03-23 13:40:50 +00:00
<a name="l82"></a>that everybody uses. </span><a href="/Wb/Doc/StdTempleOSPC.DD.HTML#l1"><span class=cF4>::/Doc/StdTempleOSPC.DD</span></a><span class=cF0>
2024-03-16 16:25:48 +00:00
<a name="l83"></a>
<a name="l84"></a></span><span class=cF8>
<a name="l85"></a>* "QEMU" is a trademark owned by Fabrice Bellard.
<a name="l86"></a>* "VMware" is a trademark owned by VMware, Inc.
<a name="l87"></a>* "VirtualBox" is a trademark owned by Oracle.
</span></pre></body>
</html>
