toku-sa-n / ramen Goto Github PK

View Code? Open in Web Editor NEW

39.0 3.0 4.0 3.67 MB

A toy OS written in Rust supporting xHCI.

License: GNU General Public License v3.0

Makefile 1.83% Rust 98.17%

rust os x86-64 uefi

ramen's Introduction

ramen

A toy OS

Requirements

A computer supporting UEFI or QEMU
mtools (if you want to run on QEMU)
OVMF_VARS.fd and OVMF_CODE.fd (if you want to run on QEMU)
Rustup nightly version

Run on QEMU

How to get `OVMF_VARS.fd` and `OVMF_CODE.fd`

For Gentoo users:

sudo USE="binary" emerge sys-firmware/edk2-ovmf
cp /usr/share/edk2-ovmf/{OVMF_VARS.fd,OVMF_CODE.fd} /path/to/ramen

Execution

git clone https://github.com/toku-sa-n/ramen
cd ramen
rustup override set nightly
make run

Run on your computer

You have to create an EFI partition.

Then run the following command:

git clone https://github.com/toku-sa-n/ramen.git
cd ramen
rustup override set nightly
make
USB_DEVICE_PATH="/dev/sdx1" make copy_to_usb

(/dev/sdx1 is the EFI partition you created.)

Execution

Reboot your machine and run Ramen OS.

License

GPL-3.0 or later. See LICENSE.

(This image is not related to the project.)

ramen's People

Contributors

Stargazers

Watchers

Forkers

zzhgithub monarrk oslist jakubgawron1

ramen's Issues

Update README.md

You no longer need cargo-xbuild. Also, you can run RamenOS without installing it on USB memory. Instead you can boot on QEMU. Add an instruction to run RamenOS on QEMU.

Remove `init` module

The content of this module can be moved to main.rs.

Dependabot couldn't find a Cargo.toml for this project

Dependabot couldn't find a Cargo.toml for this project.

Dependabot requires a Cargo.toml to evaluate your project's current Rust dependencies. It had expected to find one at the path: /,kernel/,bootx64/,common_items/Cargo.toml.

If this isn't a Rust project, or if it is a library, you may wish to disable updates for it from within Dependabot.

View the update logs.

limit of lidt should be u16

Initialize paging before exiting boot services

If OS panics between after exiting it and before jumping to the kernel, no error messages will be printed.

Rename foo/mod.rs to foo.rs

`Makefile` should detect the changes in `bootx64`

Currently if some files in bootx64 directory are changed, make will not recompile. This will cause overlooking some bugs.

Use `use` to remove unnecessary module specification

Rename to `initialize_libs`

ramen/bootx64/src/main.rs

Line 40 in 32fb68b

uefi(&system_table);

Rewrite `memmove`

ramen/kernel/memlib/lib.c

Lines 21 to 28 in 61a49fc

 void* memmove(void* dst, const void* src, size_t n) 

 { 

 char buf[n]; 

 memcpy(buf, src, n); 

 memcpy(dst, buf, n); 

 return dst; 

 }

Remove function callings.

Create `common_items/const.rs`

All predefined addresses and sizes should be in this file.

Release version stucks in `virt_points_phys_recur`

Enable recursive mapping

Set 511st index of PML4.

Define `PhysAddr` and `VirtAddr`

Use type.

Store addresses which are common between bootx64.efi and the kernel in the same place

This may be possible using subcrate, then add a dependency.

`asm::lgdt` and `asm::lidt` should be moved to proper module

asm module should contain only general-purpose functions like in, out.

Mark all unused pages as not present

To detect invalid memory accesses easily.

`bootx64/src/memory.rs` should be separated into files

At least separate this file into two: getting memory map and initializing paging.

Is there a reason to save screen_(x|y) and bpp as u16

This is reminiscent of Haribote OS, isn't it?

CI stucks

Travis CI: Failed (missing rust-src)
Github Actions: Failed (missing rust-src)
Last update of cargo-xbuild: 13 days ago
Last update of Github virtual environment: Recent
Last update of rustup: 12 days ago

`cat` is no longer used

ramen/Makefile

Line 28 in 9df0f82

CAT := cat

load_interrupt_descriptor_table_register is too long

Rename this to lidt.

`descriptor.page_count` may be less than 1.

ramen/bootx64/src/memory.rs

Line 178 in c977a93

if descriptor.ty == MemoryType::CONVENTIONAL {

Check descriptor.page_count > 0.

Refactor `init_pic`

ramen/src/interrupt/mod.rs

Lines 37 to 53 in c913ced

 pub fn init_pic() -> () { 

 asm::out8(PIC0_IMR, 0xFF); 

 asm::out8(PIC1_IMR, 0xFF); 

 asm::out8(PIC0_ICW1, 0x11); 

 asm::out8(PIC0_ICW2, 0x20); 

 asm::out8(PIC0_ICW3, 1 << 2); 

 asm::out8(PIC0_ICW4, 0x01); 

 asm::out8(PIC1_ICW1, 0x11); 

 asm::out8(PIC1_ICW2, 0x28); 

 asm::out8(PIC1_ICW3, 2); 

 asm::out8(PIC1_ICW4, 0x01); 

 asm::out8(PIC0_IMR, 0xFB); 

 asm::out8(PIC1_IMR, 0xFF); 

 }

Is the order to call these functions important? What do the numbers mean?

If this isn't a Rust project, or if it is a library, you may wish to disable updates for it from within Dependabot.

View the update logs.

	void* memmove(void* dst, const void* src, size_t n)
	{
	char buf[n];
	memcpy(buf, src, n);
	memcpy(dst, buf, n);

	return dst;
	}

	pub fn init_pic() -> () {
	asm::out8(PIC0_IMR, 0xFF);
	asm::out8(PIC1_IMR, 0xFF);

	asm::out8(PIC0_ICW1, 0x11);
	asm::out8(PIC0_ICW2, 0x20);
	asm::out8(PIC0_ICW3, 1 << 2);
	asm::out8(PIC0_ICW4, 0x01);

	asm::out8(PIC1_ICW1, 0x11);
	asm::out8(PIC1_ICW2, 0x28);
	asm::out8(PIC1_ICW3, 2);
	asm::out8(PIC1_ICW4, 0x01);

	asm::out8(PIC0_IMR, 0xFB);
	asm::out8(PIC1_IMR, 0xFF);
	}

toku-sa-n / ramen Goto Github PK

ramen's Introduction

ramen

Requirements

Run on QEMU

How to get OVMF_VARS.fd and OVMF_CODE.fd

Execution

Run on your computer

Execution

License

ramen's People

Contributors

Stargazers

Watchers

Forkers

ramen's Issues

Recommend Projects

Recommend Topics

Recommend Org

How to get `OVMF_VARS.fd` and `OVMF_CODE.fd`