This should fix runtime_loader "cannot open file" errors logged into syslog because every
standard locations were attempted without checking for actual existance of a file to
attempt to open.
There messages were misleading users about their criticity.
Change-Id: I621b122a4eee1cc7ad2ff1c03f5146809657e7d4
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11175
Tested-by: Commit checker robot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
* Ensure memory is locked before doing virtual->physical translation.
* Make sure get_memory_map_etc actually returned an entry.
I didn't see either of these trip in some basic testing though.
This change will cause HaikuDepot to communicate
with the server on start-up to obtain runtime
information.
Included in the information is the server's
current timestamp. This allows the client to then
validate there is not too much drift between the
server and the client.
The primary driver for this change is to pickup
the future transition from the server allowing
nickname+password authentication over to only
supporting SSO. Once the server no longer supports
nickname+password auth then the UI can disable it
and the users of the legacy HaikuDepot versions
can nevertheless continue to use the rest of the
application OK.
Change-Id: I203102c2266f67115f4b0290f1909346701f79e4
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11047
Reviewed-by: Andrew Lindesay <[email protected]>
Tested-by: Commit checker robot <[email protected]>
* Properly handle copy-on-write in the case of consumers, same as
set_area_protection. This seems to fix most of the remaining problems
in boehm-gc's mprotect-VDB.
* Do not call set_area_protection if the whole range is covered,
as it tries to acquire address space locks, which can lead to
deadlocks: that was the cause of #20138. Instead, handle changing
the protection of all pages in here.
* Don't unmap pages of lower caches; just don't allow writing to
those pages. This allows us to avoid unlocking the translation map,
and also should mean a lot fewer page faults, hopefully improving
performance.
Fixes#20138.
This would underestimate the number of pages needed to map an address
range resulting in too-small page table page reservations, causing a crash
Change-Id: I34513621b36ecd60de71e128912950b66a6a6964
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11129
Haiku-Format: Haiku-format Bot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
Tested-by: Commit checker robot <[email protected]>
- This is a mandatory feature in HCI Implementation Conformance Statement (ICS).
- The inquiry cancel logic was implemented in Haiku, but wasn't linked to the inquiry panel.
Change-Id: Ic827b0a09979a078bed5b9f99a8541dc319ac449
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11106
Tested-by: Commit checker robot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
Untested as I don't have hardware with supported brightness control,
but the changes are relatively straightforward.
Should fix#20134.
Change-Id: I45b78bc8006a54cc5ba4f65a026df99401c621b5
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11083
Reviewed-by: waddlesplash <[email protected]>
- Running the function RemoteDevice::Authenticate() caused "Invalid
Arguments" error because packetType had both ACL and SCO types while
the command parameter require only ACL packet types.
- Thus, bits 5, 6, and 7 should be 0 becuase they're for reserved for
future use.
- This was tested on Haiku to pair with an Android phone.
Change-Id: I24a338a2494bfaaab056abf73f1c946179d6b606
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11105
Tested-by: Commit checker robot <[email protected]>
Haiku-Format: Haiku-format Bot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
Shows Device path in /dev if used and Driver used. New tree-view layout for Basic
Information and Attributes separated.
Changes:
- Added new attribute in device_manager to get the path of device
- Tree view layout that separates the Basic Information of a device,
such as name or driver used and the Attributes that shows the rest
- new call in dm_wrapper
- new case in device_manager
- logic to add the new attributes as Device path and Driver used in
DevicesView.cpp
Change-Id: I05eaf5d7cf9e3b5ec8e9f1e0ac5c6cf7561ccde5
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11012
Reviewed-by: Kacper Kasper <[email protected]>
Tested-by: Commit checker robot <[email protected]>
Reviewed-by: Jérôme Duval <[email protected]>
* Block writes to ranges that have been read as part of a
read-modify-write operation until that operation has completed.
* Fixes potential corruption issues when using a filesystem block size
smaller than the device physical block size.
Fixes#16951
Change-Id: Ibae317483ae34e506ceee1736107837a3b999ca7
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11017
Reviewed-by: waddlesplash <[email protected]>
Tested-by: Commit checker robot <[email protected]>
- The feature was tested in Haiku Nightly
- Users now can type a new friendly name in settings then the name will be updated in the local devices menu, the device view, and the Bluetooth device
Change-Id: I367512ceba8e798327c7b28fa4ea5a2f63c3f383
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11076
Tested-by: Commit checker robot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
- The added command is mandatory under the HCI Implementation Conformance Statement (ICS).
- The command was tested through running the bluetooth_server and Bluetooth preferences and tracking the output logs.
Change-Id: I471766233dee5b24b3fe424fe6724e4378b5927b
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11075
Tested-by: Commit checker robot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
Otherwise, the host won't be able to modify the guest FPU (and we could
clobber the state, too.)
This doesn't seem to fix the general problems seen so far, however.
This seems to fix the crash when opening a filepanel. I didn't test it
further. It may make more sense to revert all my attempted changes
instead and find a better approach.
Fixes#20128.
Change-Id: Ibf8d77a5f435abdbf4610666642235f2f727879f
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11074
Haiku-Format: Haiku-format Bot <[email protected]>
Reviewed-by: waddlesplash <[email protected]>
Tested-by: Commit checker robot <[email protected]>
When there is no screenshot, shows a
placeholder image and some text to explain
that there is no screenshot.
Closes#19923.
Change-Id: Icd12dca9503d9fc270fc88ec8cba05ad20fa8a79
Reviewed-on: https://review.haiku-os.org/c/haiku/+/11013
Tested-by: Commit checker robot <[email protected]>
Reviewed-by: Andrew Lindesay <[email protected]>
The bootloader is now only responsible for setting up Protected Mode
and Paging. It otherwise preserves the existing CR0, and leaves setup
to the kernel.
The kernel now sets CR0 for each CPU in preboot_init_percpu().
Some redundant sets are removed from x86_init_fpu, which now
panic()s in the case where we don't have a FPU, and avoids
unnecessary prints.
This fixes a massive oversight where CR0 was never reset on x86
systems booted using the EFI loader, except on the boot CPU! That
meant that NUMERIC_ERROR and possibly even WRITE_PROTECT were
simply not set on non-boot CPUs, unless the EFI BIOS had set them up
already. (On the BIOS loader, smp_start_kernel() ran on all CPUs.)
Fixes NVMM initialization on non-boot CPUs on Intel hardware.
Philippe Houdoin