- Add some new entries

This commit is contained in:
Gabor Kovesdan 2009-10-07 19:52:24 +00:00
parent e56bb9e084
commit 9f571536e4
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=34775

View file

@ -2,7 +2,7 @@
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status
Report//EN"
"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<!-- $FreeBSD: www/en/news/status/report-2009-04-2009-09.xml,v 1.4 2009/10/06 18:32:49 danger Exp $ -->
<!-- $FreeBSD: www/en/news/status/report-2009-04-2009-09.xml,v 1.5 2009/10/07 19:25:06 gabor Exp $ -->
<report>
<date>
<month>April-September</month>
@ -1421,4 +1421,265 @@ Report//EN"
</task>
</help>
</project>
<project cat='arch'>
<title>FreeBSD/sparc64</title>
<contact>
<person>
<name>
<given>Marius</given>
<common>Strobl</common>
</name>
<email>marius@FreeBSD.org</email>
</person>
</contact>
<links/>
<body>
<p>Noteworthy developments regarding FreeBSD/sparc64 since the last
Status Reports are:</p>
<ul>
<li>Cas(4), a driver for Sun Cassini/Cassini+, as well as
National Semiconductor DP83065 Saturn Gigabit NICs has been
committed and thus will be part of FreeBSD beginning with
8.0-RELEASE and 7.3-RELEASE, respectively. This means that
the on-board NICs found in Fire V440, as well as the add-on
cards based on these chips are now supported, including on
non-sparc64 machines. Unfortunately, it triggers, what
seem to be secondary problems with the on-board NICs found in
B100 blades and Fire V480, which due to lack of access to such
systems could not be fixed so far.</li>
<li>Initial support for sun4u machines based on the "Fire"
Host-PCI-Express bridge like Fire V215, V245, etc. has been
completed (including support for the on-board ATA controller,
which caused several problems at first, and MSI/MSI-X). Some
code like the quirk handling for the ALi/ULi chips found in
these machines needs to be revisited though and no stability
tests have been conducted so far. If all goes well, the code
will hit HEAD some time after FreeBSD 8.0-RELEASE has been
released. In theory, machines based on the "Oberon"
Host-PCI-Express bridge, at least for the most part, should
also be supported with these changes, but due to lack of access
to a Mx000 series machine the code could not be tested with
these so far.</li>
<li>Some bugs in the snd_t4dwave(4) driver have been fixed, as
well as some special handling for sparc64 has been added so
it does 32-bit DMA and now generally works with the on-board
ALi M5451 found for example in Blade 100 and Blade 1500.
Unfortunately, it was only tested to work correctly in two out
of three Blade 100. Why it still does not work correctly in
the remaining one is currently unknown but at least no longer
causes IOMMU-panics so testing snd_t4dwave(4) on sparc64 is no
longer harmful. These changes will be part of
FreeBSD 8.0-RELEASE and 7.3-RELEASE.</li>
<li>Ata-marvell(4) has been fixed to work on sparc64 (actually
also on anything that is not x86 with less than 4GB of RAM).
These fixes will be part of FreeBSD 8.0-RELEASE and
7.3-RELEASE.</li>
<li>A proper and machine-independent fix for the old problem
that the loader leaves the NIC opened by the firmware,
which could lead to panics during boot when netbooting,
has been developped but not committed yet.</li>
</ul>
</body>
<help/>
</project>
<project cat='proj'>
<title>NFSv4 ACLs</title>
<contact>
<person>
<name>
<given>Edward Tomasz</given>
<common>Napierala</common>
</name>
<email>trasz@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://wiki.freebsd.org/NFSv4_ACLs"/>
</links>
<body>
<p>During Google Summer of Code 2008, I have implemented native support
for NFSv4 ACLs for both ZFS and UFS. Most of the code has already been
merged to CURRENT. NFSv4 ACLs are unconditionally enabled in ZFS and
the usual tools, like getfacl(1) and setfacl(1) can be used to view and
change them. I plan to merge remaining bits (UFS support) this month.
It should be possible to MFC it in order to ship in
FreeBSD 8.1-RELEASE.</p>
</body>
<help>
<task>UFS changes review</task>
<task>Support for NFSv4 ACLs in tar(1)</task>
</help>
</project>
<project cat='misc'>
<title>Google Summer of Code 2009</title>
<contact>
<person>
<name>
<given>Brooks</given>
<common>Davis</common>
</name>
<email>brooks@freebsd.org</email>
</person>
<person>
<name>
<given>Tim</given>
<common>Kientzle</common>
</name>
<email>kientzle@freebsd.org</email>
</person>
<person>
<name>
<given>Robert</given>
<common>Watson</common>
</name>
<email>rwatson@freebsd.org</email>
</person>
</contact>
<links>
<url href="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd">FreeBSD
GSoC Homepage</url>
<url href="http://wiki.freebsd.org/SummerOfCode2009Projects">FreeBSD GSoC
2009 Wiki</url>
</links>
<body>
<p>2009 was The FreeBSD Project's fifth year of participation
in the Google Summer of Code. We had a total of 17 successful projects.
Some GSoC code will be shipping with FreeBSD 8.0-RELEASE and others
will be integrated into future releases.</p>
<p>The FreeBSD GSoC admin team would like to thank Google and
our students and mentors of another great year!</p>
</body>
</project>
<project cat='proj'>
<title>FreeBSD TDM Framework</title>
<contact>
<person>
<name>
<given>Rafal</given>
<common>Czubak</common>
</name>
<email>rcz@semihalf.com</email>
</person>
<person>
<name>
<given>Michal</given>
<common>Hajduk</common>
</name>
<email>mih@semihalf.com</email>
</person>
</contact>
<body>
<p>This work's purpose is a generic and flexible framework for systems
equipped with Time Division Multiplexing (TDM) units, often found on
embedded telecom chips. The framework is designed to support various
controllers and many types of TDM channels e.g. voiceband, sound and
miscellaneous data channels. Currently, voiceband infrastructure is
being developed on Marvell RD-88F6281 reference board. It will serve
as an example of how to use the TDM framework for other channel types.
The direct objective of using TDM with voiceband channels is bringing
a FreeBSD based VoIP system, capable of bridging analog telephone world
with digital IP telephony. Together with third party VoIP software
(e.g. Asterisk), the design can serve as VoIP Private Branch Exchange
(PBX).</p>
<p>Current state highlights:</p>
<ul>
<li>TDM controller interface</li>
<li>TDM channel interface</li>
<li>TDM channel API for kernel modules</li>
<li>codec interface</li>
<li>voiceband channel character device driver</li>
<li>TDM controller driver for Marvell Kirkwood and Discovery SoCs</li>
<li>Si3215 SLIC driver</li>
<li>Si3050 DAA driver</li>
</ul>
</body>
<help>
<task>Develop demo application showing example usage of voiceband
channel.</task>
<task>Integrate voiceband infrastructure with Zaptel/DAHDI telephony
hardware drivers.</task>
</help>
</project>
<project cat='team'>
<title>Release Engineering Status Report</title>
<contact>
<person>
<name>
<given>Release Engineering Team</given>
</name>
<email>re@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.FreeBSD.org/releng/" />
</links>
<body>
<p>The Release Engineering Team continues to work on FreeBSD
8.0-RELEASE. Public testing has turned up quite a few problems,
many related to the low-level network (routing/ARP table) changes
and their interactions with IPv6.</p>
<p>Progress continues to be made on fixing up the issues that have
been identified during the public testing. At this point in time
we are shooting for two more public test builds (RC2 and RC3)
followed by the release late October or early November.</p>
</body>
</project>
</report>