General editing, sentence clarity, and addition of <tt> tags every other
word or so.
This commit is contained in:
parent
a313a6c362
commit
ef6a3033c9
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=48603
1 changed files with 112 additions and 114 deletions
|
@ -124,14 +124,6 @@
|
|||
Translations</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
<name>
|
||||
<given>Warren</given>
|
||||
<common>Block</common>
|
||||
</name>
|
||||
<email>wblock@FreeBSD.org</email>
|
||||
</person>
|
||||
|
||||
<person>
|
||||
<name>
|
||||
<given>Federico</given>
|
||||
|
@ -155,6 +147,14 @@
|
|||
</name>
|
||||
<email>raycherng@gmail.com</email>
|
||||
</person>
|
||||
|
||||
<person>
|
||||
<name>
|
||||
<given>Warren</given>
|
||||
<common>Block</common>
|
||||
</name>
|
||||
<email>wblock@FreeBSD.org</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
<links>
|
||||
|
@ -196,7 +196,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='kern'>
|
||||
<title>NFS server</title>
|
||||
<title>NFS Server</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -211,7 +211,7 @@
|
|||
<links></links>
|
||||
|
||||
<body>
|
||||
<p>A new option "-manage-gids" was added to the nfsuserd
|
||||
<p>A new <tt>-manage-gids</tt> option was added to the <tt>nfsuserd</tt>
|
||||
daemon. This option tells the NFS server to use the list of
|
||||
groups for a uid on the server and not the list of groups in
|
||||
the NFS RPC request. Use of this option avoids the 16 group
|
||||
|
@ -237,7 +237,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='arch'>
|
||||
<title>powerpcspe target</title>
|
||||
<title><tt>powerpcspe</tt> Target</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -270,16 +270,16 @@
|
|||
|
||||
<help>
|
||||
<task>
|
||||
<p>Potentially optimizing setjmp/longjmp to not use SPE unless
|
||||
it's already been enabled. This would save the kernel
|
||||
switch for processes that don't otherwise use the SPE. This
|
||||
<p>Potentially optimizing <tt>setjmp</tt>/<tt>longjmp</tt> to not use SPE unless
|
||||
it has already been enabled. This would save the kernel
|
||||
switch for processes that do not otherwise use the SPE. This
|
||||
is a low priority task which may not be completed.</p>
|
||||
</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
<project cat="proj">
|
||||
<title>The Graphics stack on FreeBSD</title>
|
||||
<title>The Graphics Stack on FreeBSD</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -318,7 +318,7 @@
|
|||
"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 libdevq. Six students
|
||||
a kernel task, one to redesign <tt>libdevq</tt>. Six students
|
||||
submitted a proposal for those two ideas, that was unexpected!
|
||||
We now need to decide which one we want to mentor and the
|
||||
choice is difficult.</p>
|
||||
|
@ -427,7 +427,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='docs'>
|
||||
<title>new "FreeBSD Mastery" books</title>
|
||||
<title>New "FreeBSD Mastery" Books</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -448,7 +448,7 @@
|
|||
is now available everywhere, in print and ebook.</p>
|
||||
|
||||
<p>Lucas and Allan Jude have also finished writing "FreeBSD
|
||||
Mastery: Advanced ZFS." It's in copyedit now, and should be
|
||||
Mastery: Advanced ZFS." It is in copyedit now, and should be
|
||||
available before May 2016. Check
|
||||
<a href="zfsbook.com">zfsbook.com</a> for details.</p>
|
||||
|
||||
|
@ -505,7 +505,7 @@
|
|||
and current Cavium firmware. Backward compatibility is
|
||||
maintained.</li>
|
||||
|
||||
<li>Moved to using pci_host_generic.c as a main driver for the
|
||||
<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>
|
||||
|
||||
|
@ -527,13 +527,13 @@
|
|||
</ul>
|
||||
|
||||
<p>The driver supports all available Ethernet connections (1,
|
||||
10, 30 Gbps) and system can can saturate 10 Gbps link (on Tx)
|
||||
10, 30 Gbps) and system can saturate 10 Gbps link (on Tx)
|
||||
using 4 CPU cores.</p>
|
||||
|
||||
<ul>
|
||||
<li>Significantly improved overall I/O performance:</li>
|
||||
<ul>
|
||||
<li>Complete rework of copyin/copyout and bzero
|
||||
<li>Complete rework of <tt>copyin</tt>/<tt>copyout</tt> and <tt>bzero</tt>
|
||||
functionalities</li>
|
||||
</ul>
|
||||
|
||||
|
@ -544,7 +544,7 @@
|
|||
</ul>
|
||||
</ul>
|
||||
|
||||
<p>This work is integrated to the FreeBSD HEAD on on-going
|
||||
<p>This work is integrated to the FreeBSD HEAD on an on-going
|
||||
basis.</p>
|
||||
</body>
|
||||
|
||||
|
@ -602,19 +602,19 @@
|
|||
</task>
|
||||
|
||||
<task>
|
||||
<p>Add support for $_siginfo.</p>
|
||||
<p>Add support for <tt>$_siginfo</tt>.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>Add support for ELF auxv data via 'info auxv'.</p>
|
||||
<p>Add support for ELF auxv data via <tt>info auxv</tt>.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>Implement 'info os' commands.</p>
|
||||
<p>Implement <tt>info os</tt> commands.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>Implement gdbserver for freebsd.</p>
|
||||
<p>Implement <tt>gdbserver</tt> for FreeBSD.</p>
|
||||
</task>
|
||||
</help>
|
||||
</project>
|
||||
|
@ -641,14 +641,14 @@
|
|||
hotplug is present at the URL above. Much of the new code
|
||||
lives in the PCI-PCI bridge driver to handle hotplug events
|
||||
and manage the PCI-express slot registers. Additional changes
|
||||
in the branch include adding new 'rescan' and 'delete'
|
||||
in the branch include adding new <tt>rescan</tt> and <tt>delete</tt>
|
||||
commands to <tt>devctl(8)</tt> as well as support for
|
||||
rescanning PCI busses.</p>
|
||||
|
||||
<p>The current implementation has been tested on systems with
|
||||
ExpressCard but could use additional testing, especially on
|
||||
systems with other PCI-express HotPlug features such as
|
||||
mechanical latches, attention buttons, indicators, etc.</p>
|
||||
mechanical latches, attention buttons, indicators, and so on.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
|
@ -686,11 +686,11 @@
|
|||
that the experience of KDE and Qt on FreeBSD is as good as
|
||||
possible.</p>
|
||||
|
||||
<p>While the list of updates is shorter compared to the previous
|
||||
<p>While the list of updates is shorter than that for the previous
|
||||
quarter, the team remained busy and work on KDE Frameworks 5
|
||||
and Plasma 5 continues.</p>
|
||||
|
||||
<p>This quarter, Tobias Berner, who has been driving our KDE
|
||||
<p>Tobias Berner, who has been driving our KDE
|
||||
Frameworks 5 and Plasma 5 efforts from the beginning, received
|
||||
a KDE commit bit, and has been putting it to good use by
|
||||
upstreaming FreeBSD across several KDE repositories. Another
|
||||
|
@ -723,17 +723,17 @@
|
|||
landed to the ports tree</a>.</li>
|
||||
</ul>
|
||||
|
||||
<p>In our experimental area51 repository, work on Qt 5.6.0 is
|
||||
underway in our experimental repositories. Additionally, at
|
||||
the time of writing it also contains KDE Frameworks 5.20.0,
|
||||
Plasma 5.6.1 and KDE Applications 16.03.80.</p>
|
||||
<p>Work on Qt 5.6.0 is
|
||||
under way in our experimental repositories. At
|
||||
the time of writing, it also contains KDE Frameworks 5.20.0,
|
||||
Plasma 5.6.1, and KDE Applications 16.03.80.</p>
|
||||
|
||||
<p>Users interested in testing those ports are encouraged to
|
||||
follow the instructions in
|
||||
<a href="https://freebsd.kde.org/area51.php">our website</a>
|
||||
and report their results to our mailing list. Qt5 5.6.0 is in
|
||||
our "qt-5.6" branch, and Plasma 5 and the rest is in the
|
||||
"plasma5" branch.</p>
|
||||
our <tt>qt-5.6</tt> branch, and Plasma 5 and the rest is in the
|
||||
<tt>plasma5</tt> branch.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
|
@ -750,7 +750,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='proj'>
|
||||
<title>Process-Shared locks for libthr</title>
|
||||
<title>Process-Shared Locks for <tt>libthr</tt></title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -870,7 +870,7 @@
|
|||
<li>clang/llvm buildbbot now hosted in the FreeBSD cluster
|
||||
at NYI (sbruno, emaste)</li>
|
||||
|
||||
<li>resolved UK mirror outtage with Bytemark (gavin,
|
||||
<li>resolved UK mirror outage with Bytemark (gavin,
|
||||
peter)</li>
|
||||
</ul></p>
|
||||
</body>
|
||||
|
@ -955,20 +955,20 @@
|
|||
Some highlights include:</p>
|
||||
|
||||
<ul>
|
||||
<li><em>WITH_FAST_DEPEND</em> was made default in r296668 and
|
||||
<li><tt>WITH_FAST_DEPEND</tt> was made default in r296668 and
|
||||
later made the only option in r297434. The new depend code
|
||||
avoids a 'make depend' tree walk and generates .depend files
|
||||
avoids a <tt>make depend</tt> tree walk and generates <tt>.depend</tt> files
|
||||
during build as a side-effect of compiling. This is using
|
||||
the -MF flags of the compiler. This speeds up the build by
|
||||
the <tt>-MF</tt> flags of the compiler. This speeds up the build by
|
||||
15-35%.</li>
|
||||
|
||||
<li><a href="http://bugs.freebsd.org/196193">PR 196193</a>:
|
||||
<em>WITHOUT_CROSS_COMPILER</em> was fixed to properly use
|
||||
<em>--sysroot</em> which allows the option to work in more
|
||||
<tt>WITHOUT_CROSS_COMPILER</tt> was fixed to properly use
|
||||
<tt>--sysroot</tt> which allows the option to work in more
|
||||
cases. It is still unsafe when major compiler upgrades
|
||||
occur. Further work is planned to improve that still.</li>
|
||||
|
||||
<li><em>WITHOUT_TOOLCHAIN</em> now properly builds.</li>
|
||||
<li><tt>WITHOUT_TOOLCHAIN</tt> now properly builds.</li>
|
||||
</ul>
|
||||
</body>
|
||||
|
||||
|
@ -983,22 +983,22 @@
|
|||
</task>
|
||||
|
||||
<task>
|
||||
<p>Skipping the 'make obj' tree walk.</p>
|
||||
<p>Skipping the <tt>make obj</tt> tree walk.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>Enabling <em>WITH_META_MODE</em> in buildworld to provide a
|
||||
reliable incremental build using filemon(4) and bmake's
|
||||
.MAKE.MODE=meta. This should not be confused with
|
||||
<em>WITH_DIRDEPS_BUILD</em> which previously was named
|
||||
<em>WITH_META_MODE</em> and is a drastically different build
|
||||
<p>Enabling <tt>WITH_META_MODE</tt> in buildworld to provide a
|
||||
reliable incremental build using <tt>filemon(4)</tt> and <tt>bmake</tt>'s
|
||||
<tt>.MAKE.MODE=meta</tt>. This should not be confused with
|
||||
<tt>WITH_DIRDEPS_BUILD</tt> which previously was named
|
||||
<tt>WITH_META_MODE</tt> and is a drastically different build
|
||||
system presented at BSDCan 2014 by Simon Gerraty.</p>
|
||||
</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
<project cat='kern'>
|
||||
<title>Filemon performance/stability improvements</title>
|
||||
<title>Filemon Performance/Stability Improvements</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -1022,25 +1022,25 @@
|
|||
|
||||
<body>
|
||||
<p>Filemon is a kernel module for tracing which files a command
|
||||
creates, reads, writes or executes. It allows tracking build
|
||||
dependencies in combination with bmake's meta mode. Bmake
|
||||
will store filemon's output in a .meta file along with the
|
||||
build command and later use this to check if any of the files
|
||||
references are missing or modified, or if the build command
|
||||
changes, to trigger a rebuild of the target. It provides the
|
||||
same functionality as compiler -MF flags but for everything.
|
||||
It will be critical for buildworld's <em>WITH_META_MODE</em>
|
||||
creates, reads, writes, or executes. It allows tracking build
|
||||
dependencies in combination with <tt>bmake</tt>'s meta mode. <tt>bmake</tt>
|
||||
stores filemon's output in a <tt>.meta</tt> file along with the
|
||||
build command and later uses this to trigger a rebuild of the target if any of the files
|
||||
referenced are missing or modified or if the build command
|
||||
changes. It provides the
|
||||
same functionality as compiler <tt>-MF</tt> flags but for everything.
|
||||
It will be critical for buildworld's <tt>WITH_META_MODE</tt>
|
||||
(which is the normal buildworld but just using filemon) to
|
||||
provide a reliable incremental build without even the need of
|
||||
.depend files or compiler -MF flags. This will allow
|
||||
<em>-DNO_CLEAN</em> to work all of the time.</p>
|
||||
<tt>.depend</tt> files or compiler <tt>-MF</tt> flags. This allows
|
||||
<tt>-DNO_CLEAN</tt> to work all of the time.</p>
|
||||
|
||||
<p>Over this quarter filemon on head was improved for stability
|
||||
and performance. It no longer causes every syscall it hooks
|
||||
<p>Filemon on -HEAD was improved for stability
|
||||
and performance over this quarter. It no longer causes every syscall it hooks
|
||||
into to loop on processes looking for a matching filemon
|
||||
struct. It now just attaches directly to the struct proc with
|
||||
its own pointer. This improves performance by reducing lock
|
||||
contention during a build using it. Much other work went into
|
||||
contention during a build. Much other work went into
|
||||
improving error handling and other stability issues in the
|
||||
module as well.</p>
|
||||
|
||||
|
@ -1071,7 +1071,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='arch'>
|
||||
<title>AmigaOne X5000 support</title>
|
||||
<title>AmigaOne X5000 Support</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -1098,12 +1098,12 @@
|
|||
peripherals.</p>
|
||||
|
||||
<p>Currently most code is checked in to enable basic support:
|
||||
dTSEC (ethernet), core support (e500mc, e5500). Additionally,
|
||||
as part of this, rman, the kernel resource manager, was
|
||||
enhanced to use uintmax_t for resources. This allows devices
|
||||
dTSEC (ethernet), core support (e500mc, e5500).
|
||||
As part of this, <tt>rman</tt>, the kernel resource manager, was
|
||||
enhanced to use <tt>uintmax_t</tt> for resources. This allows devices
|
||||
to be physically above the 4GB boundary on 32-bit systems.
|
||||
With a statically compiled device tree, it boots to multiuser
|
||||
mode, with nfsroot, and can be used as normal (serial and ssh
|
||||
mode with nfsroot, and can be used as normal (serial and SSH
|
||||
logins once configured).</p>
|
||||
</body>
|
||||
|
||||
|
@ -1113,48 +1113,48 @@
|
|||
|
||||
<help>
|
||||
<task>
|
||||
<p>eSDHC driver. Work has been started on this, hijacking the
|
||||
imx_sdhc.c from Ian Lepore, but there are still bugs:
|
||||
<p>eSDHC driver: Work has been started on this, hijacking the
|
||||
<tt>imx_sdhc.c</tt> from Ian Lepore, but there are still bugs:
|
||||
missing DMA from the iMX driver, and odd timeouts after the
|
||||
system starts up.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>SATA support. There is a WIP driver for the SATA
|
||||
controller, but it's currently very slow, about 11MB/s on a
|
||||
<p>SATA support: There is a WIP driver for the SATA
|
||||
controller, but it is currently very slow, about 11MB/s on a
|
||||
SATA 2 link. It currently relies on a 10ms delay on every
|
||||
SATA transaction, in order for it to be even somewhat
|
||||
SATA transaction for it to be even somewhat
|
||||
stable. Without this delay, the disk scan never works and I
|
||||
haven't yet figured out why.</p>
|
||||
have not yet figured out why.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>Local console (VGA) support. It currently boots with a
|
||||
serial console. vgapci0 is seen if there's a PCIe graphics
|
||||
card, but vt(4) doesn't attach to it yet.</p>
|
||||
<p>Local console (VGA) support: It currently boots with a
|
||||
serial console. vgapci0 is seen if there is a PCIe graphics
|
||||
card, but <tt>vt(4)</tt> does not attach to it yet.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>64-bit support. The CPU on the board is a P5020, a 64-bit
|
||||
<p>64-bit support: The CPU on the board is a P5020, a 64-bit
|
||||
e5500 dual-core SoC. Currently, booke support in FreeBSD is
|
||||
32-bit only.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>SMP. SMP support on Book-E hardware is currently
|
||||
<p>SMP: SMP support on Book-E hardware is currently
|
||||
broken.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>U-boot support. Currently this uses a compiled-in device
|
||||
tree, but it would be preferred for it to use the device
|
||||
<p>U-boot support: Currently this uses a compiled-in device
|
||||
tree, but it would be preferable to use the device
|
||||
tree provided by u-boot, or at least the Linux-compatible
|
||||
device tree.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>More work is needed on the DPAA front (Datapath
|
||||
Acceleration Architecture) to improve the ethernet driver,
|
||||
Acceleration Architecture) to improve the Ethernet driver
|
||||
and utilize the SEC engine for crypto, <tt>random(4)</tt>,
|
||||
and IPSec.</p>
|
||||
</task>
|
||||
|
@ -1167,7 +1167,7 @@
|
|||
<contact>
|
||||
<person>
|
||||
<name>
|
||||
<given>Bj??rn</given>
|
||||
<given>Björn</given>
|
||||
<common>Heidotting</common>
|
||||
</name>
|
||||
<email>bhd@FreeBSD.org</email>
|
||||
|
@ -1199,7 +1199,7 @@
|
|||
documentation (handbook, articles, website, etc.) into the
|
||||
German language.</p>
|
||||
|
||||
<p>Due to the tireless effort of Bj??rn Heidotting, we made huge
|
||||
<p>Due to the tireless effort of Björn Heidotting, we made huge
|
||||
improvements in catching up with the translation of the German
|
||||
handbook. Benedict helped with reviewing the changes using
|
||||
FreeBSD's review system Phabricator, which helped a lot. We
|
||||
|
@ -1220,7 +1220,7 @@
|
|||
ways to translate like the PO/gettext-based system. We are
|
||||
always looking for volunteers who are interested in
|
||||
translating small sections or even entire documents. The
|
||||
process is relatively easy and contributors don't have to know
|
||||
process is relatively easy and contributors do not have to know
|
||||
much to get started. The members of the FreeBSD German
|
||||
Documentation Team are also willing to mentor people who are
|
||||
interested in helping out.</p>
|
||||
|
@ -1234,7 +1234,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='bin'>
|
||||
<title>ELF Tool Chain tools</title>
|
||||
<title>ELF Tool Chain Tools</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -1319,8 +1319,8 @@
|
|||
<body>
|
||||
<p>Mellanox is working on a big infiniband update towards
|
||||
Mellanox OFED v3.2 of the infiniband stack in &os;. The
|
||||
updates include both userland and kernel. If you are using
|
||||
infiniband with &os;, patches are available in the link above
|
||||
updates include both userland and kernel.
|
||||
Infiniband patches for &os; are available in the link above
|
||||
which can be downloaded and applied to a recent &os;-head
|
||||
checkout.</p>
|
||||
</body>
|
||||
|
@ -1440,11 +1440,11 @@
|
|||
distinguished, fixing a potential issue.</li>
|
||||
|
||||
<li>Instead of finding an available IDT vector by hacking,
|
||||
we're changing to use the normal method, i.e.,
|
||||
lapic_ipi_alloc().</li>
|
||||
we are changing to use the normal method, that is,
|
||||
<tt>lapic_ipi_alloc()</tt>.</li>
|
||||
|
||||
<li>We're modularizing the Hyper-V modules: 1) they will be
|
||||
loaded in the loader; 2) we're going to enhance devd(8) to
|
||||
<li>We are modularizing the Hyper-V modules: 1) they will be
|
||||
loaded in the loader; 2) we are going to enhance <tt>devd(8)</tt> to
|
||||
improve the hot plug case.</li>
|
||||
</ul>
|
||||
|
||||
|
@ -1463,11 +1463,11 @@
|
|||
|
||||
<li>Fixed TSC calibration issue (PR 208238 - [Hyper-V] TSC
|
||||
frequency is not correctly detected: "calcru: runtime went
|
||||
backwards") and we won't see the "runtime went backwards"
|
||||
messages anymore!</li>
|
||||
backwards") and we will not see the "runtime went backwards"
|
||||
messages any more!</li>
|
||||
|
||||
<li>Fixed the "very slow terminal" issue of 11-CURRENT by
|
||||
enabling text mode when we're running on hypervisors.</li>
|
||||
enabling text mode when we are running on hypervisors.</li>
|
||||
|
||||
<li>Fixed the "unknown dhcp option value 0xf5" issue in
|
||||
<tt>dhclient(8)</tt> by asking <tt>dhclient(8)</tt> to
|
||||
|
@ -1490,8 +1490,6 @@
|
|||
<p>We published BIS test cases for Hyper-V on github:
|
||||
https://github.com/FreeBSDonHyper-V/Test-BIS and we are going
|
||||
to publish the test cases for Azure soon.</p>
|
||||
|
||||
<p>This project is sponsored by Microsoft.</p>
|
||||
</body>
|
||||
|
||||
<sponsor>
|
||||
|
@ -1528,7 +1526,7 @@
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>As of the end of Q1 the ports tree holds a bit more
|
||||
<p>As of the end of Q1, the ports tree holds a bit more
|
||||
than 25,000 ports, and the PR count is below 1,900. The
|
||||
activity on the ports tree remains steady, with almost 7,000
|
||||
commits performed by around 120 active committers.</p>
|
||||
|
@ -1539,17 +1537,17 @@
|
|||
Indeed, almost 2,400 reports were fixed, which allows us to go
|
||||
below the threshold value of 2,000 open PRs.</p>
|
||||
|
||||
<p>In Q1 3 commit bits were taken in for safekeeping,
|
||||
<p>In Q1, three commit bits were taken in for safekeeping,
|
||||
following an inactivity period of more than 18 months (milki,
|
||||
brian), or on committer's request (mmoll). We had one
|
||||
returning committer (fluffy) who had his commit bit
|
||||
reinstated. Two new developers were granted a ports commit bit
|
||||
(Olivier Cochard-Labbe, Christoph Moench-Tegeder).</p>
|
||||
(Olivier Cochard-Labbe and Christoph Moench-Tegeder).</p>
|
||||
|
||||
<p>On the management side, we had the pleasure to welcome back
|
||||
miwi to the portmgr team.</p>
|
||||
<p>On the management side, we had the pleasure to welcome miwi
|
||||
back to the portmgr team.</p>
|
||||
|
||||
<p>On QA side 39 exp-runs were performed to validate sensitive
|
||||
<p>On the QA side, 39 exp-runs were performed to validate sensitive
|
||||
updates or cleanups. The most noticeable change might be the
|
||||
removal of the now unneeded <tt>${PORTSDIR}</tt> when
|
||||
specifying dependencies in Makefiles (see the
|
||||
|
@ -1651,7 +1649,7 @@
|
|||
by default for wider testing).</p>
|
||||
|
||||
<p>Stack gap, W^X, shared page randomization, KASLR and other
|
||||
techniques are explicitely out of scope of this work.</p>
|
||||
techniques are explicitly out of scope of this work.</p>
|
||||
|
||||
<p>The paxtest results for the run with the previous version 5
|
||||
of the patch applied and aggresively tuned can be seen at the
|
||||
|
@ -1689,7 +1687,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='proj'>
|
||||
<title>RCTL disk IO Limits</title>
|
||||
<title>RCTL Disk IO Limits</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -1759,7 +1757,7 @@
|
|||
</links>
|
||||
|
||||
<body>
|
||||
<p>Qt 5.6 is a great framework to build embedded GUI application
|
||||
<p>Qt 5.6 is a great framework to build embedded GUI applications,
|
||||
so when Qt 5.6 was released it was natural to bring it up on
|
||||
Raspberry Pi. Current Qt support in ports is very
|
||||
Xorg-centric so as a proof of concept I created an
|
||||
|
@ -1781,7 +1779,7 @@
|
|||
</project>
|
||||
|
||||
<project cat='kern'>
|
||||
<title>FDT overlay support in ubldr</title>
|
||||
<title>FDT Overlay Support in UBLDR</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
|
@ -1804,7 +1802,7 @@
|
|||
and the kernel instantiates and attaches drivers according to
|
||||
the information in the blob.</p>
|
||||
|
||||
<p>This approach does not work if hardware is expansible. For
|
||||
<p>This approach does not work when hardware is expandable. For
|
||||
example, the Raspberry Pi and Beaglebone Black have the
|
||||
concept of capes or shields: snap-on PCBs that are connected
|
||||
to IO headers on the main board and provide additional
|
||||
|
@ -1815,8 +1813,8 @@
|
|||
|
||||
<p>The proposed patch add this functionality to ubldr. The user
|
||||
can specify a comma-separated list of overlays as U-Boot or
|
||||
the loader fdt_overlays variable and ubldr will load them from
|
||||
/boot/dtb/ directory and do the overlaying.</p>
|
||||
the loader <tt>fdt_overlays</tt> variable and ubldr will load them from
|
||||
the <tt>/boot/dtb/</tt> directory and do the overlaying.</p>
|
||||
</body>
|
||||
|
||||
<help></help>
|
||||
|
@ -1853,7 +1851,7 @@
|
|||
|
||||
<p>Another feature that the new stack will have is support for
|
||||
sending SD commands from the userland applications using
|
||||
<tt>cam(3)</tt>. This will allow to build device drivers in
|
||||
<tt>cam(3)</tt>. This will allow building device drivers in
|
||||
userland and make debugging much easier.</p>
|
||||
|
||||
<p>The first version of the code was uploaded to Phabricator for
|
||||
|
@ -1861,9 +1859,9 @@
|
|||
bring it to an operational state so it is possible to read and
|
||||
write to the card.</p>
|
||||
|
||||
<p>Support for the imx_sdhci SD Host Controller (used on
|
||||
<p>Support for the <tt>imx_sdhci</tt> SD Host Controller (used on
|
||||
iMX-based boards, for example Wandboard) was added in 2016Q1,
|
||||
along with ti_sdhci, which is used on the BeagleBone Black.
|
||||
along with <tt>ti_sdhci</tt>, which is used on the BeagleBone Black.
|
||||
Modifying other SDHCI-compliant drivers should not be
|
||||
difficult.</p>
|
||||
</body>
|
||||
|
|
Loading…
Reference in a new issue