From owner-svn-doc-all@freebsd.org Mon Jun 3 19:52:14 2019 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6445615BC30A; Mon, 3 Jun 2019 19:52:14 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 132026C7A7; Mon, 3 Jun 2019 19:52:14 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C5F49ADB1; Mon, 3 Jun 2019 19:52:13 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x53JqDEX016354; Mon, 3 Jun 2019 19:52:13 GMT (envelope-from trasz@FreeBSD.org) Received: (from trasz@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x53JqDkn016353; Mon, 3 Jun 2019 19:52:13 GMT (envelope-from trasz@FreeBSD.org) Message-Id: <201906031952.x53JqDkn016353@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: trasz set sender to trasz@FreeBSD.org using -f From: Edward Tomasz Napierala Date: Mon, 3 Jun 2019 19:52:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53102 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head X-SVN-Commit-Author: trasz X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/news/status X-SVN-Commit-Revision: 53102 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 132026C7A7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.977,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jun 2019 19:52:14 -0000 Author: trasz Date: Mon Jun 3 19:52:13 2019 New Revision: 53102 URL: https://svnweb.freebsd.org/changeset/doc/53102 Log: Add Quarterly Status Report for 2019Q1. Reviewed by: allanjude, bcr Differential Revision: https://reviews.freebsd.org/D20446 Added: head/en_US.ISO8859-1/htdocs/news/status/report-2019-01-2019-03.xml (contents, props changed) Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Jun 3 09:46:32 2019 (r53101) +++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Jun 3 19:52:13 2019 (r53102) @@ -82,6 +82,7 @@ XMLDOCS+= report-2017-07-2017-09 XMLDOCS+= report-2017-10-2017-12 XMLDOCS+= report-2018-01-2018-09 XMLDOCS+= report-2018-09-2018-12 +XMLDOCS+= report-2019-01-2019-03 XSLT.DEFAULT= report.xsl Added: head/en_US.ISO8859-1/htdocs/news/status/report-2019-01-2019-03.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2019-01-2019-03.xml Mon Jun 3 19:52:13 2019 (r53102) @@ -0,0 +1,2527 @@ + + + + + + + + + + January-March + + 2019 + + +
+ Introduction + +

As spring leads into summer, we reflect back on what the + FreeBSD project has accomplished in the first quarter of 2019. + Events included FOSDEM and AsiaBSDCon, the FreeBSD Journal + is now free to everyone, ASLR is available in -CURRENT and KPTI + can be controlled per-process. The run up to 11.3-RELEASE + has begun, and a team is applying syzkaller guided fuzzing + to the kernel, plus so much more. Catch up on many new and + ongoing efforts throughout the project, and find where you can + pitch in.

+
+ + + team + + &os; Team Reports + +

Entries from the various official and semi-official teams, + as found in the Administration + Page.

+
+ + + proj + + Projects + +

Projects that span multiple categories, from the kernel and userspace + to the Ports Collection or external projects.

+
+ + + kern + + Kernel + +

Updates to kernel subsystems/features, driver support, + filesystems, and more.

+
+ + + arch + + Architectures + +

Updating platform-specific features and bringing in support + for new hardware platforms.

. +
+ + + bin + + Userland Programs + +

Changes affecting the base system and programs in it.

+
+ + + ports + + Ports + +

Changes affecting the Ports Collection, whether sweeping + changes that touch most of the tree, or individual ports + themselves.

+
+ + + doc + + Documentation + +

Noteworthy changes in the documentation tree or new external + books/documents.

+
+ + + misc + + Miscellaneous + +

Objects that defy categorization.

+
+ + + third + + Third-Party Projects + +

Many projects build upon &os; or incorporate components of + &os; into their project. As these projects may be of interest + to the broader &os; community, we sometimes include brief + updates submitted by these projects in our quarterly report. + The &os; project makes no representation as to the accuracy or + veracity of any claims in these submissions.

+
+ + + FreeBSD Release Engineering Team + + + + FreeBSD Release Engineering Team + re@FreeBSD.org + + + + + FreeBSD 11.3-RELEASE schedule + FreeBSD development snapshots + + + +

The FreeBSD Release Engineering Team is responsible for + setting and + publishing release schedules for official project releases + of + FreeBSD, announcing code freezes and maintaining the + respective + branches, among other things.

+ +

During the first quarter of 2019, the FreeBSD Release + Engineering team + published the initial schedule for the upcoming the + 11.3-RELEASE.

+ +

FreeBSD 11.3-RELEASE will be the fourth release from the + stable/11 + branch, building on the stability and reliability of + 11.2-RELEASE. + FreeBSD 11.3-RELEASE is currently targed for release in + early July, 2019.

+ +

Additionally throughout the quarter, several development + snapshots builds + were released for the head, stable/12, + and stable/11 branches.

+ +

Much of this work was sponsored by the FreeBSD Foundation.

+ + + +
+ + + Ports Collection + + + + René Ladan + portmgr-secretary@FreeBSD.org + + + FreeBSD Ports Management Team + portmgr@FreeBSD.org + + + + + About FreeBSD Ports + Contributing to Ports + FreeBSD Ports Monitoring + Ports Management Team">Ports Management Team + + + +

As always, below is a summary of what happened in the + Ports Tree during the + last quarter.

+ +

During 2019q1, the number of ports dropped slightly to + just over 32,500. At + the end of the quarter, we had 2092 open port PRs. The + last quarter saw 8205 + commits from 167 committers. So more PRs were closed and + more commits were + made than in 2018q4.

+ +

During the last quarter, we welcomed Kai Knoblich (kai@) + and said goodbye to + Matthew Rezny (rezny@).

+ +

On the infrastructure side, two new USES were introduced + (azurepy and sdl) and + USES=gecko was removed. The default versions of Lazarus + and LLVM were bumped + to 2.0.0 and 8.0 respectively. Some big port frameworks + that were end-of-life + were removed: PHP 5.6, Postgresql 9.3, Qt4, WebKit-Gtk and + XPI. Firefox was + updated to 66.0.2, Firefox-ESR to 60.6.1, and Chromium was + updated to + 72.0.3626.121.

+ +

During the last quarter, antoine@ ran 30 exp-runs for + package updates, moving + from GNU ld to LLVM ld, and switching clang to DWARF4.

+ + + +
+ + + FreeBSD Core Team + + + + FreeBSD Core Team + core@FreeBSD.org + + + + +

The FreeBSD Core Team is the governing body of FreeBSD.

+ +

Core initiated a Release Engineering Charter + Modernization working + group. The purpose of the working group is to present (to + Core) a + modernized version of the Release Engineering + Charter and a first + version of a new Release Engineering Team Operations + Plan. The + group hopes to complete its goals and dissolve by + 2019-06-30.

+ +

The Core Team invites all members of the FreeBSD community + to + complete the 2019 FreeBSD Community Survey.

+ +

https://www.research.net/r/freebsd2019

+ +

The purpose of the survey is to collect quantitative data + from the + public in order to help guide the project's priorities and + efforts. + It will remain open for 17 days and close at midnight May + 13 UTC + (Monday 5pm PDT). + (Editor's note: Survey has finished)

