What's New in Haiku development
The Haiku source is continually built and released for testing purposes nearly every day. You can download and install these latest snapshots to check out the latest features and bug-fixes.
Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.
If you're OK with this, you can find further instructions at our Nightly image page.
At last, R1/beta1 is nearly upon us. As I’ve already explained on the mailing list, only two non-“task” issues remain in the beta1 milestone, and I have prototype solutions for both. The buildbot and other major services have been rehabilitated and will need only minor tweaking to handle the new branch, and mmlr has been massaging the HaikuPorter buildmaster so that it, too, can handle the new branch, though that work is not quite finished yet.
Hello everyone, We are in the final week of GSoC’18 program and yesterday our code has successfully merged. It got crashed in the first build because we thought we would add the code but disable the build currently but we didn’t test the case when device manager will try to find the driver in a certain directory which we hardcoded at the time of loading the module. So we just changed it to an OR condition where it won’t be able to find the driver binary but still be able to boot the OS in any case.
Hello everyone, this week we have tried to get the response from the command but unfortunately, it didn’t work out. In the meantime, I have submitted the code for review and PulkoMandy had already reviewed once. I have been going through Linux patches1 2 which are related to the issue we are currently facing.
I have done following improvements in the code
Disabled adding drivers to the kernel, removed statements from
Hi there, it's time for the monthly report! (yes, I'm still out of inspiration for catchy headlines)
This report covers hrev52055-521XX
Drivers waddlesplash completed his work synchronizing drivers with FreeBSD 11. The FreeBSD9 compatibility layer is now gone and all drivers are up to date again.
jessicah fixed a problem in the UEFI framebuffer driver (most of the code is shared with the "VESA" driver, although there is no VESA BIOS in this case).
This is the thirteenth progress report for TrackGit project. I did the following in last week:
Since, the planned work from the proposal is done, Stephan and I agreed on doing some UI improvements to the existing views. Stephan suggested me some improvements, which I did in last week. These are:
Added progress bar to Clone Window I added a progress bar to the clone window. This will give better information about the clone progress.
Hello everyone, here we are with another update on the project. Last week we have started with installing interrupt handler, so basically we will pass the address of a function while installing the interrupt handler, later when an interrupt occurs that function will be called.
We opted for pin-based interrupt handler, which is one of the levels of interrupt handling. I have explained them in previous blogs.
Instructions to install an interrupt handler: bus->irq = pciInfo->u.
This is the twelveth progress report for TrackGit project. I did the following in last week:
Implemented Log Viewer I implemented a log viewer in TrackGit. It shows a window with the commits in the repository so far. Link to commit.
The following screenshot shows the log viewer:
I also added tests for the log command. Link to commit.
This is the eleventh progress report for TrackGit project. I did the following in last week:
Implemented Create Branch command I implemented Create Branch command. This command creates a branch at head of the repository. There is also an option to switch to the newly created branch. Link to commit.
The following screenshot shows Create Branch window:
Implemented Switch Branch command I implemented option to switch branch. The Switch Branch window gives user with a drop down list of branches in current repository.
So here we are in the final week of the second phase of this project. I would like to address what was planned for this phase and what we have achieved and will proceed to plan for the third phase.
Second Phase Highlights We were successful in register mapping through MMUIO. We have created a bus manager but not linked with controller ATM. Interrupts have not been implemented but also not required in this phase.
Hey guys! Last week we have improved the code and made it more readable. We have completed the reset and clock sequence and proceed with power sequence. In the 4th step of the sequence, it asks to get the Operation Conditions Register(OCR) value of SD card. In the SD host controller spec, in command register there is command index bits which mention about setting up command number specified in bits 45-40 of the command-format in SD Memory Card Physical Layer Specification.
