Aren/haiku

Go to file

David Karoly adc32659fb arm: enable enforcing memory access permissions Bootloader: * set permissions to kernel read/write, no user access for initially mapped memory areas * set permissions to kernel read/write, no execute, no user access for UART Kernel: * physical memory mapper uses kernel read/write mapping with no-execute bit enabled * all other pages are mapped as read/write/execute for kernel and user * proper access permissions and memory types to be implemented later Enforce memory access permissions by setting DACR to client mode for domain #0, no access for other domains. see ARM Architecture Reference Manual, section B3.7 Memory access control and in particular the following subsections: B3.7.1 Access permissions B3.7.2 Execute-never restrictions on instruction fetching B3.7.3 Domains, Short-descriptor format only Change-Id: I8127b4c72dc516d013cb9751d80d6f3a9ec835e6 Reviewed-on: https://review.haiku-os.org/c/haiku/+/5233 Reviewed-by: Adrien Destugues <pulkomandy@gmail.com>		2022-04-22 12:20:01 +00:00
3rdparty	3rdparty/docker/bootstrap: Cleanup, little modernization	2022-03-28 19:38:38 -05:00
build	userlandfs: add a pkg-config file for the fuse compatibility	2022-04-22 09:43:53 +00:00
data	userlandfs: add a pkg-config file for the fuse compatibility	2022-04-22 09:43:53 +00:00
docs	docs/arm: update info for Raspberry Pi 2	2022-04-22 10:50:59 +00:00
headers	arm: enable enforcing memory access permissions	2022-04-22 12:20:01 +00:00
src	arm: enable enforcing memory access permissions	2022-04-22 12:20:01 +00:00
.editorconfig
.gitignore	gitignore: Add Visual Studio Code and IntelliJ IDEA configuration directories	2021-05-31 20:15:44 +00:00
.gitreview
configure	configure & build: make use of 64-bit libgcc and libsupc++ for EFI/x86_64	2022-03-25 09:51:39 +00:00
Jamfile	Update build-packages for GCC 11 upgrade.	2021-12-07 14:26:24 -05:00
Jamrules	Revert "Jamrules: Include the UserBuildConfig before processing repositories."	2019-09-15 17:33:36 +02:00
lgtm.yml	lgtm.yml: disable Wformat-diag when building gcc	2021-12-14 06:06:41 +00:00
License.md
ReadMe.Compiling.md	Added missing --cross-tools-source argument name for bootstrap build and missing \ at the end of line 136	2021-12-02 08:05:50 +00:00
ReadMe.md	ReadMe: Add Getting Involved link	2021-06-13 21:06:58 +00:00

ReadMe.md

Haiku

Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs

Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.

Goals

Sensible defaults with minimal configuration required.
Clean, clear, concise code.
Unified desktop environment.

Trying Haiku

Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.

Compiling Haiku

See ReadMe.Compiling.

Contributing

Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!

Contributing code

If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.

If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:

https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
https://git.haiku-os.org/ (git, provided by Haiku, Inc.)

Contributing documentation

The main piece of documentation that still needs work are the API docs (found in the tree at docs/user). Just find an undocumented class, write documentation for it, and submit a patch.