OSDev.org

Posted: **Fri Jul 18, 2014 1:59 am**

Time to work on displaying that mp4 movie
<90' rotated image>

Tip of the day

(edit: posts moved; context added)

Posted: **Fri Jul 18, 2014 7:03 am**

mateuszb wrote:native intel graphics also working

Got sources or references for that?

Posted: **Fri Jul 18, 2014 11:23 pm**

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!

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

)

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.

Posted: **Sat Jul 19, 2014 10:40 pm**

I've got multitasking working on my raspberrypi os

Now I can work on VFS and EMMC driver.

Posted: **Sun Jul 20, 2014 7:29 pm**

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

Posted: **Mon Jul 21, 2014 2:23 pm**

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.

Posted: **Tue Jul 22, 2014 2:53 pm**

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

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.

Posted: **Wed Jul 23, 2014 4:21 am**

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.

Posted: **Wed Jul 23, 2014 8:46 am**

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.

Posted: **Wed Jul 23, 2014 9:01 am**

The vbe entry is usually filled with zeroes. If not, let me know cause that would be news to me.

Posted: **Sat Jul 26, 2014 5:02 am**

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:

See the words "hello from shared object" on teh terminal?

Guess it's time to write a few wrappers for it? eh?

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!

Posted: **Sun Jul 27, 2014 1:02 pm**

Runtime.JS new terminal & shell

Posted: **Mon Jul 28, 2014 12:50 pm**

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

with background:

compositor running a test program, that 100x100 black square with a title bar is an app connected to the compositor

Posted: **Fri Aug 01, 2014 10:52 pm**

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.

Posted: **Sat Aug 02, 2014 3:15 am**

Looks extremely neat

Did you write the PDF viewer yourself?

OSDev.org

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

Re: Thins are coming along together

Re: Thins are coming along together

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

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

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

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

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

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

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

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

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

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

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

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

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