4630 clean stale references to ddi_iopb_alloc and ddi_iopb_free
4634 undocument scsi_hba_attach() and ddi_dma_lim(9s)

*** 689,701 ****
   * mapped by the DMA handle up to date. It should be used
   * by a driver after the receipt of data from the device to
   * the memory object is done (over the range specified by
   * the other arguments to the ddi_dma_sync(9F) call).
   *
!  * If the only mapping that concerns the driver is one for the
!  * kernel (such as memory allocated by ddi_iopb_alloc(9F)), the
!  * flag DDI_DMA_SYNC_FORKERNEL can be used. This is a hint to the
   * system that if it can synchronize the kernel's view faster
   * that the CPU's view, it can do so, otherwise it acts the
   * same as DDI_DMA_SYNC_FORCPU. DDI_DMA_SYNC_FORKERNEL might
   * speed up the synchronization of kernel mappings in case of
   * non IO-coherent CPU caches.
--- 689,700 ----
   * mapped by the DMA handle up to date. It should be used
   * by a driver after the receipt of data from the device to
   * the memory object is done (over the range specified by
   * the other arguments to the ddi_dma_sync(9F) call).
   *
!  * If the only mapping that concerns the driver is one for the kernel,
!  * the flag DDI_DMA_SYNC_FORKERNEL can be used. This is a hint to the
   * system that if it can synchronize the kernel's view faster
   * that the CPU's view, it can do so, otherwise it acts the
   * same as DDI_DMA_SYNC_FORCPU. DDI_DMA_SYNC_FORKERNEL might
   * speed up the synchronization of kernel mappings in case of
   * non IO-coherent CPU caches.