Welcome to the tenth monthly report for 2018! PulkoMandy is busy packing and then travelling to BeGeistert, and most of the work these past two months was done by myself anyway, so, I’m covering for him once again. (Writing about yourself in the third person is fun!)
This report covers hrev52310-hrev52462 (~250 commits.)
R1/beta1!
As you’ve probably already seen, heard, felt, … etc., Haiku R1/beta1 was released at the end of last month!! A list of all the major changes since the last release (many of which were covered in progress reports past) can be found in the release notes.
A small notification that we have updated our repository URL’s in preperation for R1 Beta 1.
This change will ensure that repository links remain consistant through R1 Beta 1 and beyond.
Time has come and a new monthly activity report arrived with it. It is the first time I write something this long in english. Enjoy!
This report covers hrev52141-52310.
Drivers
Now that GSoC is over krish_iyer’s SDHCI MMC driver has been merged in master. There is still a lot of work to do and it is not enabled in automated builds yet, but should serve as a basis for any future related work. His commits include extensive documentation on how to setup a testing vm, what has been done and what is left to do.
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
Hi there, it's time for the monthly report! (yes, I'm still out of inspiration for catchy headlines)
This report covers hrev52055-52140
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). So you are more likely to see a
bootscreen on UEFI machines now.
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.h0.interrupt_line; // driver needs to assign interrupt line to itself
if (bus->irq == 0 || bus->irq == 0xff){ // checking if right interrupt value is assigned
return B_ERROR
status = install_io_interrupt_handler(bus->irq, handler_function_name, bus, 0);
if(status != B_OK) // check if interrupt handler is successfully installed
return B_ERROR
Currently interrupt handler function can handle following interrupts(Referred: FreeBSD code)
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.
