created | 2020-02-07T02:08:25Z |
---|---|
begin | 2020-01-22T00:00:00Z |
end | 2020-01-23T00:00:00Z |
path | src/sys |
commits | 16 |
date | 2020-01-22T00:17:46Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/scsi/scsi_base.c | log | diff | annotate |
message |
scsi_delay(): sleep without lbolt If we want to sleep for a multiple of seconds we can do that without involving lbolt. This may cause some paths to sleep longer than they have on average, as sleeping on lbolt wakes you up within one second, not after one second. If this is a problem we will need to shorten the intervals given to scsi_delay(). With insight from deraadt@. ok krw@ |
date | 2020-01-22T02:02:31Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/dev/pv/xbf.c | log | diff | annotate |
message | xbf(4): tsleep(9) -> tsleep_nsec(9); ok mikeb@ |
date | 2020-01-22T02:25:11Z | |||
---|---|---|---|---|
author | krw | |||
files | src/sys/dev/usb/xhci.c | log | diff | annotate |
message |
Add a zero length TD, rather than adding a zero length TRB to the original TD, when a transfer is a multiple of the max packet size. The zero length TD will have a NULL xfer pointer. As a result "NULL xfer pointer" situations become perfectly normal. So change the log_warnx() that issues that verbiage to a log_debug(). Note that the original transfer will complete and report its result up the USB stack before the zero length transfer is executed. Fixes (at least) urtwn(4) interfaces. Feeback, cluebats, fixes and ok patrick@ |
date | 2020-01-22T03:26:02Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/dev/ic/w83l518d_sdmmc.c | log | diff | annotate |
message | wbsd(4): timeout_add(9) -> timeout_add_msec(9); ok deraadt@ |
date | 2020-01-22T03:29:58Z | |||
---|---|---|---|---|
author | mlarkin | |||
files | src/sys/arch/amd64/include/vmmvar.h | log | diff | annotate |
message | Remove trailing whitespace, no code change. |
date | 2020-01-22T03:43:13Z | |||
---|---|---|---|---|
author | krw | |||
files | src/sys/dev/usb/umass.c | log | diff | annotate |
message |
Some devices do not update the TRB transfer residual information as STALL'ing. So use the standard's recommended csw.dCSWDataResidue and copy data only on successful completion of the request. Fixes issue where N bytes are requested, M bytes are returned, and the device STALL's because it has no more data to give. Thus resulting in no data is copied to the user buffer but the claim being made that said buffer now contains M new bytes of valid data. e.g. when cdio(1) asks for 4096 bytes of media data and only 96 bytes are provided by the CDRW device. Feeback, cluebats, fixes and ok patrick@ |
date | 2020-01-22T04:17:50Z | |||
---|---|---|---|---|
author | kettenis | |||
files | src/sys/dev/pci/drm/ttm/ttm_bo.c | log | diff | annotate |
message |
Make ttm_bo_unmap_virtual_locked() actually unmap things. Fixes cursor issues and suspend/resume on amdgpu(4). Might help radeondrm(4) issues as well. tested by mortimer@, abieber@, krw@ ok jsg@ |
date | 2020-01-22T05:06:19Z | |||
---|---|---|---|---|
author | tedu | |||
files | src/sys/arch/i386/conf/GENERIC | log | diff | annotate |
src/sys/dev/isa/files.isa | log | diff | annotate | |
src/sys/dev/isa/Attic/rtfps.c | log | diff | annotate | |
message |
rm rtfps driver. disabled and man page doesn't inspire much confidence. ok deraadt |
date | 2020-01-22T05:25:05Z | |||
---|---|---|---|---|
author | patrick | |||
files | src/sys/dev/fdt/simplefb.c | log | diff | annotate |
message |
The Pinebook Pro's u-boot seems to add a zero-length framebuffer node, which essentially means that there is none. Make sure we don't attach in that case, so that we don't panic while trying to map it. ok kettenis@ |
date | 2020-01-22T07:52:31Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/drm/include/drm/drm_vma_manager.h | log | diff | annotate |
src/sys/dev/pci/drm/include/linux/mm.h | log | diff | annotate | |
message |
Remove empty unmap_mapping_range() define and hide drm_vma_node_unmap(). Errors at compile time are preferred over being silently broken. ok kettenis@ |
date | 2020-01-22T07:52:37Z | |||
---|---|---|---|---|
author | deraadt | |||
files | src/sys/dev/fdt/rkclock.c | log | diff | annotate |
src/sys/dev/sdmmc/sdhc.c | log | diff | annotate | |
src/sys/kern/kern_unveil.c | log | diff | annotate | |
message |
delete wasteful ;; ok tedu |
date | 2020-01-22T11:56:41Z | |||
---|---|---|---|---|
author | patrick | |||
files | src/sys/dev/fdt/dwmmc.c | log | diff | annotate |
message |
Ack SDIO interrupts earlier on dwmmc(4). While handling an SDIO interrupt it is possible that the card immediately raises another one. Since the interrupt seems to be edge triggered, and we only acked it after said handling, it was possible we lose the next one. This heavily improves bwfm(4) on the Pinebook Pro. ok kettenis@ |
date | 2020-01-22T12:08:55Z | |||
---|---|---|---|---|
author | patrick | |||
files | src/sys/dev/sdmmc/if_bwfm_sdio.c | log | diff | annotate |
message |
Recognize BCM4345 rev 9, which requires a different firmware, as shipped with the Pinebook Pro as an AMPAK AP6256 module. |
date | 2020-01-22T14:52:14Z | |||
---|---|---|---|---|
author | mpi | |||
files | src/sys/dev/pckbc/pms.c | log | diff | annotate |
message |
Unbreak !DIAGNOSTIC build. From Andrius V vezhlys (at) gmail, on bugs@ |
date | 2020-01-22T22:56:35Z | |||
---|---|---|---|---|
author | dlg | |||
files | src/sys/kern/uipc_mbuf.c | log | diff | annotate |
src/sys/sys/mbuf.h | log | diff | annotate | |
message |
add ml_hdatalen and mq_hdatalen as workalikes of ifq_hdatalen. this is so pppx(4) and the upcoming pppac(4) can give kq read data dn FIONREAD values that makes sense like the ones tun(4) and tap(4) provide with ifq_hdatalen. |
date | 2020-01-22T23:06:05Z | |||
---|---|---|---|---|
author | dlg | |||
files | src/sys/net/if_pppx.c | log | diff | annotate |
src/sys/sys/conf.h | log | diff | annotate | |
message |
add pppac(4) code for a dedicated PPP Access Concentrator interface. this is so we can pull the PIPEX code out of tun(4), which in turn will let us lock down tun(4) functionality and start moving the code around. ok claudio@ yasuoka@ |