Aren/haiku

Go to file

Kyle Ambroff-Kao d8779e44ee Drop requirement for specifying firmware map size The HAIKU_FIRMWARE_NAME_MAP macro takes a size parameter to define the firmware map array type, and then a multi-dimensional array literal is assigned to the array defined by that macro. This is error-prone. The idualwifi7260 driver, before this patch, had the size incorrectly set to 6 when the number of entries was 7, which sliced the last entry off of the map, making it unavailable to the driver. After fixing this size, the driver properly loads the iwm-8265-22.ucode firmware on my computer. This patch changes that macro to take a const char[][2] literal as its only parameter, making it less likely for this sort of bug to be re-introduced. Fixes #15413. Change-Id: I78a75e692a8637af0f13d1eb16180ce8d95d0852 Reviewed-on: https://review.haiku-os.org/c/haiku/+/1917 Reviewed-by: Adrien Destugues <pulkomandy@gmail.com>		2019-10-16 00:23:55 +00:00
3rdparty	dump_windows: off-by-1	2019-09-17 19:56:34 +02:00
build	build-packages/x86_64: Bump HaikuPorts to latest packages	2019-10-15 09:28:39 -05:00
data	Update translations from Pootle	2019-10-12 08:50:26 +00:00
docs	Start documentation for filesystems	2019-10-08 18:57:28 +02:00
headers	fixed btrfs_shell	2019-10-08 18:57:27 +02:00
src	Drop requirement for specifying firmware map size	2019-10-16 00:23:55 +00:00
.editorconfig
.gitignore
.gitreview
configure	ARM64: Initial changes so we can compile GCC toolchain	2019-08-30 19:05:16 +00:00
Jamfile	Jamfile: gutenprint -> gutenprint8.	2019-05-14 19:32:29 -04:00
Jamrules	Revert "Jamrules: Include the UserBuildConfig before processing repositories."	2019-09-15 17:33:36 +02:00
lgtm.yml	Initial version of lgtm.com configuration file.	2019-09-19 04:03:09 +00:00
License.md
ReadMe.Compiling.md	ReadMe.Compiling: Various updates.	2019-01-08 19:32:34 -05:00
ReadMe.md	ReadMe: Add note about infrastructure	2018-02-23 11:40:11 -06: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 OpenGrok servers:

http://xref.plausible.coop/ (provided by Landon Fuller)
http://code.metager.de/source/xref/haiku (provided by MetaGer)

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.