Source Activity

Syndicate content
Haiku's main repository
Updated: 31 min 33 sec ago

UEFI: serial debugging support.

Fri, 2016-12-16 03:46
Signed-off-by: Jessica Hamilton Signed-off-by: Jessica Hamilton
Categories: Development

Update pci.ids from pciids.sourceforge.net

Thu, 2016-12-15 04:20
Categories: Development

App Server DefaultWindowBehaviour: style fixes only

Wed, 2016-12-14 19:01
Compare bitmasks against 0 explicitly Replace integer constant 0 with floating point constant 0.0f No logic reversals I promise Compare bitmasks against 0 explicitly Replace integer constant 0 with floating point constant 0.0f No logic reversals I promise
Categories: Development

Add rtmpdump package for x86_64.

Tue, 2016-12-13 19:14
* update libgcrypt and wpa_supplicant packages for x86_64. * update libgcrypt and wpa_supplicant packages for x86_64.
Categories: Development

UEFI: CR0.WP must be set before entering the kernel.

Tue, 2016-12-13 13:44
If WP is not enabled then the kernel can freely write to read-only user pages, which breaks copy-on-write. Signed-off-by: Jessica Hamilton If WP is not enabled then the kernel can freely write to read-only user pages, which breaks copy-on-write. Signed-off-by: Jessica Hamilton
Categories: Development

Revert "vm: Try harder to allocate early physical pages."

Tue, 2016-12-13 09:24
This reverts commit 21e3ac6cf52f91dba8217f15fc33dc1d45dffd40, which was accidentally applied twice, missed during rebase. Originally applied in 601b2f7eda4d25b46e7d17e212d22954f28bd0fe. This reverts commit 21e3ac6cf52f91dba8217f15fc33dc1d45dffd40, which was accidentally applied twice, missed during rebase. Originally applied in 601b2f7eda4d25b46e7d17e212d22954f28bd0fe.
Categories: Development

Add a dumb framebuffer driver.

Tue, 2016-12-13 08:41
This is separate to the VESA driver, as the VESA driver requires using the VBE BIOS. Under UEFI, we don't have the VBE BIOS, nor are we able to switch modes after leaving UEFI Boot Services, so a dumb framebuffer driver seemed like the easier way to approach the problem. The framebuffer & vesa drivers now test for the presence of the VESA_MODES_BOOT_INFO boot item to distinguish between which driver to use. Also added check for the VESA mode count to determine whether to add the VESA_MODES_BOOT_INFO item. UEFI video updated to explicitly zero out the VESA and EDID boot data. This is separate to the VESA driver, as the VESA driver requires using the VBE BIOS. Under UEFI, we don't have the VBE BIOS, nor are we able to switch modes after leaving UEFI Boot Services, so a dumb framebuffer driver seemed like the easier way to approach the problem. The framebuffer & vesa drivers now test for the presence of the VESA_MODES_BOOT_INFO boot item to distinguish between which driver to use. Also added check for the VESA mode count to determine whether to add the VESA_MODES_BOOT_INFO item. UEFI video updated to explicitly zero out the VESA and EDID boot data.
Categories: Development

MediaEncoder: Fixes CID 1347183: Control flow issues (NO_EFFECT)

Mon, 2016-12-12 23:19
* An unsigned value was checked for negative values. * An unsigned value was checked for negative values.
Categories: Development

Sync x86_64 packages with Haikuports trunk.

Mon, 2016-12-12 16:34
Categories: Development

kernel: Fix NULL dereference in ThreadTimeUserTimer::Schedule().

Mon, 2016-12-12 10:42
The SpinLocker was always initialized to fThread->time_lock even though fThread may be NULL. This looks like a simple oversight as the rest of the method handles fThread being NULL and the team variants of these timers have very similar logic and do the NULL check as well. This fixes the last remaining KDL in the posixtestsuite. The SpinLocker was always initialized to fThread->time_lock even though fThread may be NULL. This looks like a simple oversight as the rest of the method handles fThread being NULL and the team variants of these timers have very similar logic and do the NULL check as well. This fixes the last remaining KDL in the posixtestsuite.
Categories: Development

MediaInput/Output: Inherit base virtually

Sun, 2016-12-11 18:13
Categories: Development

Debugger: Fix oversight.

Sun, 2016-12-11 16:08
DebugReportGenerator: - In the case where the function was already disassembled beforehand, we weren't retrieving the statement, leading to a null pointer dereference. DebugReportGenerator: - In the case where the function was already disassembled beforehand, we weren't retrieving the statement, leading to a null pointer dereference.
Categories: Development

FreeBSD compat: Align allocations according to FreeBSD man page.

Sat, 2016-12-10 21:58
According to the FreeBSD kernel malloc man page the allocator is expected to return power of two aligned addresses for allocations up to one page size. While it also states that this shouldn't be relied upon, at least our (directly copied) bus_dmamem_alloc expects it and drivers may depend on it as well. Looking through the FreeBSD commit logs, this expectation seems to be rooted quite deeply. This fixes watchdog timeouts in the ipro1000 driver under KVM and may help with #11953. It might also be related to #9099 and #9601 as those seem memory allocation related as well. According to the FreeBSD kernel malloc man page the allocator is expected to return power of two aligned addresses for allocations up to one page size. While it also states that this shouldn't be relied upon, at least our (directly copied) bus_dmamem_alloc expects it and drivers may depend on it as well. Looking through the FreeBSD commit logs, this expectation seems to be rooted quite deeply. This fixes watchdog timeouts in the ipro1000 driver under KVM and may help with #11953. It might also be related to #9099 and #9601 as those seem memory allocation related as well.
Categories: Development

