git: 3847af12e0 - main - status/2022q1: Fix several small nits noticed late
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 10 Jun 2022 03:03:36 UTC
The branch main has been updated by debdrup:
URL: https://cgit.FreeBSD.org/doc/commit/?id=3847af12e0c7eb057deb95f7dd7aa0eab65ac92a
commit 3847af12e0c7eb057deb95f7dd7aa0eab65ac92a
Author: Daniel Ebdrup Jensen <debdrup@FreeBSD.org>
AuthorDate: 2022-06-10 02:52:24 +0000
Commit: Daniel Ebdrup Jensen <debdrup@FreeBSD.org>
CommitDate: 2022-06-10 02:52:24 +0000
status/2022q1: Fix several small nits noticed late
A couple of reports had incorrect syntax for proper display, such as
having or not having the + indicator to indicate that the subsequent
text should be on the line below, as well as a few blank spaces that
made it past previous passes.
Also attempt to use manual page link generation where appropriate.
While here, convert everything to one sentence per line.
---
.../report-2022-01-2022-03/accessibility.adoc | 5 +-
.../report-2022-01-2022-03/boot-performance.adoc | 28 ++---
.../en/status/report-2022-01-2022-03/dpaa2.adoc | 25 ++--
.../report-2022-01-2022-03/freebsd-foundation.adoc | 138 +++++++--------------
.../en/status/report-2022-01-2022-03/kde.adoc | 5 +-
.../en/status/report-2022-01-2022-03/ocf-wg.adoc | 19 ++-
.../en/status/report-2022-01-2022-03/office.adoc | 5 +-
.../status/report-2022-01-2022-03/portconfig.adoc | 26 ++--
.../en/status/report-2022-01-2022-03/rtw88.adoc | 2 +-
.../en/status/report-2022-01-2022-03/wifibox.adoc | 59 +++------
10 files changed, 110 insertions(+), 202 deletions(-)
diff --git a/website/content/en/status/report-2022-01-2022-03/accessibility.adoc b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc
index f91908d2c8..7ad1cdc052 100644
--- a/website/content/en/status/report-2022-01-2022-03/accessibility.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc
@@ -2,10 +2,9 @@
Links: +
link:https://wiki.freebsd.org/Accessibility[Accessibility wiki page] URL: link:https://wiki.freebsd.org/Accessibility[https://wiki.freebsd.org/Accessibility] +
-link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[List introduction, goals, audience, and ground rules] URL: link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html] +
-
+link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[List introduction, goals, audience, and ground rules] URL: link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html]
Contact: Pau Amma <pauamma@gundo.com> +
-Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org>
+Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org>
Over the past several months, I've started putting together tools and resources to help make the FreeBSD ecosystem (more) accessible to people with disabilities:
diff --git a/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc
index 3d0503f1cc..cb159b69f6 100644
--- a/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc
@@ -7,31 +7,21 @@ link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html
Contact: Colin Percival <cperciva@FreeBSD.org>
Colin Percival is coordinating an effort to speed up the FreeBSD boot process.
-For benchmarking purposes, he is primarily using an EC2 c5.xlarge instance as a
-reference platform and is measuring the time between when the virtual machine
-enters the EC2 "running" state and when it is possible to SSH into the instance.
+For benchmarking purposes, he is primarily using an EC2 c5.xlarge instance as a reference platform and is measuring the time between when the virtual machine enters the EC2 "running" state and when it is possible to SSH into the instance.
-This work started in 2017, and as of the end of December 2021 the FreeBSD boot
-time was reduced from approximately 30 seconds to approximately 10 seconds.
-During 2022Q1, further improvements have shaved more time off the boot process,
-taking it down to roughly 8 seconds.
+This work started in 2017, and as of the end of December 2021 the FreeBSD boot time was reduced from approximately 30 seconds to approximately 10 seconds.
+During 2022Q1, further improvements have shaved more time off the boot process, taking it down to roughly 8 seconds
Two major issues remain outstanding:
-. The first time an EC2 instance boots, dhclient takes about 2 seconds longer
-than normal to get an IPv4 address. The cause of this is unknown and requires
-investigation.
+. The first time an EC2 instance boots, dhclient takes about 2 seconds longer than normal to get an IPv4 address. The cause of this is unknown and requires investigation.
-. IPv6 configuration includes two one-second-long sleep(1) invocations, one
-from /etc/rc.d/netif and the other from /etc/rc.d/rtsold. It might be possible
-to simply remove these; but care is needed to avoid progressing too far in the
-boot process before IPv6 addresses are configured. Input from IPv6 experts
-is required here.
+. IPv6 configuration includes two one-second-long sleep(1) invocations, one from /etc/rc.d/netif and the other from /etc/rc.d/rtsold.
+It might be possible to simply remove these; but care is needed to avoid progressing too far in the boot process before IPv6 addresses are configured.
+Input from IPv6 experts is required here.
-Issues are listed on the wiki page as they are identified; the wiki page also
-has instructions for performing profiling. Users are encouraged to profile
-the boot process on their own systems, in case they experience delays which
-don't show up on the system Colin is using for testing.
+Issues are listed on the wiki page as they are identified; the wiki page also has instructions for performing profiling.
+Users are encouraged to profile the boot process on their own systems, in case they experience delays which don't show up on the system Colin is using for testing.
This work is supported by Colin's FreeBSD/EC2 Patreon.
diff --git a/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc
index 3ccc689b10..b7fdc16a03 100644
--- a/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc
@@ -1,4 +1,4 @@
-== NXP DPAA2 support
+=== NXP DPAA2 support
Links +
link:https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[Development] URL: https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2] +
@@ -6,21 +6,14 @@ link:https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[De
Contact: Dmitry Salychev <dsl@mcusim.org> +
Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
-Some of the NXP SoCs (LX2160A, LS1088A) are shipped with
-link:https://www.nxp.com/design/qoriq-developer-resources/second-generation-data-path-acceleration-architecture-dpaa2:DPAA2[DPAA2],
-the second generation of the data path acceleration architecture. It allows to
-dynamically configure and wire packet processing "objects" (like DPNI for a
-network interface, DPMAC for media access controller, etc.) together to form a
-network-on-a-chip.
-
-link:https://solidrun.atlassian.net/wiki/spaces/developer/pages/197494288/HoneyComb+LX2+ClearFog+CX+LX2+Quick+Start+Guide[Honeycomb LX2],
-as one of the powerful ARM64 boards from SolidRun, is also built around NXP
-LX2160A and lacks on-board GbE support in FreeBSD. These drivers are about to
-change it.
-
-It's still work in progress and a rough implementation of the drivers for some
-DPAA2 objects is available at the moment. A new network interface (dpni) can be
-used on Honeycomb for testing.
+Some of the NXP SoCs (LX2160A, LS1088A) are shipped with link:https://www.nxp.com/design/qoriq-developer-resources/second-generation-data-path-acceleration-architecture-dpaa2:DPAA2[DPAA2], the second generation of the data path acceleration architecture.
+It allows to dynamically configure and wire packet processing "objects" (like DPNI for a network interface, DPMAC for media access controller, etc.) together to form a network-on-a-chip.
+
+link:https://solidrun.atlassian.net/wiki/spaces/developer/pages/197494288/HoneyComb+LX2+ClearFog+CX+LX2+Quick+Start+Guide[Honeycomb LX2], as one of the powerful ARM64 boards from SolidRun, is also built around NXP LX2160A and lacks on-board GbE support in FreeBSD.
+These drivers are about to change it.
+
+It's still work in progress and a rough implementation of the drivers for some DPAA2 objects is available at the moment.
+A new network interface (dpni) can be used on Honeycomb for testing.
TODO:
diff --git a/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc
index 71be9af883..fad2959648 100644
--- a/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc
@@ -6,86 +6,58 @@ link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap]
link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] +
link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] +
link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] +
-link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/] +
+link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/]
Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
-The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated
-to supporting and promoting the FreeBSD Project and community
-worldwide. Donations from individuals and corporations are used to fund
-and manage software development projects, conferences, and developer
-summits. We also provide travel grants to FreeBSD contributors, purchase
-and support hardware to improve and maintain FreeBSD infrastructure, and
-provide resources to improve security, quality assurance, and release
-engineering efforts. We publish marketing material to promote, educate,
-and advocate for the FreeBSD Project, facilitate collaboration between
-commercial vendors and FreeBSD developers, and finally, represent the
-FreeBSD Project in executing contracts, license agreements, and other
-legal arrangements that require a recognized legal entity.
-
-Here are some highlights from the Foundation for the first quarter of
-2022.
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits.
+We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts.
+We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+Here are some highlights from the Foundation for the first quarter of 2022.
==== Fundraising Efforts
-As promised, we updated our fundraising meter for 2022. So far, we’ve
-raised over $84,000 towards our 2022 goal of $1,400,000. We’d like to
-thank our individual and corporate donors for supporting our efforts
-this year. We’d also like to give a big shout out to our Gold Sponsor,
-Facebook, Silver Sponsors, VMware and Tarsnap, and the companies that
-provide free hosting for the Project: Bytemark, 365 Data Centers, NYI,
-NextArray, Sentex Data Communications, and the Computer Science
-Department at NCTU.
+As promised, we updated our fundraising meter for 2022. So far, we’ve raised over $84,000 towards our 2022 goal of $1,400,000.
+We’d like to thank our individual and corporate donors for supporting our efforts this year.
+We’d also like to give a big shout out to our Gold Sponsor, Facebook, Silver Sponsors, VMware and Tarsnap, and the companies that provide free hosting for the Project: Bytemark, 365 Data Centers, NYI, NextArray, Sentex Data Communications, and the Computer Science Department at NCTU.
-You can find out how we spent your donations by reading about what we
-supported in Q1, in this report, and our Spring Newsletter.
+You can find out how we spent your donations by reading about what we supported in Q1, in this report, and our Spring Newsletter.
-If you haven’t made a donation this year, please consider making a donation
-now at https://freebsdfoundation.org/donate/.
+If you haven’t made a donation this year, please consider making a donation now at https://freebsdfoundation.org/donate/.
-We also have a Partnership Program for larger commercial donors. You can
-find out more at
-https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
+We also have a Partnership Program for larger commercial donors. You can find out more at https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
==== OS Improvements
-During the first quarter of 2022, 372 src, 41 ports, and 16 doc tree
-commits were made that identified The FreeBSD Foundation as a sponsor.
+During the first quarter of 2022, 372 src, 41 ports, and 16 doc tree commits were made that identified The FreeBSD Foundation as a sponsor.
# This represents 16, 0.4, and 5% of the total number of commits in each repository.
-You can read about Foundation-sponsored projects in individual quarterly report
-entries:
+You can read about Foundation-sponsored projects in individual quarterly report entries:
* Crypto changes for WireGuard
* Intel Wireless driver support
-Here is a small sample of other base system improvements from Foundation
-developers this quarter that do not have separate report entries.
+Here is a small sample of other base system improvements from Foundation developers this quarter that do not have separate report entries.
==== riscv: Add support for enabling SV48 mode
-SV48 is intended for systems for which a 39-bit virtual address space is
-insufficient. This change increases the size of the user map from 256GB
-to 128TB. The kernel map is left unchanged for now.
+SV48 is intended for systems for which a 39-bit virtual address space is insufficient. This change increases the size of the user map from 256GB to 128TB.
+The kernel map is left unchanged for now.
-For now SV48 mode is left disabled by default, but can be enabled with a
-tunable. Note that extant hardware does not implement SV48, but QEMU
-does.
+For now SV48 mode is left disabled by default, but can be enabled with a tunable.
+Note that extant hardware does not implement SV48, but QEMU does.
-* In pmap_bootstrap(), allocate a L0 page and attempt to enable SV48
- mode. If the write to SATP doesn't take, the kernel continues to run
- in SV39 mode.
-* Define VM_MAX_USER_ADDRESS to refer to the SV48 limit. In SV39 mode,
- the region [VM_MAX_USER_ADDRESS_SV39, VM_MAX_USER_ADDRESS_SV48] is not
- mappable.
+* In pmap_bootstrap(), allocate a L0 page and attempt to enable SV48 mode.
+ If the write to SATP doesn't take, the kernel continues to run in SV39 mode.
+* Define VM_MAX_USER_ADDRESS to refer to the SV48 limit.
+ In SV39 mode, the region [VM_MAX_USER_ADDRESS_SV39, VM_MAX_USER_ADDRESS_SV48] is not mappable.
==== Add v3 support to CTF tools
-CTF, the Compact C Type Format, is a representation of type information
-most often contained within ELF binaries. This type information is
-helpful for probing tools like DTrace. Recent work by Mark Johnston
-allows different Dtrace providers like the FBT (Function Boundary
-Tracing) provider to work with version 3 of CTF.
+CTF, the Compact C Type Format, is a representation of type information most often contained within ELF binaries.
+This type information is helpful for probing tools like DTrace.
+Recent work by Mark Johnston allows different Dtrace providers like the FBT (Function Boundary Tracing) provider to work with version 3 of CTF.
==== FreeBSD on the Framework Laptop
@@ -103,16 +75,12 @@ You can follow news about FreeBSD work on the Framework laptop at: https://wiki.
==== Continuous Integration and Quality Assurance
-The Foundation provides a full-time staff member and funds projects to improve
-continuous integration, automated testing, and overall quality assurance efforts
-for the FreeBSD project.
+The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project.
==== Supporting FreeBSD Infrastructure
-The Foundation provides hardware and support for the Project. At the
-time of writing, the server that will become the new Australian mirror
-has arrived in Australia, has a fresh FreeBSD install and will shortly
-join the cluster.
+The Foundation provides hardware and support for the Project.
+At the time of writing, the server that will become the new Australian mirror has arrived in Australia, has a fresh FreeBSD install and will shortly join the cluster.
==== FreeBSD Advocacy and Education
@@ -124,27 +92,19 @@ or contribution easier. Other than attending and presenting at events,
we encourage and help community members run their own FreeBSD events,
give presentations, or staff FreeBSD tables.
-The FreeBSD Foundation sponsors many conferences, events, and summits
-around the globe. These events can be BSD-related, open source, or
-technology events geared towards underrepresented groups. We support the
-FreeBSD-focused events to help provide a venue for sharing knowledge,
-working together on projects, and facilitating collaboration between
-developers and commercial users. This all helps provide a healthy
-ecosystem. We support the non-FreeBSD events to promote and raise
-awareness of FreeBSD, to increase the use of FreeBSD in different
-applications, and to recruit more contributors to the Project. We are
-continuing to attend virtual events and began planning the June 2022
-Developer Summit.
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups.
+We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.
+This all helps provide a healthy ecosystem.
+We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.
+We are continuing to attend virtual events and began planning the June 2022 Developer Summit.
Check out some of the advocacy and education work we did last quarter:
* Committed to hosting a FreeBSD Workshop at SCALE 19x and serve as a Media Sponsor - July 28-31, 2022 in Los Angeles, CA
-* Participated in the FLOSS Weekly Podcast - January 5, 2022
- https://twit.tv/shows/floss-weekly/episodes/662
+* Participated in the FLOSS Weekly Podcast - January 5, 2022 https://twit.tv/shows/floss-weekly/episodes/662
-* Sent out the 2021 Impact Report showcasing how we supported the Project last year.
- https://freebsdfoundation.org/blog/2021-freebsd-foundation-impact-report/
+* Sent out the 2021 Impact Report showcasing how we supported the Project last year. https://freebsdfoundation.org/blog/2021-freebsd-foundation-impact-report/
* Hosted a stand at FOSDEM 2022 - Videos from the stand can be found at: https://youtube.com/playlist?list=PLugwS7L7NMXxwqIRg1PlhgzhNRi1eVdRQ
@@ -152,16 +112,13 @@ Check out some of the advocacy and education work we did last quarter:
* Began planning the June 2022 FreeBSD Developers Summit taking place virtually, June 16-17, 2022 https://wiki.freebsd.org/DevSummit/202206
-* Held a new FreeBSD Friday - How to Track FreeBSD Using Git Pt. 2
- https://youtu.be/Fe-dJrDMK_0
+* Held a new FreeBSD Friday - How to Track FreeBSD Using Git Pt. 2 https://youtu.be/Fe-dJrDMK_0
-* Presented at the St. Louis Unix User Group on March 9, 2022
- https://ow.ly/1QXn50Ivj75
+* Presented at the St. Louis Unix User Group on March 9, 2022 https://ow.ly/1QXn50Ivj75
* Served as Admins and were accepted as a mentoring organization for the 2022 Google Summer of Code
-* Held an Office Hours session on Google Summer of Code.
- https://youtu.be/x-4U1xurmBE
+* Held an Office Hours session on Google Summer of Code. https://youtu.be/x-4U1xurmBE
* Hosted a booth at the virtual Open Source 101 conference on March 29, 2022
@@ -175,19 +132,14 @@ Check out some of the advocacy and education work we did last quarter:
* New FreeBSD Journal Article: link:https://freebsdfoundation.org/wp-content/uploads/2022/04/Contributing-to-FreeBSD-Ports-with-Git.pdf[Contributing to FreeBSD ports with Git]
-We help educate the world about FreeBSD by publishing the professionally
-produced FreeBSD Journal. As we mentioned previously, the FreeBSD
-Journal is now a free publication. Find out more and access the latest
-issues at https://www.FreeBSDfoundation.org/journal/
+We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal.
+As we mentioned previously, the FreeBSD Journal is now a free publication.
+Find out more and access the latest issues at https://www.FreeBSDfoundation.org/journal/
-You can find out more about events we attended and upcoming events at
-https://www.FreeBSDfoundation.org/news-and-events/.
+You can find out more about events we attended and upcoming events at https://www.FreeBSDfoundation.org/news-and-events/.
==== Legal/FreeBSD IP
-The Foundation owns the FreeBSD trademarks, and it is our responsibility to
-protect them. We also provide legal support for the core team to investigate
-questions that arise.
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise.
-Go to link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org]
-to find more about how we support FreeBSD and how we can help you!
+Go to link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2022-01-2022-03/kde.adoc b/website/content/en/status/report-2022-01-2022-03/kde.adoc
index 8c88b635d1..f0baa843a0 100644
--- a/website/content/en/status/report-2022-01-2022-03/kde.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/kde.adoc
@@ -11,7 +11,10 @@ The software includes a full desktop environment called KDE Plasma (for both X11
The KDE team (kde@) is part of desktop@ and x11@ as well, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine.
-*KDE Qt Patch Collection* The Qt Company did not release Qt 5.15 updates under Open Source licenses in 2021, leaving the Open Source 5.15 version lagging behind the proprietary release. Qt 6 is released under an Open Source license, but for the world of Open Source software that requires Qt 5, there is still a need for updates. The KDE Community fills that need by maintaining a curated set of patches -- generally backported from Qt6 -- to maintain the Open Source version of Qt 5. FreeBSD ports now use this *KDE Qt Patch Collection*, rather than the outdated last Qt 5.15.2 release from the Qt Company.
+*KDE Qt Patch Collection* The Qt Company did not release Qt 5.15 updates under Open Source licenses in 2021, leaving the Open Source 5.15 version lagging behind the proprietary release.
+Qt 6 is released under an Open Source license, but for the world of Open Source software that requires Qt 5, there is still a need for updates.
+The KDE Community fills that need by maintaining a curated set of patches -- generally backported from Qt6 -- to maintain the Open Source version of Qt 5.
+FreeBSD ports now use this *KDE Qt Patch Collection*, rather than the outdated last Qt 5.15.2 release from the Qt Company.
This landed both in main and the last quarterly branch for 2021, since it brings important bugfixes.
==== KDE Stack
diff --git a/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc b/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc
index 0d5abf64da..b8f6f51fc8 100644
--- a/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc
@@ -2,16 +2,13 @@
Contact: John Baldwin <jhb@FreeBSD.org>
-During the last quarter, I continued my work to improve the FreeBSD
-WireGuard driver. On the FreeBSD side, I added support for the
-XChaCha20-Poly1305 AEAD cipher. I also added a dedicated API to support
-[X]ChaCha20-Poly1035 on small, flat buffers. Finally, I added an API
-wrapper for the curve25519 implementation from libsodium.
-
-For the WireGuard driver, I wrote a series of patches which updates the
-driver to use crypto APIs such as those mentioned above in place of
-internal cipher implementations. The series also includes a fix to
-avoid scheduling excessive crypto tasks as well as a few other small
-fixes. This series is pending review.
+During the last quarter, I continued my work to improve the FreeBSD WireGuard driver.
+On the FreeBSD side, I added support for the XChaCha20-Poly1305 AEAD cipher.
+I also added a dedicated API to support [X]ChaCha20-Poly1035 on small, flat buffers.
+Finally, I added an API wrapper for the curve25519 implementation from libsodium.
+
+For the WireGuard driver, I wrote a series of patches which updates the driver to use crypto APIs such as those mentioned above in place of internal cipher implementations.
+The series also includes a fix to avoid scheduling excessive crypto tasks as well as a few other small fixes.
+This series is pending review.
Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-01-2022-03/office.adoc b/website/content/en/status/report-2022-01-2022-03/office.adoc
index a7175b9377..5b1503d300 100644
--- a/website/content/en/status/report-2022-01-2022-03/office.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/office.adoc
@@ -1,7 +1,7 @@
=== FreeBSD Office Team
Links: +
-link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[https://wiki.freebsd.org/Office]
+link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[https://wiki.freebsd.org/Office] +
link:https://lists.freebsd.org/subscription/freebsd-office[The FreeBSD Office mailing list] URL: link:https://lists.freebsd.org/subscription/freebsd-office[https://lists.freebsd.org/subscription/freebsd-office]
Contact: FreeBSD Office team ML <office@FreeBSD.org> +
@@ -12,8 +12,7 @@ The FreeBSD Office team works on a number of office-related software suites and
Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users.
-During the 2022Q1 period we pushed maintenance patches for the LibreOffice 7.2 port to the quarterly branch and brought the latest, 7.3, releases
-and all companion libraries such as MDDS, libIxion and more to the ports tree.
+During the 2022Q1 period we pushed maintenance patches for the LibreOffice 7.2 port to the quarterly branch and brought the latest, 7.3, releases and all companion libraries such as MDDS, libIxion and more to the ports tree.
Also we are still working on the link:https://github.com/fluffykhv/freebsd-ports-boost[Boost WIP repository] to bring the latest Boost library to the ports.
diff --git a/website/content/en/status/report-2022-01-2022-03/portconfig.adoc b/website/content/en/status/report-2022-01-2022-03/portconfig.adoc
index 11401ab1f0..205201ff8c 100644
--- a/website/content/en/status/report-2022-01-2022-03/portconfig.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/portconfig.adoc
@@ -1,24 +1,18 @@
=== PortConfig
-Links
-link:https://gitlab.com/alfix/portconfig/[Repository portconfig] URL: link:https://gitlab.com/alfix/portconfig/[https://gitlab.com/alfix/portconfig/] +
+Links: +
+link:https://gitlab.com/alfix/portconfig/[Repository portconfig] URL: link:https://gitlab.com/alfix/portconfig/[https://gitlab.com/alfix/portconfig/]
-Contact: Alfonso Sabato Siciliano (upstream) <asiciliano@FreeBSD.org>
+Contact: Alfonso Sabato Siciliano (upstream) <asiciliano@FreeBSD.org> +
Contact: Baptiste Daroussin (port) <bapt@FreeBSD.org>
-FreeBSD provides the Ports Collection to give users and administrators a
-simple way to install applications. It is possible to configure a port before
-the building and installation. PortConfig is an utility for setting the port
-options via a Text User Interface.
+FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications.
+It is possible to configure a port before the building and installation.
+PortConfig is an utility for setting the port options via a Text User Interface.
-As each terminal has different properties PortConfig can be customized via
-environment variables to set up the User Interface, for example: menu size,
-theme, borders, and so on; each feature is documented inside the manual.
-Further, if a port has a specific 'pkg-help' file, PortConfig will show a Help
-button to open a "popup" with help information.
+As each terminal has different properties PortConfig can be customized via environment variables to set up the User Interface, for example: menu size, theme, borders, and so on; each feature is documented inside the manual.
+Further, if a port has a specific 'pkg-help' file, PortConfig will show a Help button to open a "popup" with help information.
-FreeBSD provides thousands of ports therefore it is not feasible to test
-PortConfig for each use; please report any problem.
+FreeBSD provides thousands of ports therefore it is not feasible to test PortConfig for each use; please report any problem.
-Alfonso would like to thank Baptiste Daroussin for the port, suggestions, help, and
-testing for this utility and its library.
+Alfonso would like to thank Baptiste Daroussin for the port, suggestions, help, and testing for this utility and its library.
diff --git a/website/content/en/status/report-2022-01-2022-03/rtw88.adoc b/website/content/en/status/report-2022-01-2022-03/rtw88.adoc
index f63f007dce..8d7a852b40 100644
--- a/website/content/en/status/report-2022-01-2022-03/rtw88.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/rtw88.adoc
@@ -1,7 +1,7 @@
=== Realtek Wireless driver support
Links: +
-link:https://wiki.freebsd.org/WiFi/Rtw88[rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88]
+link:https://wiki.freebsd.org/WiFi/Rtw88[rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88] +
link:https://wiki.freebsd.org/WiFi/Rtw89[rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89]
Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
diff --git a/website/content/en/status/report-2022-01-2022-03/wifibox.adoc b/website/content/en/status/report-2022-01-2022-03/wifibox.adoc
index bb245a2210..6edbf18e57 100644
--- a/website/content/en/status/report-2022-01-2022-03/wifibox.adoc
+++ b/website/content/en/status/report-2022-01-2022-03/wifibox.adoc
@@ -6,45 +6,26 @@ link:https://cgit.freebsd.org/ports/tree/net/wifibox[``net/wifibox`` port]
Contact: PÁLI Gábor János <pali.gabor@gmail.com>
-Wifibox is an experimental project for exploring the ways of deploying
-a virtualized Linux guest to drive wireless networking cards on the
-FreeBSD host system. There have been guides on the Internet to
-suggest the use of such techniques to improve the wireless networking
-experience, of which Wifibox aims to implement as a single easy-to-use
-software package.
-
-- ``bhyve(8)`` is utilized to run the embedded Linux system. This
- helps to achieve low resource footprint. It requires an x64 CPU
- with I/O MMU (AMD-Vi, Intel VT-d), ~150 MB physical memory, and some
- disk space available for the guest virtual disk image, which can be
- even ~30 MB only in certain cases. It works with FreeBSD 12 and
- later, some cards may require a recent 13-STABLE though.
-
-- The guest is constructed using https://alpinelinux.org/[Alpine
- Linux], a security-oriented, lightweight distribution based on
- https://www.musl-libc.org/[musl libc] and
- https://busybox.net/[BusyBox].
-
-- Configuration files are shared with the host system. The guest uses
- ``wpa_supplicant(8)`` so it is possible to import the host's
- ``wpa_supplicant.conf(5)`` file without any changes.
-
-- When configured, ``wpa_supplicant(8)`` control sockets could be
- exposed by the guest, which enables use of related utilities
- directly from the host, such as ``wpa_cli(8)`` or ``wpa_gui(8)``
- from the ``net/wpa_supplicant_gui`` package.
-
-- Everything is shipped in a single package that can be easily
- installed and removed. This comes with an ``rc(8)`` system service
- that automatically launches the guest on boot and stops it on
- shutdown.
+Wifibox is an experimental project for exploring the ways of deploying a virtualized Linux guest to drive wireless networking cards on the FreeBSD host system.
+There have been guides on the Internet to suggest the use of such techniques to improve the wireless networking experience, of which Wifibox aims to implement as a single easy-to-use software package.
+
+- man:bhyve[8] is utilized to run the embedded Linux system.
+ This helps to achieve low resource footprint.
+ It requires an x64 CPU with I/O MMU (AMD-Vi, Intel VT-d), ~150 MB physical memory, and some disk space available for the guest virtual disk image, which can be even ~30 MB only in certain cases.
+ It works with FreeBSD 12 and later, some cards may require a recent 13-STABLE though.
+
+- The guest is constructed using https://alpinelinux.org/[Alpine Linux], a security-oriented, lightweight distribution based on https://www.musl-libc.org/[musl libc] and https://busybox.net/[BusyBox].
+
+- Configuration files are shared with the host system. The guest uses man:wpa_supplicant[8] so it is possible to import the host's man:wpa_supplicant.conf[8] file without any changes.
+
+- When configured, man:wpa_supplicant[8] control sockets could be exposed by the guest, which enables use of related utilities directly from the host, such as man:wpa_cli[8] or man:wpa_gui[8] from the ``net/wpa_supplicant_gui`` port/package.
+
+- Everything is shipped in a single package that can be easily installed and removed.
+ This comes with an man:rc[8] system service that automatically launches the guest on boot and stops it on shutdown.
- A workaround is supplied for laptops to support suspend/resume.
-Wifibox has been mainly tested with Intel chipsets so far, and it has
-shown great performance and stability. Therefore it might serve as an
-interim solution until the Intel Wireless support becomes mature
-enough. It was confirmed that Wifibox works with Atheros chipsets
-too, and feedback is more than welcome about others. Support for
-Broadcom chipsets is not yet complete, that is currently a work in
-progress.
+Wifibox has been mainly tested with Intel chipsets so far, and it has shown great performance and stability.
+Therefore it might serve as an interim solution until the Intel Wireless support becomes mature enough.
+It was confirmed that Wifibox works with Atheros chipsets too, and feedback is more than welcome about others.
+Support for Broadcom chipsets is not yet complete, that is currently a work in progress.