+ +

Core voted to approve source commit bits for Johannes + Lundberg + (johalun@) and Mitchell Horne (mhorne@) and associate + membership + for Philip Jocks. Core also voted to revoke Michael + Dexter's + documentation bit.

+ +

After a long lapse of not closing idle source commit bits, + core has + taken in the commit bit for these developers. We thank + each for + contributing to the project as a source committer.

+ +
    +
  • Alfred Perlstein (alfred@)
  • + +
  • Eric Badger (badger@)
  • + +
  • Daniel Eischen (deischen@)
  • + +
  • Ermal Luçi (eri@)
  • + +
  • Tony Finch (fanf@)
  • + +
  • Justin T. Gibbs (gibbs@)
  • + +
  • Imre Vadász (ivadasz@)
  • + +
  • Julio Merino (jmmv@)
  • + +
  • John W. De Boskey (jwd@)
  • + +
  • Kai Wang (kaiw@)
  • + +
  • Luigi Rizzo (luigi@)
  • + +
  • Neel Natu (neel@)
  • + +
  • Craig Rodrigues (rodrigc@)
  • + +
  • Stanislav Sedov (stas@)
  • + +
  • Thomas Quinot (thomas@)
  • + +
  • Andrew Thompson (thompsa@)
  • + +
  • Pyun YongHyeon (yongari@)
  • + +
  • Zbigniew Bodek (zbb@)
  • +
+ +

+ + + +
+ + + FreeBSD Foundation + + + + 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. + Funding comes from individual and corporate donations and + is used to fund + and manage software development projects, conferences and + developer summits, + and provide travel grants to FreeBSD contributors.

+ +

The Foundation purchases and supports hardware to improve + and maintain + FreeBSD infrastructure and provides resources to improve + security, + quality assurance, and release engineering efforts; + publishes + marketing material to promote, educate, and advocate for + the FreeBSD Project; + facilitates collaboration between commercial vendors and + FreeBSD developers; + and finally, represents the FreeBSD Project in executing + contracts, + license agreements, and other legal arrangements that + require + a recognized legal entity.

