OpenBSD src changes summary for 2016-07-09 ==========================================
distrib/notes sbin/route share/man share/misc sys/arch/armv7/conf sys/arch/armv7/imx sys/arch/armv7/omap sys/dev/mii sys/dev/ofw sys/uvm usr.bin/mandoc usr.sbin/vmd == distrib =========================================================== 01/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib notes ~ armv7/prep > Mention the EFI and DTB requirement. List U-Boot 2016.07 as 2016.05 > needs a patch to work with efiboot on non imx platforms that is > included in ports/packages but might not be present otherwise. > While U-Boot 2016.07 final is not released yet the > "efi_loader: Don't allocate from memory holes" patch is included > in rc1/rc2/rc3 and should make the final release. (jsg@) == sbin ============================================================== 02/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin route ~ route.c > only print one error, not multiple misleading messages (tedu@) == share ============================================================= 03/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/share man ~ man4/man4.armv7/imx.4 > ehci no longer attaches to imx (jsg@) misc ~ inter.phone > spelling; from Ilya dot Kaliman at gmail dot com (schwarze@) == sys =============================================================== 04/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys arch/armv7/conf ~ GENERIC ~ RAMDISK > Dynamically attach i.MX6 ehci(4) using the FDT. > ok jsg@ (kettenis@) arch/armv7/imx ~ files.imx ~ imx.c ~ imxehci.c > Dynamically attach i.MX6 ehci(4) using the FDT. > ok jsg@ (kettenis@) ~ if_fec.c > Perform PHY-specific initialization based on the PHY ID instead of the > board ID for the AR8031/AR8035. > ok jsg@ (kettenis@) ~ imx.c ~ imx6.c > Simplify the i.MX6 platform code. The list of board devices is now > (essentially) the same for all boards, so we can use a single list and > match based on the compatible property of the root node in the device tree. > ok jsg@ (kettenis@) arch/armv7/omap ~ if_cpsw.c > Use mac address and phy id from the fdt. Store settings for a second > port as well, though we still only handle a single port for now. > ok kettenis@ (jsg@) dev/mii ~ atphy.c > Initialize the mii_oui field such that fec(4) can look at it. > ok jsg@ (kettenis@) dev/ofw ~ fdt.c ~ fdt.h ~ openfirm.h > Add interfaces to look up a device tree node by phandle. > ok patrick@, jsg@, visa@ (kettenis@) uvm ~ uvm_amap.c > Fix bugs introduced with the amap rework > - The number of slots must be initialized in the chunk of a small amap, > otherwise unmapping() part of a mmap()'d range would delay freeing > of vm_anons for small amaps > - If the first chunk of a bucket is freed, check if the next chunk in > the list has to become the new first chunk > - Use a separate loop for each type of traversal (small amap, by bucket > by list) in amap_wiperange(). This makes the code easier to follow and > also fixes a bug where too many chunks were wiped out when traversing > by list > However, the last two bugs should happen only when turning a previously > private mapping into a shared one, then forking, and then having > both processes unmap a part of the mapping. > snap and ports build tested by krw@, review by kettenis@ (stefan@) == usr.bin =========================================================== 05/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin mandoc ~ mandocdb.c ~ mansearch.c > getopt(3) is declared in <unistd.h>, and <getopt.h> is not needed; > from Joerg Sonnenberger via Thomas Klausner, NetBSD. (schwarze@) ~ cgi.c > Do not treat PATH_INFO as a complete path if it doesn't contain > a manpath. For example, this makes http://man.openbsd.org/mandoc > work as expected. > Bug reported by tb@, reminded by Svyatoslav Mishyn. (schwarze@) == usr.sbin ========================================================== 06/06 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin vmd ~ virtio.c ~ virtio.h ~ vmd.h ~ vmm.c > Prepare vionet to be handled asynchronously to the VCPU thread > This splits the handling of received data into a separate function > that can later be called in parallel to the VCPU thread instead of > handling received packets on VCPU exits only. > It also makes virtq accesses in the rx path safe to run in parallel > to the VCPU thread: the last index into the 'avail' ring the driver > has notified to the host is kept track of. It also makes sure that > the host only writes back to the 'avail' ring instead of modifying > the whole receive virtq. > While there, describe what virtio_vq_info and virtio_io_cfg are used > for, as suggested by mlarkin@ > ok mlarkin@ (stefan@) =============================================================================== _______________________________________________ odc mailing list [email protected] http://www.squish.net/mailman/listinfo/odc
