Go to file
X512 de8c1bcc32 kernel/arch/user_debugger: implement for risv64
Change-Id: I9cdf7a6a5b66cdd83133485f98067ce9a5fb819d
Reviewed-on: https://review.haiku-os.org/c/haiku/+/4058
Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com>
2021-08-06 15:42:49 +00:00
3rdparty
build HaikuPortsCross/riscv64: update GCC package 2021-08-06 07:33:42 +00:00
data Synchronize translations from the r1beta3 branch 2021-07-21 12:55:45 +01:00
docs docs/user/net: add BUrlRequest documentation 2021-07-25 11:52:21 +00:00
headers kernel/arch/user_debugger: implement for risv64 2021-08-06 15:42:49 +00:00
src kernel/arch/user_debugger: implement for risv64 2021-08-06 15:42:49 +00:00
.editorconfig
.gitignore
.gitreview
configure
Jamfile
Jamrules
lgtm.yml
License.md
ReadMe.Compiling.md
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:

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.

Contributing translations

See wiki:i18n.

Contributing software ports

See HaikuPorts.

Contributing to our infrastructure

See Infrastructure.