+ +

Here are some highlights of what we did to help FreeBSD + last quarter:

+ +

We kicked off the year with an all-day board meeting in + Berkeley, + where FreeBSD began, to put together high-level plans for + 2019. + This included prioritizing technologies and features we + should support, + long-term planning for the next 2-5 years, and + philosophical discussions + on our purpose and goals.

+ +

Partnerships and Commercial User Support

+ +

We began the year by meeting with a few commercial users, + to help them + navigate working with the Project, and understanding how + they are using + FreeBSD. We're also in the process of setting up meetings + for Q2 and + throughout the rest of 2019. Because we're a 501(c)(3) + non-profit, we + don't directly support commercial users. + However, these meetings allow us to focus on facilitating + collaboration + with the community.

+ +

Fundraising Efforts

+ +

Our work is 100% funded by your donations. We kicked off + the year with many + individual and corporate donations, including donations + and commitments from + NetApp, Netflix, Intel, Tarsnap, Beckhoff Automation, + E-Card, VMware, and + Stormshield. We are working hard to get more commercial + users to give back + to help us continue our work supporting FreeBSD. + Please consider making a + donation + to help us continue and increase our support for FreeBSD + at: + www.FreeBSDfoundation.org/donate/.

+ +

We also have the Partnership Program, to provide more + benefits for our + larger commercial donors. Find out more information at + + https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/ + and share with your companies!

+ +

OS Improvements

+ +

The Foundation improves the FreeBSD operating system by + employing our + technical staff to maintain and improve critical kernel + subsystems, + add features and functionality, and fix problems. This + also includes funding + separate project grants like + the arm64 port, porting the blacklistd access control + daemon, and the + integration of VIMAGE support, + to make sure that FreeBSD remains a viable solution for + research, education, + computing, products and more.

+ +

Over the quarter there were 241 commits from nine + Foundation-sponsored staff + members and grant recipients.

+ +

We kicked off or continued the following projects last + quarter:

+ +
    +
  • FUSE file system kernel support (update and bug fixes)
  • + +
  • Linuxulator testing and diagnostics improvements
  • + +
  • SDIO and WiFi infrastructure improvements
  • + +
  • x86-64 scalability and performance improvements
  • + +
  • OpenZFS Online RAID-Z Expansion
  • +
+ +

+ Having software developers on staff has allowed us to jump + in and + work directly on projects to improve FreeBSD like:

+ +
    +
  • amd64 and i386 pmap improvements and bugfixes
  • + +
  • address userland threading library issues
  • + +
  • improve i386 support to keep the platform viable
  • + +
  • improve FreeBSD on RISC-V
  • + +
  • application of the Capsicum sandboxing framework
  • + +
  • build system improvements and bug fixes
  • + +
  • respond to reports of security issues
  • + +
  • implement vulnerability mitigations
  • + +
  • tool chain updates and improvements
  • + +
  • adding kernel code coverage support for the + Syzkaller + coverage-guided system call + fuzzer
  • + +
  • improved Syzkaller support for FreeBSD
  • + +
  • improve the usability of freebsd-update
  • + +
  • improve network stack stability and address race + conditions
  • + +
  • ensure FreeBSD provides userland interfaces required by + contemporary + applications
  • + +
  • implement support for machine-dependent optimized + subroutines
  • + +
  • update and correct documentation and manpages
  • + +
  • DTrace bug fixes
  • + +
  • update the FreeBSD Valgrind port and try to upstream the + changes
  • +
+ +

+ Continuous Integration and Quality Assurance

+ +

The Foundation provides a full-time staff member who is + working on improving + our automated testing, continuous integration, and overall + quality assurance + efforts.

+ +

During the first quarter of 2019, Foundation staff + continued improving the + project's CI infrastructure, working with contributors to + fix failing build + and test cases, and working with other teams in the + project for their + testing needs. In this quarter, we started publishing the + CI + weekly report + on the freebsd-testing@ mailing list.

+ +

See the FreeBSD CI section of this report for more + information.

+ +

Release Engineering

+ +

The Foundation provides a full-time staff member to + oversee the + release engineering efforts. This has provided timely and + reliable releases + over the last five years.

+ +

During the first quarter of 2019, the FreeBSD Release + Engineering team + continued providing weekly development snapshots for + 13-CURRENT, 12-STABLE, + and 11-STABLE.

