Editorial tweaks to the 2016Q1 report
Remove some unnecessary quotes, and use " where they remain. (Also sprinkle some more <tt>.) Try to use title case for <url> descriptions, and convert a few FreeBSD into &os;. And more.
This commit is contained in:
parent
b31911d153
commit
f266622398
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=48680
1 changed files with 47 additions and 44 deletions
|
@ -99,7 +99,7 @@
|
|||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="http://www.viva64.com/en/b/0377/">PVS-Studio delved into the FreeBSD kernel</url>
|
||||
<url href="http://www.viva64.com/en/b/0377/">PVS-Studio Delved into the FreeBSD kernel</url>
|
||||
<url href="https://reviews.freebsd.org/D5245">PVS Static Analysis Phabricator Review</url>
|
||||
</links>
|
||||
|
||||
|
@ -221,18 +221,18 @@
|
|||
|
||||
<p>Work is ongoing with respect to development of pNFS support
|
||||
for the NFS server using GlusterFS as a back end. This will
|
||||
be a long term project with the eventual goal of allowing the
|
||||
be a long-term project with the eventual goal of allowing the
|
||||
NFS server to scale beyond a single server system. Hopefully
|
||||
it will be available for testing in late Spring 2016. pNFS
|
||||
allows a NFSv4.1 client to do reads/writes directly to a data
|
||||
allows an NFSv4.1 client to do reads/writes directly to a data
|
||||
server and not the NFS server.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>
|
||||
<p>Development of the pNFS server will be in need of testing
|
||||
or it will never progress to a near production status. I
|
||||
hope to have code available in FreeBSD's subversion projects
|
||||
<p>The pNFS server will be in need of testing during development
|
||||
or it will never progress to a near-production status. I
|
||||
hope to have code available in &os;'s Subversion project
|
||||
branch for testing in late spring 2016.</p>
|
||||
</task>
|
||||
</help>
|
||||
|
@ -252,21 +252,22 @@
|
|||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="https://svnweb.freebsd.org/base/projects/powerpcspe/">Source tree</url>
|
||||
<url href="https://svnweb.freebsd.org/base/projects/powerpcspe/">Source Tree</url>
|
||||
</links>
|
||||
|
||||
<body>
|
||||
<p>The purpose of this is to enable use of the Signal Processing
|
||||
<p>This project aims to enable the use of the Signal Processing
|
||||
Engine found in the NXP/Freescale e500v2 SoC. The SPE uses
|
||||
opcodes overlapping with Altivec, so is mutually exclusive.
|
||||
Additionally, the e500v2 does not have a traditional FPU, and
|
||||
instead uses the SPE for all floating point operations (or
|
||||
emulation as is currently done). Combined with the fact that
|
||||
the SPE ABI is incompatible with traditional ABI, a new
|
||||
MACHINE_ARCH is created to address this.</p>
|
||||
opcodes overlapping with those of Altivec, so they are mutually
|
||||
exclusive. Additionally, the e500v2 does not have a traditional
|
||||
FPU, and instead uses the SPE for all floating point operations
|
||||
(or emulation, as is currently done). Combined with the fact
|
||||
that the SPE ABI is incompatible with the traditional ABI, a new
|
||||
MACHINE_ARCH has been created to address these
|
||||
incompatibilities.</p>
|
||||
|
||||
<p>A project branch has been created with the work. A
|
||||
powerpcspe kernel boots on the RouterBoard RB800, and base
|
||||
<p>A project branch has been created for the work. A
|
||||
powerpcspe kernel boots on the RouterBoard RB800, and the base
|
||||
utilities run properly.</p>
|
||||
</body>
|
||||
|
||||
|
@ -294,12 +295,12 @@
|
|||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</url>
|
||||
<url href="https://github.com/freebsd/freebsd-ports-graphics">Ports development tree on GitHub</url>
|
||||
<url href="https://wiki.freebsd.org/Graphics">Graphics Stack Roadmap and Supported Hardware Matrix</url>
|
||||
<url href="https://github.com/freebsd/freebsd-ports-graphics">Ports Development Tree on GitHub</url>
|
||||
<url href="https://fosdem.org/2016/schedule/event/freebsd_graphic_stack/">FreeBSD Graphics Team at FOSDEM 2016</url>
|
||||
<url href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes">GSoC 2016: link /dev entries to sysctl nodes</url>
|
||||
<url href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_redesign_and_rewrite_libdevq">GSoC 2016: redesign libdevq</url>
|
||||
<url href="http://planet.freebsd.org/graphics/">Graphics team blog</url>
|
||||
<url href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes">GSoC 2016: link <tt>/dev</tt> Entries to <tt>sysctl</tt> Nodes</url>
|
||||
<url href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_redesign_and_rewrite_libdevq">GSoC 2016: Redesign <tt>libdevq</tt></url>
|
||||
<url href="http://planet.freebsd.org/graphics/">Graphics Team Blog</url>
|
||||
</links>
|
||||
|
||||
<body>
|
||||
|
@ -307,7 +308,8 @@
|
|||
driver in the kernel! The driver now matches Linux 3.8.13, so
|
||||
it includes initial Haswell support. Linux 3.8 is already
|
||||
three years old, but work continues to upgrade DRM further.
|
||||
In particular, the move to <tt>linuxkpi</tt> was started.</p>
|
||||
In particular, work commenced to move to using the
|
||||
<tt>linuxkpi</tt> compatibility.</p>
|
||||
|
||||
<p>In the Ports tree, Mesa was updated to 11.1.2. The next minor
|
||||
release, 11.2.0, is ready for testing in our development tree.
|
||||
|
@ -321,21 +323,22 @@
|
|||
how people can contribute. It was well received and the
|
||||
presentation was followed by interesting discussions. FOSDEM
|
||||
was also a nice occasion to meet and talk again to the nice
|
||||
"upstream" developers of the graphics stack.</p>
|
||||
upstream developers of the graphics stack.</p>
|
||||
|
||||
<p>For the first year, we added two ideas for GSoC 2016: one for
|
||||
a kernel task, one to redesign <tt>libdevq</tt>. Six students
|
||||
submitted a proposal for those two ideas, that was unexpected!
|
||||
submitted proposals for those ideas; that was unexpected!
|
||||
We now need to decide which one we want to mentor and the
|
||||
choice is difficult.</p>
|
||||
|
||||
<p>Our blog has moved to
|
||||
<a href="http://planet.freebsd.org/graphics/">Graphics Team blog</a>.</p>
|
||||
<p>Our blog has moved to a
|
||||
<a href="http://planet.freebsd.org/graphics/">new location</a>
|
||||
(linked above).</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>
|
||||
<p>See the "Graphics" wiki page for up-to-date
|
||||
<p>See the "Graphics" wiki page for up-to-date
|
||||
information.</p>
|
||||
</task>
|
||||
</help>
|
||||
|
@ -367,11 +370,11 @@
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>Allwinner SoC are used in multiple hobbyist devboards and
|
||||
single board computers. Recently, support for these SoC have
|
||||
<p>Allwinner SoCs are used in multiple hobbyist devboards and
|
||||
single-board computers. Recently, support for these SoCs has
|
||||
received a lot of updates</p>
|
||||
|
||||
<p>Task done during first quarter :</p>
|
||||
<p>Task done during first quarter:</p>
|
||||
|
||||
<ul>
|
||||
<li>I2C</li>
|
||||
|
@ -397,13 +400,13 @@
|
|||
<li>A20 now uses the ARM Generic Timer</li>
|
||||
</ul>
|
||||
|
||||
<p>Ongoing task :</p>
|
||||
<p>Ongoing tasks:</p>
|
||||
|
||||
<ul>
|
||||
<li>Switch to new clock framework
|
||||
<li>Switch to a new clock framework
|
||||
<a href="https://reviews.freebsd.org/D5752">(In review)</a></li>
|
||||
|
||||
<li>Convert A10 interrupt controller to INTRNG
|
||||
<li>Convert the A10 interrupt controller to INTRNG
|
||||
<a href="https://reviews.freebsd.org/D5573">(In review)</a></li>
|
||||
|
||||
<li>OHCI support
|
||||
|
@ -417,7 +420,7 @@
|
|||
|
||||
<li>USB OTG</li>
|
||||
|
||||
<li>Finish the switch to upstream DTS</li>
|
||||
<li>Finish the switch to using upstream DTS files</li>
|
||||
|
||||
<li>A83T SoC Support</li>
|
||||
|
||||
|
@ -521,7 +524,7 @@
|
|||
|
||||
|
||||
<body>
|
||||
<p>Since the last report &os; support for ThunderX has been
|
||||
<p>Since the last report, &os; support for ThunderX has been
|
||||
significantly improved and stabilized. Semihalf contributions
|
||||
include the following items:</p>
|
||||
|
||||
|
@ -531,14 +534,14 @@
|
|||
maintained.</li>
|
||||
|
||||
<li>Moved to using <tt>pci_host_generic.c</tt> as a main
|
||||
driver for the internal PCIe bridge. Significant rework of
|
||||
PCIe code to support both generic and ThunderX based
|
||||
platforms.</li>
|
||||
driver for the internal PCIe bridge. This involved a
|
||||
significant rework of PCIe code to support both generic and
|
||||
ThunderX based platforms.</li>
|
||||
|
||||
<li> Serious networking performance boost and bug fixes: </li>
|
||||
<li> Serious networking performance boost and bug fixes:</li>
|
||||
<ul>
|
||||
<li>Fixed race condition on Rx path causing very rare
|
||||
‘use after free’ issue</li>
|
||||
<li>Fixed race condition on Rx path causing a very rare
|
||||
"use after free" issue</li>
|
||||
|
||||
<li>Hardware L3 and L4 checksums support</li>
|
||||
|
||||
|
@ -553,7 +556,7 @@
|
|||
</ul>
|
||||
|
||||
<p>The driver supports all available Ethernet connections (1,
|
||||
10, 30 Gbps) and system can saturate 10 Gbps link (on Tx)
|
||||
10, 30 Gbps) and the system can saturate a 10 Gbps link (on Tx)
|
||||
using 4 CPU cores.</p>
|
||||
|
||||
<ul>
|
||||
|
@ -570,7 +573,7 @@
|
|||
</ul>
|
||||
</ul>
|
||||
|
||||
<p>This work is integrated to the FreeBSD HEAD on an on-going
|
||||
<p>This work is integrated to &os; HEAD on an on-going
|
||||
basis.</p>
|
||||
</body>
|
||||
|
||||
|
@ -584,7 +587,7 @@
|
|||
|
||||
<help>
|
||||
<task>
|
||||
<p>Support for multi Queue Set operation in VNIC</p>
|
||||
<p>Add support for multi-Queue Set operation in VNIC.</p>
|
||||
</task>
|
||||
</help>
|
||||
</project>
|
||||
|
|
Loading…
Reference in a new issue