What does your OS look like? (Screen Shots..)
Re: What does your OS look like? (Screen Shots..)
managarm running kmscube on Mesa DRI + softpipe (this is not using Mesa's offscreen rendering like all other hobby OS do).
managarm's roadmap to Wayland:
✓ DRM drivers for Bochs and virtio graphics
✓ libdrm
✕ virtio hardware rendering
✓ Mesa (including GBM and EGL)
✕ libudev
✕ Weston
managarm's roadmap to Wayland:
✓ DRM drivers for Bochs and virtio graphics
✓ libdrm
✕ virtio hardware rendering
✓ Mesa (including GBM and EGL)
✕ libudev
✕ Weston
managarm: Microkernel-based OS capable of running a Wayland desktop (Discord: https://discord.gg/7WB6Ur3). My OS-dev projects: [mlibc: Portable C library for managarm, qword, Linux, Sigma, ...] [LAI: AML interpreter] [xbstrap: Build system for OS distributions].
Re: What does your OS look like? (Screen Shots..)
Added C++ exceptions support :
My C++ OS Project : https://github.com/Stellaris-code/LudOS
FAT read support, Tar, VESA, AHCI, PIO IDE, along with a basic shell !
FAT read support, Tar, VESA, AHCI, PIO IDE, along with a basic shell !
- DeezRamChips
- Member
- Posts: 132
- Joined: Fri Apr 08, 2016 5:03 am
- Location: atapio.cpp - why won't you work :(
- Contact:
Re: What does your OS look like? (Screen Shots..)
he he, looks like I had the excact same idea for the look of my panic screenStellaris wrote:Added C++ exceptions support :
My github page: https://github.com/AlexandreRouma
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Re: What does your OS look like? (Screen Shots..)
I don't have an OS (yet?), but I've been thinking of making something small and simple to showcase my C compiler in an unusual/new environment (not much new/unusual in DOS, Windows, Linux or MacOS).
And there you go, someone just did it!
They took my compiler and my friend's assembler and linker from RetroBSD (AKA BSD 2.11) and squeezed them into a smaller PIC32 MIPS microcontroller (64KB RAM, 256KB Flash) and now we have a ROM BASIC, er, scratch that, Flash C system!
Video1:
Video2:
And there you go, someone just did it!
They took my compiler and my friend's assembler and linker from RetroBSD (AKA BSD 2.11) and squeezed them into a smaller PIC32 MIPS microcontroller (64KB RAM, 256KB Flash) and now we have a ROM BASIC, er, scratch that, Flash C system!
Video1:
Video2:
Re: What does your OS look like? (Screen Shots..)
I guess that compiler is useful by now :v
For those trying to figure out the relevant specs (since trying to sort it out from the PIC32 specs along side everything else can be somewhat confusing):
For those trying to figure out the relevant specs (since trying to sort it out from the PIC32 specs along side everything else can be somewhat confusing):
- MIPS at 50MHz
- 256KB ROM
- 64KB RAM
- Both text and graphics mode
- Graphics mode is 256×224 4bpp
- Audio playback seems to use DMA
Re: What does your OS look like? (Screen Shots..)
It's been useful (or usable?) for a while now. "While" depending on what you want/need. Mac OS X support is recent and so is float support in scanf() and strtod(). Unreal mode support has been there for a year. Proper preprocessor (ucpp) has been included for about a year and a half. Floats were added two years ago. DPMI support is even older. Linux and Windows support were added three years ago. MIPS support (in RetroBSD) is some four years old.Sik wrote:I guess that compiler is useful by now :v
Yeah, graphics without dedicated on-display memory is expensive. Especially on this lower-end chip. RetroBSD runs on a chip with 128KB RAM, 512KB Flash at 80MHz.Sik wrote:For those trying to figure out the relevant specs (since trying to sort it out from the PIC32 specs along side everything else can be somewhat confusing):
Graphics mode eats up nearly half the RAM though (which means no double buffering hence why the screen flickers badly in the second video).
- MIPS at 50MHz
- 256KB ROM
- 64KB RAM
- Both text and graphics mode
- Graphics mode is 256×224 4bpp
- Audio playback seems to use DMA
There are better MIPS microcontrollers. Like the PIC32MZ series with up to 512KB RAM running at 200 MHz (also has an FPU, can have external memory and much more).Sik wrote:The microcontroller can come in several speeds so I had to look up at the pic to see the exact model in use. The speed certainly makes software rendering easy enough, though I guess the memory limit is still a pain.
Re: What does your OS look like? (Screen Shots..)
Interesting. hardware is too limited though. I am more comfortable with mini PCs. Do you have CI20 board, Alex?
Re: What does your OS look like? (Screen Shots..)
I have been using it for my loader code. In fact, my whole loader.sys file is built with SmallerC. Most of the code is C with a little bit of Asm.alexfru wrote:It's been useful (or usable?) for a while now.Sik wrote:I guess that compiler is useful by now :v
I have even had some of my readers ask me questions about SmallerC and why they can't get their code to work. With a few modifications to their code, their loaders work just fine, compiled with SmallerC.
Ben
http://www.fysnet.net/osdesign_book_series.htm
Re: What does your OS look like? (Screen Shots..)
Occasionally running AOSP ART tests on one at work. If you have enough RAM and storage, you can compile larger pieces of code with Smaller C (e.g. itself) and then use binutils for MIPS to make binaries (this is exactly how I test MIPS support in the compiler).zaval wrote:Interesting. hardware is too limited though. I am more comfortable with mini PCs. Do you have CI20 board, Alex?
Re: What does your OS look like? (Screen Shots..)
Yeah, was saying it more like "proven" (as in, actually seen proper use outside its original scope).alexfru wrote:It's been useful (or usable?) for a while now. "While" depending on what you want/need. Mac OS X support is recent and so is float support in scanf() and strtod(). Unreal mode support has been there for a year. Proper preprocessor (ucpp) has been included for about a year and a half. Floats were added two years ago. DPMI support is even older. Linux and Windows support were added three years ago. MIPS support (in RetroBSD) is some four years old.Sik wrote:I guess that compiler is useful by now :v
Re: What does your OS look like? (Screen Shots..)
nicey GUI, mariusz! very XP-ish. great work, inspiring results.
Re: What does your OS look like? (Screen Shots..)
Looks like the screenshot I posted was also moved, could it be moved back?zaval wrote:nicey GUI, mariusz! very XP-ish. great work, inspiring results.
Re: What does your OS look like? (Screen Shots..)
Added terminal background image support :
My C++ OS Project : https://github.com/Stellaris-code/LudOS
FAT read support, Tar, VESA, AHCI, PIO IDE, along with a basic shell !
FAT read support, Tar, VESA, AHCI, PIO IDE, along with a basic shell !
Re: What does your OS look like? (Screen Shots..)
SUCCESS!
After hours of toiling I finally cracked the nut that is VESA and fonts.
Here is a single line of text in 1024x768 glory.
After hours of toiling I finally cracked the nut that is VESA and fonts.
Here is a single line of text in 1024x768 glory.
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: What does your OS look like? (Screen Shots..)
I haven't posted here for a really long time, and xOS is inactive but I am working on a rewrite of it in C. Hopefully I can reach the same stage. Anyway, I was looking back at my GitHub commits, and decided why not?
xOS looked like this in its first commit. Each window is in its own task.
And this was its first image background. I still like this image, though.
Cheers!
xOS looked like this in its first commit. Each window is in its own task.
And this was its first image background. I still like this image, though.
Cheers!
You know your OS is advanced when you stop using the Intel programming guide as a reference.