+ +

In addition, the Release Engineering team published the + schedule for the + upcoming 11.3-RELEASE cycle, the fourth release from the + stable/11 branch, + which builds on the stability and reliability of + 11.2-RELEASE.

+ +

The upcoming + 11.3-RELEASE + schedule + can be found at: + https://www.freebsd.org/releases/11.3R/schedule.html

+ +

FreeBSD 11.3 is currently targeted for final release in + early July 2019.

+ +

Please see the FreeBSD Release Engineering Team section of + this quarterly + status report for additional details surrounding the above + mentioned work.

+ +

Supporting FreeBSD Infrastructure

+ +

The Foundation provides hardware and support to improve + FreeBSD infrastructure. Last quarter, we continued + supporting FreeBSD hardware located + around the world.

+ +

FreeBSD Advocacy and Education

+ +

A large part of our efforts are dedicated to advocating + for the Project. + This includes promoting work being done by others with + FreeBSD; producing + advocacy literature to teach people about FreeBSD and help + make the path to + starting using FreeBSD or contributing to the Project + easier; and attending + and getting other FreeBSD contributors to volunteer to run + FreeBSD events, + staff FreeBSD tables, and give FreeBSD presentations.

+ +

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, + to work together on projects, and to facilitate + 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.

+ +

Check out some of the advocacy and education work we did + last quarter:

+ +
    +
  • Attended FOSDEM 2019 where we: staffed the FreeBSD Stand, + sponsored the + co-located FreeBSD Developer Summit, and gave the 25 Years + of FreeBSD + presentation in the BSD Dev room.
  • +
+ +

+ +
    +
  • Sponsored and presented at SANOG33 in Thimphu, Bhutan
  • +
+ +

+ +
    +
  • Represented FreeBSD at APRICOT 2019 in Yuseong-gu, Daejeon + South Korea
  • +
+ +

+ +
    +
  • Sponsored the USENIX FAST conference in Boston, MA as an + Industry Partner
  • +
+ +

+ +
    +
  • Ran our first ever FreeBSD track at + SCALE + 17x, which included an + all-day + Getting + Started with FreeBSD + workshop. We were thrilled with the turnout of almost 30 + participants and + received a lot of positive feedback. Thanks to Roller + Angel who taught the + class with the help of Deb Goodkin and Gordon Tetlow. We + also promoted + FreeBSD at the FreeBSD table in the Expo Hall.
  • +
+ +

+ +
    +
  • Sponsored, presented, and exhibited at FOSSASIA in + Singapore
  • +
+ +

+ +
    +
  • Sponsored AsiaBSDCon 2019
  • +
+ +

+ +
    +
  • Committed to sponsoring Rootconf, BSDCan, and EuroBSDcon
  • +
+ +

+ +
    +
  • Created registration systems for the Aberdeen Hackathon + and the upcoming + 2019 Vienna FreeBSD Security Hackathon
  • +
+ +

+ +
    +
  • Provided FreeBSD advocacy material
  • +
+ +

+ +
    +
  • Provided 3 travel grants to FreeBSD contributors to attend + many + of the above events.
  • +
+ +

+ We continued producing FreeBSD advocacy material to help + people promote + FreeBSD around the world.

+ +

Read more about our conference adventures in the + conference recaps and trip + reports in our + monthly + newsletters.

+ +

We help educate the world about FreeBSD by publishing the + professionally produced FreeBSD Journal. We're excited to + announce that with + the release of the January/February 2019 issue, the + FreeBSD Journal is now a + free publication. Find out more and access the latest + issues at + www.FreeBSDfoundation.org/journal/.

+ +

You can find out more about events we attended and + upcoming events at + www.FreeBSDfoundation.org/news-and-events/.

+ +

We also engaged with a new website developer to help us + improve our website + to make it easier for community members to find + information more easily and + to make the site more efficient.

+ +

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.

+ +

Go to www.FreeBSDfoundation.org + to find out + how we support FreeBSD and how we can help you!

+ + + +
+ + + Continuous Integration + + + + Jenkins Admin + jenkins-admin@FreeBSD.org + + + Li-Wen Hsu + lwhsu@FreeBSD.org + + + + + FreeBSD Jenkins Instance + FreeBSD CI artifact archive + FreeBSD Jenkins wiki + freebsd-testing Mailing List + freebsd-ci Repository + Tickets related to freebsd-testing@ + Hosted CI wiki + FreeBSD CI weekly report + + + +

