Haiku Admin Meeting Summary - July 23, 2007

Blog post by umccullough on Thu, 2007-07-26 07:42

Haiku Admin Meeting 2007-07-23: A quick GSoC status was discussed. It was agreed that having Axel and Ingo working together in the same location to focus on many of the VM and stability issues was a successful endeavor: It was proposed that this be done more often, with possible sponsorship from Haiku, Inc. to pay for costs whenever possible. It was agreed that Axel and/or Ingo will be reimbursed for any expenses that were incurred.

Haiku Admin Meeting Summaries - July 2, 2007 and July 9, 2007

Blog post by umccullough on Thu, 2007-07-26 07:25

Haiku Admin Meeting 2007-07-02: Discussion about WalterCon planning. Things are moving along. The existence of a project called RadiantOS which claims to eventaully be a "distro" based on Haiku was mentioned. There was some discussion about the status of running GCC in Haiku: Haiku might be close to self-hosting capability (able to build itself). It was mentioned that once Haiku can self-host it's probably time for an official alpha release.

All is well

Blog post by sil2100 on Thu, 2007-07-19 12:15

Even though I had some private issues this week, all is going well with the PackageInstall. In its current form it is able to properly install all 3 test BeOS packages I tried on it, creating files and directories along with their data and attributes without flaw. So, what’s left to do right now?

Overview of Messaging in the Application Kit

Blog post by nielx on Sun, 2007-07-15 10:00

For the API Documentation team I’ve prepared an overview of the messaging functions in the Application Kit, mind map style. This image should be the guide to writing the actual API documentation. Please redirect comments on the technical content to the haiku-development list. They are highly appreciated!

Who is Joe User?

Blog post by darkwyrm on Mon, 2007-07-09 12:45

A couple of articles I just read (here and its rebuttal) are written by Linux users about why Linux is the best and how to get a regular person (hereafter referred to as Joe User) to start using Linux. To save you the time of reading the two articles, the first is entitled “Understanding the Common User: Everything should be as simple as it is, " by Keyto. The article is partly about how a Common User thinks, but primarily that quite a lot of the problem with Linux is the current users – geeks who have trouble relating to Joe at Joe’s level of expertise instead of the geek’s level.

Haiku Admin Meeting Summaries - June 18, 2007 and June 26, 2007

Blog post by umccullough on Fri, 2007-07-06 02:04

Haiku Admin Meeting 2007-06-18: Discussion about some "missing" articles on the new website - specifically old newsletters. Also desired is a way to make them easier to locate. Mention of the continual "browser for Haiku" topic that pops up in the mailing list and elsewhere. An official decision should be discussed and published. It may be still too early to fully decide on a direction. More discussion took place about a potential physical "

Design Considerations

Blog post by ivo on Thu, 2007-07-05 07:24

Haiku’s network stack follows a top-down approach with clear boundaries, pure object oriented design. However, TCP/IP protocol stack was designed more than 30 years ago with different idea in mind. It’s mostly speed, fast processing and stability that designers were looking for back then. That’s why many boundaries in the TCP/IP protocol suite design are blurred somehow. Basic hierarchy is established. Datalink layer protocol (Ethernet, PPP, etc.) is followed by a Network layer protocol (IP), which is followed by a Transport layer protocol (TCP, UDP, SCTP, etc).

Adding isochronous support to USBKit and usb_raw

Blog post by emitrax on Tue, 2007-07-03 12:36

Just to keep those of you interested updated, after discussing it with both my mentor and Michael Lotz, and after a very quick chat with Francois Revol, I am going to add isochronous support to both the USBKit and usb_raw driver. Meanwhile Francois, if time is on his side, should add isochronous support to his user space quickcam driver (see src/add-ons/media/media-add-ons/usb_webcam/). This way I can test my previous patches and perhaps everyone can start using his logitech quickcam with Haiku by using codycam.

UHCI isochronous support added

Blog post by emitrax on Tue, 2007-06-26 22:21

For those of you who are not following the haiku-commit mailing list, I’ve added the isochronous support to the UHCI driver. I’m working on a quickcam driver to test the code, but if someone of you out there, already have some very simply driver, that needs isochronous support, please contact me and help me with the testing. The sooner I’m done with the testing, the sooner I’ll move on to the OHCI driver.

And those decisions lead us to...

(Or: knitting a delicate fabric, part II: sewing it all together) (Or: Right, Joker, the underwear might be on the outside, but I get to drive the Batmobile!) (Or: I just had to say something about Batman and the Batmobile. Couldn’t help it.)

Cool, now we have a space- and time-efficient data structure (which is nothing more than a nice structure to handle non-overlapping numeric ranges) we can use to implement the simplified stride scheduling thing I’ve been discussing ou the previous posts, which will remain small most of the time, and won’t change its shape like mad, so it’s also very gentle on the CPU cache. Not only that, but the same effects hold for any trees, shall we decide that red-black trees aren’t adequate and set ourselves to use splay trees, AA trees, AVL trees, Huffman trees, unbalanced binary trees (please: no.), whatever. So far we took care of the (not any more) skewed proportions due to randomness (by using strides), the mapping of “tickets” to tasks (by using trees to store the queues, “indexes” as the tickets, offsets to simulate “special” tickets, and lazy evaluation to efficiently implement offset propagation to upper queues), and the order of complexity (by using the queues as the node elements of the tree, where the key is base priority times number of threads in that queue).