Age | Commit message (Collapse) | Author |
|
proper BSD way where the third argument is always a pointer and data is
transferred between userland and kernel using copyin(9) and copyout(9).
Intead an int is encoded in the thirs argument. This works on 32-bit
architectures and little-endian 64-bit architectures. But not on
big-endian 64-bit architectures. Deal with this by handling the argument
as long (which matches the size of a pointer).
Hopefully we can eliminate these ioctls in the near future.
ok deraadt@
|
|
|
|
initialize the 'version' field. Not numbers.
|
|
initialize the 'version' field. Not numbers.
|
|
actual length which has been allocated. We saw cases where the
wTotalLength value is changing on a second read, e.g. when a USB device
was waked up from sleep mode.
ok mpi@
|
|
struct scsi_rw_10.
ok gnezdo@ jmatthew@ (who also did sparc64 compile test)
|
|
Logitech keyboard for unknown reasons.
Reported by denis@
ok djm@
|
|
|
|
|
|
intr_barrier() now uses the argument so directly call sched_barrier(NULL)
which is what intr_barrier() used to do until recently.
problem reported by and fix tested by Andre Stoebe
|
|
Due to unstable of PLL1, sometimes the system has hanged up
especially at boot. This is observed at Allwinner H3/H2+ processor.
To solve the problem, PLL1 setting procedure is same as Linux.
1. change clock source to 24MHz
2. wait 1usec (new)
3. disable PLL1 (new)
4. set new NKMP value, but M should be 1
5. re-enable PLL1 (new)
6. wait PLL1 stable (modified)
7. change clock source to PLL1
8. wait 1usec (new)
Once disable PLL1 before setting NKMP is very important. And, sometimes
LOCK flag is set even if PLL has not locked yet so wait for PLL is
modified with simple delay() by the value of PLL_STABLE_TIME_REG1 register.
Not only Allwinner H3/H2+ but also all (i.e. A64) Allwinner processors
datasheet has "If the clock source is changed, at most to wait for 8
present running clock cycles." sentence at CPU clock source selection
field of CPU/AXI configuration register. But this is ambiguous that
_who_ should do _what_ during that cycles.
It is unclear that changing clock source itself invoke PLL1 unstability.
For safety, added 1usec wait after changing clock source like Linux.
ok by kettenis@, thanks to adr at sdf dot org
|
|
no other thread is currently within a remote section. Otherwise, the
remote subsystem could end up in a broken state where it doesn't reset
the necessary bits upon leaving the remote section.
Therefore introduce the kr_barrier() routine which waits until all
ongoing remote sections have been left. Also, extend the scope of the
mutex to also cover fields of struct kcov_dev. This is necessary to
ensure correctness.
Reported-by: syzbot+64122a5f01be1b1abb96@syzkaller.appspotmail.com
|
|
something more generic. It will soon cover the whole kcov subsystem.
|
|
|
|
device which returns a spurious value for wTotalLength on a configuration
descriptor request. Therefore don't relay on wTotalLength for free(9)
but on the length variable which was used for the malloc(9) before.
The issue was reported by
Mikolaj Kucharski <mikolaj (at) kucharski (dot) name> on bugs@.
Discussed and ok deraadt@
|
|
'NULL' instead of '0'.
ok deraadt@
|
|
as needed on xhci(4) machines. On non-xhci(4) we save and restore the
toggle bit on close/open of a pipe. With xhci(4) this does not seem to
be possible, at least I haven't yet found it. This means that on those
machines with xhci(4), after a pipe close/open, the device will use the
previous state, while xhci(4)'s state is reset to default. By issuing
a clear endpoint stall we reset the device's toggle bit. Now every
time a /dev/uhid is (re-)opened the state should be synchronized.
Discussed with damien@, mpi@ and Pedro Marteletto
ok markus@
|
|
fixes errors building with option DEBUG reported by phessler@
|
|
after Device() ones, since we should prefer the newer node type.
If we see any Device() nodes, don't attach acpicpu(4) to any Processor()
nodes if they're also present. This also makes acpitz(4) and
acpipwrres(4) devices attach slightly later.
ok kettenis@, also tested by jmc@
|
|
from an access point or is put down via ifconfig. Otherwise new Rx block ack
sessions could be refused upon reassociation due to a bogus counter value.
Found by zxystd from the OpenIntelWireless project (drivers for macOS).
Testing by jmc@, kevlo@, and Sven Falempin.
ok phessler@ mpi@ kevlo@
|
|
ok jmatthew@
|
|
and was always checked in concert with SDEV_ATAPI. Just rely on SDEV_ATAPI and
SDEV_UMASS in all but the one place sd(4) where SDEV_ONLYBIG is set
independently of SDEV_ATAPI/_UMASS.
ok jmatthew@
|
|
From Alex Deucher
813b2c197929540e700dc3d42b2c8136795c5d4c in linux 5.7.y/5.7.18
|
|
From Felix Kuehling
be580abecf13ebdcf6c16ec79d941c35017c94be in linux 5.7.y/5.7.18
c0001213d195d1bac83e0744c06ff06dd5a8ba53 in mainline linux
|
|
From Krunoslav Kovac
b9d077f3781412f304968cf806f636ee91b4470e in linux 5.7.y/5.7.18
d2e59d0ff4c44d1f6f8ed884a5bea7d1bb7fd98c in mainline linux
|
|
From Paul Hsieh
3f88e2e7a7943ef07a384f653f01832600bb91dd in linux 5.7.y/5.7.18
8e80d482608a4e6a97c75272ef8b4bcfc5d0c490 in mainline linux
|
|
From Jaehyun Chung
cdda25b43e0efb8df20a6f9956ff9091a1355328 in linux 5.7.y/5.7.18
79940e4d10df9c737a394630968471c632246ee0 in mainline linux
|
|
From Stylon Wang
a4615f3893f39560dd3e71865e80bccd20330321 in linux 5.7.y/5.7.18
b24bdc37d03a0478189e20a50286092840f414fa in mainline linux
|
|
From Daniel Kolesa
9917538295f9319dc7c6cf63d25eef89f302d81e in linux 5.7.y/5.7.18
f41ed88cbd6f025f7a683a11a74f901555fba11c in mainline linux
|
|
OK deraadt@, mpi@
|
|
|
|
avoids unimplemented function warnings when running Mesa iris driver
|
|
reliably.
|
|
ok mglocker@
|
|
|
|
|
|
found the hard way by deraadt@
|
|
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@
|
|
example for control method batteries that are attached to I2C but use an
OperationRegion() to access the I2C device.
ok jcs@, gnedzo@
|
|
the code configuring the parser, we do not yet add the proper multicast
filters.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
From hersen wu
adc8db21719668a4bf25ef0bef72c575d0a81cf5 in linux 5.7.y/5.7.17
8b0379a85762b516c7b46aed7dbf2a4947c00564 in mainline linux
|
|
From Stylon Wang
bab191af99bd97db80ba19aafeea8081949bbe53 in linux 5.7.y/5.7.17
c5892a10218214d729699ab61bad6fc109baf0ce in mainline linux
|
|
From Sandeep Raghuraman
bac04cf4ea5cd6819828b33567f23431e2468708 in linux 5.7.y/5.7.17
f87812284172a9809820d10143b573d833cd3f75 in mainline linux
|