| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Display name taken from existing pcidevs context (previous devices in
same family) and verified against AMD's "43871 Register Reference Guide"
for this platform
|
|
that we haven't implemented yet.
|
|
|
|
ok mlarkin@
|
|
OK stsp@
|
|
Tests: 7260 ccardenas, 7265 myself, 3165 Bruno Flueckiger, 8265 Tracey Emery.
ok ccardenas@, "ich bitte darum" benno@
|
|
Use zero-padding to get double-digit HH:MM:SS and space-padding for
the DOM.
ok visa@
|
|
|
|
|
|
not in INIT state. Otherwise we can have bogus state changes on ifconfig
down. Also don't try to end a scan if we were not scanning.
|
|
the channel specification (channel, freq, bandwidth, control channel)
which is parsed and understood by the bwfm(4) firmware. Another part
is that we shouldn't start a scan if the channel is selected by the
user, otherwise we override the chosen channel. The remaining part is
bringing the device down properly. If it's not disabled properly, we
cannot bring it up again.
ok stsp@
|
|
ok mpi@
|
|
and initialize bwfm(4) later in the case that the firmware was not
available on bootup and was only later installed.
ok stsp@
|
|
support to their ATF fork and I expect other vendors that bothered to
backport the early workaround to do the same. And another ATF update is
needed anyway to implement the workaround for Spectre variant 4i
(CVE-2018-3639).
ok patrick@, mlarkin@, jsg@
|
|
|
|
ok stsp@
|
|
BARs, where the second one is much larger than the first. Both need
to be properly aligned in the given extent. Since the first one is
smaller, it will "unalign" the next free space and thus create a gap
so that the second BAR cannot be properly aligned in the given space.
By mapping the second BAR first, it will automatically have proper
alignment. The first BAR, which has fewer alignment requirements,
fits well after the initial allocation. Fixes bwfm(4) on APU 1.
Debugged and solved by kettenis@
|
|
and implementing this interface only really makes sense for architectures
that use a direct map.
ok patrick@, visa@
|
|
ok mlarkin@
|
|
interrupt when it is shared by other devices.
Fixes a regression reported by nigel@ where USB stopped working after
the radeondrm update on a machine where ohci shared an interrupt with
radeondrm.
|
|
them on. Prevents a panic on the AZW Z83-S that is somewhat buggy and
checks whether the GPO3 controller is available and then pokes a pin on
GPO2. It shouldn't do that but we should make sure all the devices that
it depends on attach first anyway.
ok patrick@
|
|
rotate the inteldrm(4) framebuffer console. And judging from (somewhat)
recent commits to Linux, this happens to be the only machine where the
display needs to be rotated counterclockwise. So change the heuristic to
rotate clockwise and add a quirk for the Asus T100HA.
ok stsp@, mlarkin@, jsg@
|
|
Validate the input with timespecfix before truncating to a timeval.
timespecfix does not round, so we need to to it by hand after validation.
FreeBSD and NetBSD check the input with this range, we ought to as well.
Also add a regression test for this case.
ok tb@
|
|
Instead of converting timespec -> timeval and truncating the input,
check with timespecfix and use tstohz(9) for the tsleep.
All other contemporary systems check this correctly.
Also add a regression test for this case.
ok tb@
|
|
Replace a hex constant with the correct CR0_* define in mptramp.S.
Clean up lots and lots of whitespace glitches.
no binary change.
ok mlarkin@
|
|
system's ino for VOP_GETATTR(9) and VOP_READDIR(9) rather than the
internally generated fuse ino.
ok mpi@
|
|
This ensures the keyboard is using the expected scancode.
From miod@, problem also noticed by Markus Hennecke, ok otto@
|
|
ok bluhm@, visa@
|
|
vmm_fpu{restore,save}()
ok mlarkin@
|
|
ok kettenis@
|
|
Note: the sensor will report state UNKNOWN until at least one port
replicator event (docked / undocked) is received.
Diff from Tobias Tschinkowitz, thanks.
ok stsp@. deraadt@ also ok'ed an earlier version of the diff
|
|
ok stsp@
|
|
It does not make sense to call if_get() again, just pass ifp as
parameter. Move the IFT_CARP check into the function instead of
doing it everywhere. Replace the inverted match variable logic
with simple returns.
OK mpi@ friehm@
|
|
|
|
a ROHM part (BD2613GW) and once more the datasheet is only available under
NDA.
Disabled for now until bugs in dwiic(4) are fixed.
|
|
doesn't implement it.
ok mpi@
|
|
firmware requires on SDIO-connected chips.
From ketttenis@
|
|
|
|
controller. Some BIOSen deliver them to us in D3.
Override card detect if ACPI says that the child devices are non-removable.
ok mlarkin@
|
|
ok mlarkin@
|
|
a TI part (SND9039) but the datasheet is only available under NDA because it
contains "Intel proprietary information".
Initial implementation handles the thermal sensors, providing data to acpi(4)
which is used by acpitz(4). Power management functionality will be added
later. Disabled for now until some bugs in dwiic(4) are fixed.
|
|
ok mlarkin@ mpi@
|
|
ok mlarkin@
|
|
ok mpi@
|
|
initialised. Rather than failing, requests are now queued.
ok mpi@
|
|
VOP_CLOSE(9). The associated FUSE file handle is however not closed at this
time and is instead closed on VOP_RELEASE(9) because that's the only time
it's guaranteed to be no longer used. Directory handles are now only closed
on VOP_RELEASE(9) for the same reason.
ok mpi@
|
|
or kernel lock when accessing a socket. For pf key sockets it is
kernel lock, so add its protection in pfkey_sendup(). Fixes a
kernel lock assertion panic reported by Peter J. Philipp.
OK mpi@ visa@
|
|
ok mlarkin@
|