The FreeBSD CI team maintains continuous integration + system and + related tasks for the FreeBSD project. The CI system + regularly + checks the changes committed to the project's Subversion + repository + can be successfully built, and performs various tests and + analysis + of the results. The results from build jobs are archived + in an + artifact server, for the further testing and debugging + needs. The + CI team members examine the failing builds and unstable + tests, and + work with the experts in that area to fix the code or + adjust test + infrastructure.

+ +

Starting from this quarter, we started to publish CI + weekly report at + freebsd-testing@ + mailing list. The archive is available at + https://hackfoldr.org/freebsd-ci-report/

+ +

We also worked on extending test executing environment + to improve the code coverage, temporarily disabling flakey + test cases, + and opening tickets to work with domain experts. The + details are + of these efforts are available in the weekly CI reports.

+ +

We published the + draft + FCP for CI policy + and are ready to accept comments.

+ +

Please see freebsd-testing@ related tickets for more + information.

+ +

Work in progress:

+ +
    +
  • Fixing the failing test cases and builds
  • + +
  • Adding drm ports building test against -CURRENT
  • + +
  • Implementing automatic tests on bare metal hardware
  • + +
  • Implementing the embedded testbed
  • + +
  • Planning for running ztest and network stack tests
  • + +
  • Help more 3rd software get CI on FreeBSD through a hosted + CI solution
  • +
+ +

+ + + +
+ + + Security-Related changes + + + + Konstantin Belousov + kib@freebsd.org + + + + +

ASLR

+ +

The ASLR (Address Space Layout Randomization) patch from + review + D5603 was + committed into svn. While debate continues about the + current and + forward-looking value ASLR provides, having an + implementation in + the FreeBSD source tree makes it easily available to those + who wish + to use it. This also moves the conversation past the + relative + merits to more comprehensive security controls.

+ +

KPTI per-process control

+ +

The KPTI (Kernel Page Table Isolation) implementation was + structured + so that most selections of page isolation mode were local + to the + current address space. In other words, the global control + variable + pti was almost unused in the code paths, instead the + user/kernel + %cr3 values were directly loaded into registers or + compared to see + if the user page table was trimmed. Some missed bits of + code were + provided by Isilon, and then bugs were fixed and last + places of + direct use of pti were removed.

+ +

Now when the system starts in the pti-enabled mode, + proccontrol(1) can + be used by root to selectively disable KPTI mode for + children of a + process. The motivation is that if you trust the program + that you + run, you can get the speed of non-pti syscalls back, but + still run + your normal user session in PTI mode. E.g., firefox would + be properly + isolated.

+ +

Feature-control bits

+ +

Every FreeBSD executable now contains a bit mask intended + for + enabling/disabling security-related features which makes + sense for the + binary. This mask is part of the executable segments + loaded on image + activation, and thus is part of any reasonable way to + authenticate the + binary content.

+ +

For instance, the ASLR compatibility is de-facto the + property of the + image and not of the process executing the image. The + first (zero) + bit in the mask controls ASLR opt-out. Other OSes (e.g. + Solaris) used + an OS-specific dynamic flag, which has the same runtime + properties + but leaves less bits to consume in the feature-control + mask.

+ +

The feature-control mask is read both by kernel and by + rtld during + image activation. It is expected that more features will + be added + to FreeBSD and the mask can be used for enabling/disabling + those + features..

+ +

It is expected that a tool to manipulate the mask will be + provided + shortly, see review + D19290.

+ +

+ + + + + The FreeBSD Foundation + + +
+ + + AXP803 PMIC driver update + + + + Ganbold Tsagaankhuu + ganbold@FreeBSD.org + + + + +

The AXP803 is a highly integrated PMIC that targets + Li-battery + (Li-ion or Li-polymer) applications. It provides flexible + power + management solution for processors such as the Allwinner + A64 SoC. + This SoC is used by Pinebook.

+ +

The following updates were performed on the AXP803 driver:

+ +
    +
  • Enabled necessary bits when activating interrupts. This + allows + reading some events from the interrupt status registers. + These + events are reported to devd via system "PMU" and subsystem + "Battery", "AC" and "USB" such as plugged/unplugged, + battery + absent, charged and charging.
  • + +
  • Added sensors support for AXP803/AXP813. Sensor values + such as + battery charging, charge state, voltage, charging current, + discharging current, battery capacity can be obtained via + sysctl.
  • + +
  • Added sysctl for setting battery charging current. The + charging + current can be set using steps from 0 to 13. These steps + correspond to 200mA to 2800mA, with a granularity of + 200mA/step.
  • +
+ +

+ + *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***