| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | umstc_intr is not in process context when adjusting wscons brightness. When brightness |   deraadt | 2020-09-14 | 1 | -4/+31 |
| | | | | | | | is pushed to 0, the backlight is disabled by some backend code which happens to sleep. Solve this by bouncing to process context via a task. ok kettenis | ||||
| * | uhidev(4) does apply the SET_IDLE request to all its child drivers |   mglocker | 2020-08-23 | 1 | -1/+4 |
| | | | | | | | | | | | | | | | today. This doesn't seem to be right, since SET_IDLE limits the reporting frequency for interrupt IN endpoints, normally only required on keyboard and mouse-like input devices. We noticed recently that other device types, like e.g. the Cyrus soundKey uaudio(4), will stall after the SET_IDLE request has been issued. Therefore we move the SET_IDLE request only to the uhidev(4) child drivers which seem to require this request. Those we have identified to be; ukbd(4), ums(4), umstc(4), umt(4), utpms(4), and uwacom(4). Suggested and ok mpi@ | ||||
| * | add umstc(4) for Microsoft Surface Type Cover keyboards |   jcs | 2020-05-31 | 1 | -0/+172 |
 |
index : wireguard-openbsd | |
| WireGuard implementation for the OpenBSD kernel | Matt Dunwoodie |
| summaryrefslogtreecommitdiffstats |