OS Haiku практика применения для "хомячков"

‼️Проблема, связанная с ABI, была устранена в версии hrev60013, спасибо X512 за предоставленный трассировочный дамп. Однако драйвер все равно потребуется пересобрать.‼️ 😳 kernel/locks: Unify ABI of static initializers. hrev60013 Since 0 is now a fully invalid thread ID, we can use it in the static initialized for thread_id even on KDEBUG kernels. As a bonus, check for holder < -1 in mutex_lock. This will catch fully uninitialized or freed locks (since 0xcc and 0xdeadbeef < 0). This fixes the underlying problem that was causing #20256. However, it breaks KDEBUG kernel ABI (but not non-KDEBUG ABI), so drivers that use these (still officially unstable) APIs will need to be rebuilt.

[GSoC 2026] Expanding the functionality of the Haiku Devices Application - Final Report https://www.haiku-os.org/blog/aquamatic123/2026-08-21_gsoc_2026_expanding_the_functionality_of_the_haiku_devices_application_-_final_report/ Hello everyone! As Google Summer of Code 2026 comes to a close, it’s time to summarize the work I’ve done over the summer on expanding the functionality of the Haiku Devices application. Overview Haiku’s Devices application previously provided a basic list of connected hardware, but lacked the features necessary to function as a true management utility. My project aimed to transform Devices into a more capable hardware manager, allowing users to view detailed technical specifications and perform administrative tasks directly from the GUI. Over the course of the summer, I focused on implementing new visualization features, improving the user experience, and pulling more detailed hardware information directly from the system. Completed Objectives & Work Accomplished Here is a breakdown of what was accomplished this summer: Driver Mapping: Integrated the GUI with the kernel structures to display the active driver module name and its absolute path (/dev). This involved extending the device_manager module by adding a new device attribute and being able to fill that attribute when possible. Extract USB descriptors: Enhanced the application’s ability to inspect USB devices. By utilizing the BUSBDevice API, the app now builds a tree with all USB attributes descending the USB hierarchy. We first loop through the configurations, then the interfaces, and finally the endpoints. The app can also display HID descriptors. State Management (Packaged Driver Blocking): Added a new GUI button to disable or re-enable packaged drivers. This required implementing the backend logic to read, modify, and write to the system’s Packages configuration file. I also added safety checks to prevent users from accidentally disabling drivers essential to the system, and ad

threedeyes commited to haikuports telegram_desktop: bump version

https://discuss.haiku-os.org/t/gltoggle-new-app/19767 ablyss 9 мин Hi all, This app was created to help users toggle between mesa and nebula GL drivers. I’ve found out the hard way that if you don’t do it in just the right order, Haiku will uninstall a whole lot of packages. If you leave the app open it will reuse the previous downloads when reinstalling nebula, else it will download. Looking ahead.. I plan to add a system tray and some other options but for now this is a good start. Привет всем, Это приложение было создано, чтобы помочь пользователям переключаться между драйверами Mesa и Nebula. Я узнал на собственном горьком опыте, что если делать это не в правильной последовательности, Haiku может удалить огромное количество пакетов. Если вы оставите приложение открытым, оно будет использовать предыдущие загруженные файлы при повторной установке Nebula, в противном случае оно скачает их заново. В будущем я планирую добавить системный трей и другие опции, но пока это хорошее начало.