| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
While the for-loop checks that thie value has changed since we wrote to
it, the timeout-condition checked for non-zero, which is wrong. This
means that we didn't realize the firmware wasn't started. While there,
make sure the shared DRAM address is inside the chip's address space.
|
|
|
|
| |
the same time.
|
|
|
|
|
| |
on the rx/tx complete rings has increased slightly to accomodate possible
new features.
|
|
|
|
|
|
| |
so that we can provide IOMMU-hooked bus DMA tags for each PCI device.
ok kettenis@
|
|
|
|
| |
ok patrick@
|
|
|
|
|
|
| |
This also fixes two NULL ptr derefs in later code path.
OK patick@, krw@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the first cut of this diff was made with coccinelle using this spatch:
@rule@
type caddr_t;
expression m, off, len, cp;
@@
-m_copydata(m, off, len, (caddr_t)cp)
+m_copydata(m, off, len, cp)
i had fix it's opinionated idea of formatting by hand though, so
i'm not sure it was worth it.
ok deraadt@ bluhm@
|
| |
|
|
|
|
| |
ok mpi@
|
|
|
|
| |
ok mpi@
|
|
|
|
| |
ok mpi@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The timecounter struct is large and I think it may change in the
future. Changing it later will be easier if we use C99-style
initialization for all timecounter structs. It also makes reading the
code a bit easier.
For reasons I cannot explain, switching to C99-style initialization
sometimes changes the hash of the resulting object file, even though
the resulting struct should be the same. So there is a binary change
here, but only sometimes. No behavior should change in either case.
I can't compile-test this everywhere but I have been staring at the
diff for days now and I'm relatively confident this will not break
compilation. Fingers crossed.
ok gnezdo@
|
|
|
|
| |
ok kettenis@ pirofti@
|
|
|
|
| |
ok kettenis@
|
|
|
|
| |
ok kettenis@
|
|
|
|
|
|
|
| |
This mostly adjust the interrupt masking and status support since this
variant lacks the UINTM and UINTP registers.
ok patrick@
|
| |
|
|
|
|
| |
initial diff from Sven Wolf
|
|
|
|
|
| |
matches radeon and i915
reported by Benjamin Baier
|
| |
|
|
|
|
|
|
|
| |
we don't get a file handle back which could be closed again, and therefore
we couldn't toggle sc_open back to zero.
Spotted and ok anton@
|
|
|
|
|
|
| |
parameters which are usually called 'p'.
Spotted and ok anton@
|
|
|
|
| |
Spotted and ok anton@
|
|
|
|
| |
ok patrick@
|
|
|
|
| |
default.
|
|
|
|
| |
arbitrary and inspired by other USB drivers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
specification:
https://www.kernel.org/doc/html/v5.10/userspace-api/media/v4l/open.html#f1
The discussion has been started by jca@, who has implemented this
behavior recently, but limited to the same process. This diff extends
this behavior to any process. The first process which opens a stream
will become the device owner. Other processes are still allowed to call
certain ioctls, but none which are related to the start/stop of a
stream, or manipulation of the streaming buffers. At the moment only
VIDIOC_G_CTRL and VIDIOC_S_CTRL are supported to be called by non-
device owner processes, which should be extended further in the future.
There is no additional kernel locking implemented at the moment, since
video(4) already runs under the KERNEL_LOCK(), which we expect to be
sufficient for now (as discussed with claudio@).
A lot of improvement input received from anton@.
ok anton@
|
|
|
|
|
|
| |
reports about broken devices, e.g. for ukbd(4) and fido(4).
ok mpi@
|
|
|
|
|
|
|
|
| |
this is the only real diff we have left outstanding on a box that
experienced rx lockups. since adding this change it's been happy
for the last 4 weeks and counting so far.
ok jmatthew@
|
| |
|
|
|
|
| |
ok patrick@, deraadt@
|
|
|
|
| |
device has connected.
|
|
|
|
| |
receiver.
|
|
|
|
| |
Should help diagnose various reports regarding missing battery sensors.
|
|
|
|
|
|
|
|
|
| |
register. Use 32-bit reads and writes to access the URXH and UTXH
registers. They're documented as 32-bit registers in the Exynos 4 and
Exynos 5 User Manuals and accessing URXH with an 8-bit read triggers a
fault on Apple's M1 SoC.
ok patrick@
|
|
|
|
|
|
|
|
|
| |
Don't set taskq to system_wq in INIT_WORK(). Test if taskq pointer is
non-NULL before calling taskq_barrier() in flush functions.
fixes a black screen on boot problem with 5.10.y drm using nano x1
bisected by jcs@ to
'drm/i915: Always flush the active worker before returning from the wait'
|
|
|
|
| |
ok kettenis@
|
|
|
|
|
|
|
| |
CID 1501716
ok kevlo@
and mestre@ had the same diff
|
|
|
|
|
|
| |
CID 1501713
ok jmatthew@
|
|
|
|
| |
CID 1501705
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
necessary ones. Solves a regression introduced with the arrival of
uhidpp causing some Logitech HID devices from attaching to its
appropriate driver.
Thanks to <naszy at poczta dot fm> and Peter Kane <pwkane at gmail dot com>
for reporting and trying out diffs.
ok mglocker@
|
|
|
|
|
|
| |
uhidev_set_report_dev(). Needed by some upcoming changes to uhidpp.
ok mglocker@
|
|
|
|
|
|
| |
report id, there's no point in trying to find a matching sub device.
ok mglocker@
|
|
|
|
| |
ok visa
|