Go to file
PulkoMandy fb1d7157d2 ps2: do not publish keyboard device until mouse probing is complete
For mouse probing to work reliably, it's important that we don't
simultaneously send commands to the keyboard as well. This normally
happens because we don't publish the keyboard device until the probing
is complete.

However, if the mouse probing results in the keyboard sending some
replies, this can be detected as a "hot plugin" and leads to publishing
the keyboard device a lot earlier.

To prevent this, disable the "hot plugin" feature until we are done
initializing. This way the keyboard device is published only after we
are done with the probing.

Fixes #17806

Change-Id: Ia6a2b031550c845fa305df5b5f4d513d5c7931d6
Reviewed-on: https://review.haiku-os.org/c/haiku/+/5388
Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
Reviewed-by: Jérôme Duval <jerome.duval@gmail.com>
2022-07-11 16:09:23 +00:00
3rdparty Some script for a crude convertion from Hugo to Pandoc 2022-05-29 23:29:46 +02:00
build FAT: enable -Werror 2022-07-11 16:05:17 +00:00
data Update translations from Pootle 2022-06-25 08:11:32 +00:00
docs Userguide CSS: Fix banner color. 2022-07-06 12:01:20 -04:00
headers kernel/arm: use generic/user_memory.h 2022-07-04 16:43:39 +00:00
src ps2: do not publish keyboard device until mouse probing is complete 2022-07-11 16:09:23 +00:00
.editorconfig
.gitignore gitignore: Add Visual Studio Code and IntelliJ IDEA configuration directories 2021-05-31 20:15:44 +00:00
.gitreview
configure cross_tools: allow specifying a custom sysroot path 2022-06-05 09:08:20 +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

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.