It took me some time to write this report, between other stuff and a cold caught in July (WTF?). But still, plenty of stuff happened at this year’s edition of RMLL/LSM so I had to let you know.
Since the RMLL didn’t take place last year, as no city applied, I was quite impatient to see what this year’s edition in Saint Etienne would bring. By the way, if your hackerspace, LUG (or HUG?) wants to organize the next edition, you should apply quickly, but be warned, it’s quite a job!
Hello everyone.
After the second evaluation I have been carrying out various tests to compare the output characteristics of the current TCP implementation of Haiku against the one with my patches applied. I shared the links to my patches on the mailing list. They comprise of all ticket numbers in the range 13629 - 13634 [ Trac link ].
Test Setup
There are two systems:
- My Ubuntu 14.04 system running Haiku hrev51307 x86gcc2 inside Virtual Box.
- Raspbian pixel with 850 MB of RAM (it's based on Debian).
The Virtual Box was configured with a RAM of 4GB and video memory of 128 MB. Bridged Networking over wlan0 was enabled.<br>
Both the systems were connected to a mobile hotspot so they were part of the same LAN.
Hello Everyone!
In this post I would be focusing on the work done in the past two weeks.
I implemented a database backend and worked on generating notification for
events. Currently, I am using SQLite3 for data storage, but I would be implementing
a BFS backend for the same sooner. Google Calendar integration is currently in
progress. Also there is an issue with date/time parsing and formatting in the
app which I would be fixing.
Hi there,
Time for another monthly report! It covers hrev51254-hrev51346
Network
Waddlesplash merged some changes to netresolv (the DNS resolver), from NetBSD.
The virtio_net driver was completed by phoudoin, and is now somewhat working. This driver is used for the virtual network device provided by some virtual machines, and should be simpler to implement and keep up to date than the more or less correctly implemented emulated devices that are used otherwise. In particular, we plan to use this driver on some virtualized buildbots.
Hi there!
It has been 4 weeks since my last blog post. This blog post recaps what I have done in the second coding period and what I am doing and will do in the following weeks. Link to my previous blog post[1].
In the previous weeks I have been doing the implmentation for extent allocator and journal. About the extent allocator, the allocating strategy for now is “first fit” which means it allocates a first extent that after the address and has size that equal or larger the size we need. The allocator also handle extents that not present in the current tree because of the Copy-On-Write mechanism, so that the new allocated extent will not delete the old extent. The allocator can now allocate and deallocate extent, but it still need more testing though, it is hard to tell that it works well if is not actually in used (for examples making directories, writing files, etc).
Hello World.
The second evaluation got over recently, and wanted to update my progress. My last blog post had discussion
that custom preflets wanted to be added into SuperPrefs. It has been implemented now. Along with the exisitng
boxes for specific categories, there’s now a box for Custom preflets, which includes third party preflets which
come along with installation of apps. I also was working with implementation of Sorting of the entries in boxes,
users can sort it based on Category, or Alphabetically, both has been done now. Followed with some alignment of icons, and the buttons in the UI to look more uniform.
Hello everyone!
Since last week I worked on enabling Haiku support for running the swift test-suite. This allows the newly built compiler to be put through the same series of test-cases run by the swift buildbots for macOS, Linux and FreeBSD platforms. These tests cover different areas of the toolchain, from simple unit-tests to validation-tests that cover the compiler internals, major standard library API changes and most importantly, compiler stability via testing with malformed inputs. I ran the Swift 3.1 tests with the command ./utils/build-script -R -x , in which 2022 tests passed and 149 failed. A brief summary of the test results can be found here, and a list of the tests that have failed.
Hello Everyone!
It's been more than a week since I wrote my last blog post. In this post I
would brief you on the work done during this time.
I spent a little more time digging into the Haiku source (mostly the locale
kit) to work on bugs and possible improvements as I came across quite a few
places that would require it, while working on the Calendar app.
The current date is now highlighted in BCalendarView. This can be seen in the
deskbar calendar. I fixed a few bugs with my first commit regarding the same.
As we work to stabilize Haiku and move closer to the R1 beta releases, USB driver issues are becomming more apparent.
At the moment, bugs with our XHCI (usb 3.0) stack are high on the problem list. New hardware is beginning to ship
with XHCI-only controllers, which means we can no-longer fall back to our stable EHCI (usb 2.0) stack.
A large number of bug reports have been opened around these kinds of issues:
Greetings
It has been a while since the last Report. So here I go. Firstly, I would like to thank all the Haiku mentors and developers for the first GSoC evaluation, thank you for believing in me. Now coming to the report.
Progress
I am still at the Linux compatibility layer, adding new headers and dependencies one by one. Things are not moving as fast as I would like them to, mainly because of my lack of understanding of Haiku’s internals. Linux has great documentation and thus a simple Google search brings up reading material which can be understood easily. It is pretty much the same with FreeBSD, but not the case with Haiku. Thus, the only two options I am left with is asking people in the mailing list and figuring it out myself. Both of which I try to do every time I face a problem but is a time-consuming process.
