What does your OS look like? (Screen Shots..)

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
User avatar
Combuster
Member
Member
Posts: 9301
Joined: Wed Oct 18, 2006 3:45 am
Libera.chat IRC: [com]buster
Location: On the balcony, where I can actually keep 1½m distance
Contact:

Re: Thins are coming along together

Post by Combuster »

Time to work on displaying that mp4 movie :)
<90' rotated image>
Tip of the day :wink:

(edit: posts moved; context added)
"Certainly avoid yourself. He is a newbie and might not realize it. You'll hate his code deeply a few years down the road." - Sortie
[ My OS ] [ VDisk/SFS ]
User avatar
Candy
Member
Member
Posts: 3882
Joined: Tue Oct 17, 2006 11:33 pm
Location: Eindhoven

Re: Thins are coming along together

Post by Candy »

mateuszb wrote:native intel graphics also working
Got sources or references for that?
User avatar
BASICFreak
Member
Member
Posts: 284
Joined: Fri Jan 16, 2009 8:34 pm
Location: Louisiana, USA

Re: What does your OS look like? (Screen Shots..)

Post by BASICFreak »

After an eye injury kept me from working on my kernel for a week, then a week of me not wanting to "start" on the kernel, I finally got a PCI PATA Driver!

Image

Turns out I was scared of this for nothing first try it was working on real hardware (took me longer to get bochs working)

Still need to add PCI Bus Search (the base is there just not implemented yet) and ATAPI and DMA...
I can see all Devices on 0x1F0 and 0x170 ATA controllers.

And unlike the FDC I didn't need to ask anything on the forums (at least thus far :wink: )

The command's inputs are [DRIVE] [STARTSEC] [COUNT] and ab28 cd are debug and 0x58 is status before reading buffer - just an FYI if someone was wondering.

Oh and thanks to this driver I just realized my HDD is on secondary and CDROM on primary controller on my test bed.
BOS Source Thanks to GitHub
BOS Expanded Commentary
Both under active development!
Sortie wrote:
  • Don't play the role of an operating systems developer, be one.
  • Be truly afraid of undefined [behavior].
  • Your operating system should be itself, not fight what it is.
zxm
Posts: 4
Joined: Sun Oct 07, 2012 2:42 pm

Re: What does your OS look like? (Screen Shots..)

Post by zxm »

I've got multitasking working on my raspberrypi os :)
Now I can work on VFS and EMMC driver.
Attachments
os.JPG
Peterbjornx
Member
Member
Posts: 116
Joined: Thu May 06, 2010 4:34 am
Libera.chat IRC: peterbjornx
Location: Leiden, The Netherlands
Contact:

Re: What does your OS look like? (Screen Shots..)

Post by Peterbjornx »

Added a framebuffer driver + console (modesetting done by GRUB)

Image
User avatar
Candy
Member
Member
Posts: 3882
Joined: Tue Oct 17, 2006 11:33 pm
Location: Eindhoven

Re: What does your OS look like? (Screen Shots..)

Post by Candy »

DSC_3515.jpg
And then it worked! On real hardware this time. No rtl8139 working because, mostly, it doesn't have one. Still looking for the first machine in this house with a 64-bit CPU and a realtek network card.
martinFTW
Posts: 15
Joined: Sun Jun 08, 2014 10:39 am
Contact:

Re: What does your OS look like? (Screen Shots..)

Post by martinFTW »

Peterbjornx wrote:Added a framebuffer driver + console (modesetting done by GRUB)

