Hi all,
According to current Haiku source ICMP implementation is only a … framework. Only ICMP echo request messages are processed.
There are essentially two RFCs that should be considered when implementing ICMP (for IPv4). RFC792 - ‘INTERNET CONTROL MESSAGE PROTCOL’ and RFC1122 - ‘Requirements for Internet Hosts – Communication Layers’.
According to RFC1122, paragraph 3.2.2. there are two types of ICMP messages a host must process:
ICMP Error Messages Destination Unreachable Redirect Source Quench Time Exceeded Parameter Problem ICMP query messages: Echo Information Timestamp Address Mask First of all, I plan to implement a generic icmp_send_data() that should be used whenever sending ICMP messages.
Actually is more than half. This quick post is just to inform you that I wrote the part that schedule an isochronous request in the UHCI driver. I’ve already sent the patch to Michael for his review. The only part that is missing is the code that remove the request once it has been processed or canceled, which is not as trivial as I thought.
Personal rant: my university examination session draws near and with it all credit tests as well. I’m doing my best in time management not to put any of my current tasks and projects into starvation, but exactly as Ryan wrote to me - it’s not easy.
Going back to more Haiku-specific topics, last week I was mostly analyzing the .pkg format Be Inc. left us behind. After some tests, most crucial parts of it are clear to me now.
Haiku Admin Meeting 2007-06-04: There was some discussion about the status of several of the GSoC students/mentors now that GSoC has officially begun (May 28th). A couple of minor notes about some website changes were mentioned. Looks like June 4, 2007 was a short meeting :) I would like to remind readers that any official discussion about the decisions made by the Haiku Admins should be directed to the General Mailing List.
Haiku Admin Meeting 2007-05-28: Discussion about new "Admin organizer" internal-use website for managing tasks, admin votes, etc. Some discussion took place about possibly organizing a physical "admin gathering" somewhere. Michael Lotz has volunteered, and is currently a primary candidate for "Project management" type tasks. Mention of the need to assign/complete the Haiku, Inc. 2006 financial publication. Discussed Haiku Compatible Badges: It appears many are currently in favor of Stephan's designs.
As many of you know, I’ve started working even before the SoC started officially. I’ve already sent two patches to both my mentor (Oliver R. Dorantes) and Michael Lotz for review. One of them has already been commited by mmu_man (thanks). The second one is under review. With this latest one, the usb stack manager should be complete, as the QueueIsochronous method has been implemented, along with the CalculateBandwidth. My next move is to implement the UHCI isochronous method.
Hi all,
My name is JiSheng Zhang. I come from China. I am one of the Haiku’s GSOC2007 students. My work is implementing a FireWire stack with support for mass storage and DV cams. I plan to port the FreeBSD FireWire stack. I will do my development under debian.
After google anouncement on April 11, I spent time in building Haiku, running on the real PC and reading the source code of haiku’s PCI and SCSI sub system and other code about driver writing.
Haiku Admin Meeting 2007-05-21: Admins discussed OpenBFS Team broadening - it has currently been renamed to File System Team and should probably include all file system-related aspects of Haiku. There was some further discussion about other OSS projects and their similar struggles with "Openness" - Mozilla's recent scrutiny was cited as an example. There was a request for any final comments on the list of non-dev/non-admin tasks posted on the Admin mailing list.
This is a report of the meeting of the API documentation team that was held on May 18th 2007 at 19:00 GMT on freenode.org in the #haiku-doc channel. The full IRC log is hosted by John Drinkwater. Here are some of the highlights for those that don't want to read the complete document. In this meeting people introduced themselves to the group. There was discussion on the working process, and it was decided to create a three phase working process and to start on the support kit.
The decision to summarize and publish regular Haiku Admin meetings is a step being taken to improve transparency and openness largely as a result of recent and past community feedback on the mailing list. Additionally, there has been an Admin Team Page provided with some details about the current membership and responsibilities of the Haiku Admin Team.
Haiku Admin Meeting 2007-05-14:
The meeting started off with a reminder to subscribe to the new Haiku Development Mailing List if any attendees had not done so yet.
