See also my RISC OS related site.
YANGTOS MicroKernel OS : News
Home News Docs Links
Most Recent:

Nov-26-2018 (A): As it says on the front page for this project, this is a low priority project at this time. Well I really need to catch up on the RISC OS stuff I am working on, so I will likly let this site (and the source on my drive) sit where they are for a short while, so I may catch up on my higher priority projects. Be back in a week or two (maybe less we will see).

Nov-25-2018 (B): I must apologize for how long it is taking me to get the source up. It takes more time to document everything on the site than it takes to design the OS and write the source, and as this is a project to help teach (as well as to help me learn by teaching) I have to get the site documentation up to somewhere close to the state of the code before I upload. I am working on it, at the same time as I am cleaning up the code and checking for bugs/errors in the code (as it helps me to document the system if I am going through the code as I do so).

Nov-25-2018 (A): I am still cleaning everything up, including the site. I am going to be breaking the documents among multiple pages, and have changed the page layout for the site slightly to make the use of sub-pages a bit simpler for those that may stop by. So far everything is still on the main docs page, though that will get broken up as I add more documentation.

Nov-24-2018 (b): As I am cleaning up the existing source tree, and playing around a little, I decided to make some changes in the goals, as well as the kernel design. I am adding builtin support for a RAM disk and a simple file system to go with it to the kernel, thus simplifying loading some modules at startup. I am also changing the primary target to being able to load enough RISC OS modules correctly in order to run some RISC OS software (droping the BSD target).

Nov-24-2018 (A): It turns out I was wrong, my Raspberry Pi 3B is alive again :) .

Nov-23-2018 (A): Decisions, My only multicore ARM board died, a Raspberry Pi 3B. So I am not able to test any SMP stuff anylonger. The only thing I can do is focus on the single core target, and keep the SMP and ARMv8 specific code set aside until I can finish verifying it. So I guess that for now everything will be Running on a Raspberry Pi B+.

Nov-22-2018 (A): I am working on making sure that all of the code is correct, not only in function though also according the expected ways of doing things. I am cleaning up the code as I go and will be posting source archives as I go, for now just one source archive, that will grow as more of the source gets added to it. This is needed, along with all the documentation, so I am doing it while I am not doing much for coding other than working a bit on a simple scene demo.

Nov-22-2018 (A): While I will continue to expand the work on SMP and using the ARMv8 in AARCH32 as it is now known, that is normal ARM mode, I am going to be primarily focused on supporting the ARMv6 as used in the Raspberry A/A+/B/B+/Zero/ZeroW. The reason for this choice is that I am attempting to show people the correct way, including how to minimize bloat without sacrificing any functionality, so the lower speed CPU with less attached RAM is a better target.

Nov-21-2018 (A): Well the SMP is back. Last night I did a quick experiment on how to correctly boot either single core or SMP, and correctly assign the correct check routines for the difference at startup. So if we boot on a multi-Core Raspberry Pi it runs single core, if we boot on a multi-core Raspberry Pi it runs full SMP. Now I have to re-update the documentation.


Nov-20-2018 (C): I did not realy get anything done today. At least nothing significant, just removed the support for SMP, made sure it still boots, updated the site a little, and did a little research to help plan the path forward.

Nov-20-2018 (B): I have removed support for SMP for now. It will come back at a later time, though I realised that there is a need to support single core systems first. It would be better to support all models of Raspberry Pi, as this gives a slightly broader base from which to port to other ARM based systems. I am updating the other documentation to reflect the lack of SMP as well (and will have to update again when SMP support comes back).

Nov-20-2018 (A): I changed the scheduling algorithm to something that is arguably a little better. See the Kernel Overview document in the Docs section.

Nov-19-2018 (C):I added the beggining of the Kernel Overview document. See the Docs page.

Nov-19-2018 (B):I have updated the site to be better organised so that I can begin to get the documentation done, as well as moving towards releasing the source code and compiled versions for this project.

From Before I Added a News Page:

  • Nov-19-2018 (A): I have added the documents page, and put a nav-bar across the top of each page. Now I have a place to put documentation of the OS, and I will release the source that is done as I get it documented. Further progress will keep documentation in step with the code. I also intend to add a News page to replace this Progress box.
  • Nov-18-2018 (C): Progress is going to slow down while I add the license to the source code, write documentation describing how the completed portions work (which is going to require writing a simple C2HTML utility for RISC OS), and get the site cleaned up with more pages.
  • Nov-18-2018 (B): Last night I got a simple module loaded, to perform console output to the screen. As such I had to think about the format for a module, and I am going with a format that is compatible with RISC OS modules (why reinvent the wheel), with a couple of added extensions to the format. This probably should have been posted yesterday.
    The console output to framebuffer display module (conout0RPi) was binary dumped into the kernel image so that the kernel can just memcopy it to its own space, setup the privileges in the page tables, and start it up. This module only uses a minimum of messages.
  • Nov-18-2018 (A): The site work that was supposed to happen yesterday is put off until today, as I had to attend a friends memorial service yesterday.
    I am probably not going to get a lot done today. I have to many other things in the queue. This project has a name. YANGTOS stands for Yet ANother Goliath Tiny Operating System. YANGTOS is pronounced like bang toss with a Y sound instead of the leading B.
    Credit for the name goes to Burngate on the RPi forums recommending Goliath, and the rest just fell into place after a nights sleep.
    YANGTOS will be distributed under a 2 clause BSD license.
  • Nov-17-2018 (A): Began laying out other pages for this site, so that I can provide better information on progress, downloads, and good descriptions of the functionality of each part of the code.
  • Nov-16-2018 (B):I got the first successful boot, with MMU up, all 4 cores, cache enabled. Does not do anything yet, though a decent start. I am surprised that I was to get that much that quickly
  • Nov-16-2018 (A): Formally stated the concept for this OS. Having only previously had vauge concepts about where to go with it.

This page created and maintained on RISC OS using !Zap.
Copyright 2018 David Cagle (AKA DavidS).