Image
How did you exactly get Grub modesetting working?(This site is down: https://www.southpatron.com/software/vbe-grub/ ). Grub modesetting sounds interesting to me. I know it is not the best way of supporting VESA, but I don't want to add VM86 support or some other ugly hacks to my microkernel.
Icee
Member
Member
Posts: 100
Joined: Wed Jan 08, 2014 8:41 am
Location: Moscow, Russia

Re: What does your OS look like? (Screen Shots..)

Post by Icee »

martinFTW wrote:Grub modesetting sounds interesting to me.
It's all written down quite nicely in the Multiboot specification, sections 3.1.2 and 3.1.4. The framebuffer address and pixel format will be passed to your kernel in the multiboot structure, fields starting from framebuffer_addr. These are not reflected in the specification, though, see multiboot.h.
martinFTW
Posts: 15
Joined: Sun Jun 08, 2014 10:39 am
Contact:

Re: What does your OS look like? (Screen Shots..)

Post by martinFTW »

Icee wrote:
martinFTW wrote:Grub modesetting sounds interesting to me.
It's all written down quite nicely in the Multiboot specification, sections 3.1.2 and 3.1.4. The framebuffer address and pixel format will be passed to your kernel in the multiboot structure, fields starting from framebuffer_addr. These are not reflected in the specification, though, see multiboot.h.
Thanks a lot. The framebuffer addr is not directly passed in the multiboot structure but the multiboot structure contains a two pointers ‘vbe_control_info’ and most important ‘vbe_mode_info’:
The fields ‘vbe_control_info’ and ‘vbe_mode_info’ contain the physical addresses of vbe control information returned by the vbe Function 00h and vbe mode information returned by the vbe Function 01h, respectively.
Inside of the vbe_mode_info structure there is a dword pointer at offset 0x28, which exactly, what we want.
User avatar
Jezze
Member
Member
Posts: 395
Joined: Thu Jul 26, 2007 1:53 am
Libera.chat IRC: jfu
Contact:

Re: What does your OS look like? (Screen Shots..)

Post by Jezze »

The vbe entry is usually filled with zeroes. If not, let me know cause that would be news to me.
Fudge - Simplicity, clarity and speed.
http://github.com/Jezze/fudge/
User avatar
Bender
Member
Member
Posts: 449
Joined: Wed Aug 21, 2013 3:53 am
Libera.chat IRC: bender|
Location: Asia, Singapore

Re: What does your OS look like? (Screen Shots..)

Post by Bender »

Applications can now call C code! The code below was written and compiled to a shared object file:

Code: Select all

#include <stdio.h>
#include <stdint.h>
uint32_t hello(void* arg)
{
	printf("hello from shared object\n");
	return 0;
}
and is called like this:

Code: Select all

include 'a32.inc'
; Yes we need an .so file
REQUIRE_SO = 1
so_init:
_start:
	NATIVE_CALL hello_lib, hello_proc, 0
	VM_EXIT  
_end_start:
_data:
hello_lib: DECLARE_NATIVE_LIB "./hello1.so"
hello_proc: DECLARE_NATIVE_PROC "hello"
_end_data:
_bss:
_end_bss:
Image
See the words "hello from shared object" on teh terminal? :) Guess it's time to write a few wrappers for it? eh? 8) Unfortunately, the functionality is quite limited, right now a function can only take "void *" as an argument and return an integer (32-bit only, because teh return value is in R0 which is 32-bit), need to work more on it!
"In a time of universal deceit - telling the truth is a revolutionary act." -- George Orwell
(R3X Runtime VM)(CHIP8 Interpreter OS)
iefserge
Posts: 3
Joined: Wed Jun 04, 2014 11:04 pm

Re: What does your OS look like? (Screen Shots..)

Post by iefserge »

Runtime.JS new terminal & shell

Image
Peterbjornx
Member
Member
Posts: 116
Joined: Thu May 06, 2010 4:34 am
Libera.chat IRC: peterbjornx
Location: Leiden, The Netherlands
Contact:

Re: What does your OS look like? (Screen Shots..)

Post by Peterbjornx »

testing: http://i.imgur.com/17EPa6a.png

with background:
Image
compositor running a test program, that 100x100 black square with a title bar is an app connected to the compositor
klange
Member
Member
Posts: 679
Joined: Wed Mar 30, 2011 12:31 am
Libera.chat IRC: klange
Discord: klange

Re: What does your OS look like? (Screen Shots..)

Post by klange »

Something like two years ago, someone nagged me for not having uniform close buttons on my window titlebars. Finally got around to moving my close button from a single app into the general decorations library, so now all decorated apps (that properly pass events through the decoration library) have a functional little × button.

Image
kutkloon7
Member
Member
Posts: 98
Joined: Fri Jan 04, 2013 6:56 pm

Re: What does your OS look like? (Screen Shots..)

Post by kutkloon7 »

Looks extremely neat :) Did you write the PDF viewer yourself?
Post Reply