Revert "repo rework: Re-add compatibility url field"

Sat, 2016-12-10 11:51
Revert "repo rework: Remove stubs; Breaks repo compat." Revert "repo rework: Remove need for repos to be self-aware" This reverts commit a2b2f4d6427914cdcdb59943dd8e4a0bfdcd53ee. This reverts commit 602076ef82647a48fd10f4d1ec830bb4242f9eb6. This reverts commit 5ffaf72c8a74a7eb6827e4d2b1f47c9360ddaefe. These changes break the build on Haiku and the ability to create repo mirrors, for the lack of a replacement for the URL (an UUID was evoked on the mailing lists, but not implemented). We are due for a release soon, please don't break the build. Revert "repo rework: Remove stubs; Breaks repo compat." Revert "repo rework: Remove need for repos to be self-aware" This reverts commit a2b2f4d6427914cdcdb59943dd8e4a0bfdcd53ee. This reverts commit 602076ef82647a48fd10f4d1ec830bb4242f9eb6. This reverts commit 5ffaf72c8a74a7eb6827e4d2b1f47c9360ddaefe. These changes break the build on Haiku and the ability to create repo mirrors, for the lack of a replacement for the URL (an UUID was evoked on the mailing lists, but not implemented). We are due for a release soon, please don't break the build.
Categories: Development

Revert BNode changes resulting in non bootable system

Sat, 2016-12-10 08:57
Revert "BNode: CID 602323 explicitly ignore fCStatus return value in ctor" Revert "BNode: Set fCStatus in SetTo() explicitly" Revert "BNode: Style fixes, see below for details" This reverts commit ede463195dee8536628c54ee6a4a888c0683a83f. This reverts commit 6e3445098abd1d1e4cca69ba2d959fe74fe2cb1b. This reverts commit 89c0b71c9a5acdbdb4543f025f64937bfbd893e3. We are due for a release soon. Please keep things working. Revert "BNode: CID 602323 explicitly ignore fCStatus return value in ctor" Revert "BNode: Set fCStatus in SetTo() explicitly" Revert "BNode: Style fixes, see below for details" This reverts commit ede463195dee8536628c54ee6a4a888c0683a83f. This reverts commit 6e3445098abd1d1e4cca69ba2d959fe74fe2cb1b. This reverts commit 89c0b71c9a5acdbdb4543f025f64937bfbd893e3. We are due for a release soon. Please keep things working.
Categories: Development

Debugger: Rework parts of report generation.

Sat, 2016-12-10 03:57
Team: - Adjust report generation event to include a final status code for listeners. CliContext,TeamWindow,ReportUserinterface: - Use aforementioned status code to indicate whether report generation succeeded or failed. DebugReportGenerator: - Notify listeners if report generation fails. This may have previously been responsible for some bug reports where it was indicated that the debugger hung without exiting after being asked to save a report from a crashed app. - When dumping disassembly, retrieve it directly if necessary rather than requesting it via the user interface listener. This also fixes the quirk that requesting to save a crash report while looking at the source code of a function would trigger switching it to disassembly visually. - When walking the list of threads to dump, acquire references to all of them before starting. Otherwise, it was potentially possible for a running but not crashed thread to exit while we were generating the report, leaving us with a pointer to a deleted thread. This was most likely the cause of one of the crashes reported in #13082. - When receiving the notification that source code state has changed, clear the waiting function. Otherwise, it was potentially possible for us to get other state change notifications, leading to the data semaphore being released too often. This would then cause later potential waits such as the stack frame memory dump to not actually wait when they should, potentially leading them to dereference objects that weren't yet ready. This fixes another of the crashes in #13802. Team: - Adjust report generation event to include a final status code for listeners. CliContext,TeamWindow,ReportUserinterface: - Use aforementioned status code to indicate whether report generation succeeded or failed. DebugReportGenerator: - Notify listeners if report generation fails. This may have previously been responsible for some bug reports where it was indicated that the debugger hung without exiting after being asked to save a report from a crashed app. - When dumping disassembly, retrieve it directly if necessary rather than requesting it via the user interface listener. This also fixes the quirk that requesting to save a crash report while looking at the source code of a function would trigger switching it to disassembly visually. - When walking the list of threads to dump, acquire references to all of them before starting. Otherwise, it was potentially possible for a running but not crashed thread to exit while we were generating the report, leaving us with a pointer to a deleted thread. This was most likely the cause of one of the crashes reported in #13082. - When receiving the notification that source code state has changed, clear the waiting function. Otherwise, it was potentially possible for us to get other state change notifications, leading to the data semaphore being released too often. This would then cause later potential waits such as the stack frame memory dump to not actually wait when they should, potentially leading them to dereference objects that weren't yet ready. This fixes another of the crashes in #13802.
Categories: Development