Age | Commit message (Collapse) | Author |
|
Avoids an uninitialized variable warning. ok kettenis@
|
|
Silences an uninitialized warning in net/art.c
"reasonable" jmatthew@, ok mpi@
|
|
events and command completions as that's the only vector they can go to.
tx/rx queues are mapped to subsequent vectors.
ok mpi@ dlg@
|
|
Rename surrounding code to reflect that. ok kettenis@
|
|
information in struct acpi_attach_args.
ok mpi@
|
|
This prevent exiting processes from hanging when a slave pseudo terminal
is close(2)d before its master.
From NetBSD via anton@.
Reported-by: syzbot+2ed25b5c40d11e4c3beb@syzkaller.appspotmail.com
ok anton@, kettenis@
|
|
|
|
An invalid/corrupted hop6 option in rip6_input()/ip6_savecontrol() could
lead m_copydata(9)s' check to trigger a panic.
Fix from maxv@NetBSD where the problem was also reported by syzkaller.
Reported-by: syzbot+3b07b3511b4ceb8bf1e2@syzkaller.appspotmail.com
Reported-by: syzbot+7ee0eb2691d507fcad2e@syzkaller.appspotmail.com
ok sashan@, dlg@, claudio@, deraadt@
|
|
Purging this queue prevents a panic which occurs when a WPA2-enabled athn(4)
hostap interface is reconfigured while this queue contains frames.
In hostap mode, this queue contains group-addressed (broadcast) frames
which are buffered for clients sleeping in powersave state. Frames on
this queue are transmitted when it is time to send another beacon, at
which point in time sleeping clients wake up to receive such frames.
The panic message is "key unset for sw crypto", which can be explained as
follows: Group keys are cleared when the interface goes down. The beacon Tx
interrupt handler gets triggered by hardware when the interface comes back
up. This handler attempts to encrypt the queued frames for transmission,
resulting in the above panic since the group key has been zeroed out.
This panic has been observed with athn(4) by Jan Stary and Ted Patterson,
and Ted has confirmed that this patch fixes the problem.
ok kettenis@ (with the caveat that it's been a long time since he put our
AP-side powersave support into a working state)
|
|
block ack notifications sent by iwn(4) firmware").
This effectively reverts changes in how the driver interacts with firmware
and fixes connections getting stuck for unknown reasons, in two known cases:
One with an Airport Extreme 6th gen AP and another with a b-box 3V+ modem
using a Sagemcom MAC address for its built-in AP.
The Sagemcom case was observed by myself.
The Airport case was reported by Jeremy O'Brien via abieber@.
I am committing this now to prevent the problem from affecting 6.7 release
even though we don't yet understand what caused the problem.
ok mpi@
|
|
Fixes coverity CID 1492830.
ok sthen, deraadt
|
|
|
|
go for it deraadt@
|
|
ok sthen@, deraadt@
|
|
passed in when setting the RTC time instead of the global time_second.
ok mpi@
|
|
amd64/arm64/armv7/i386/hppa/sparc64 and move it to the end of machdep.c.
Wrap the existing time_read and time_write hooks into something that
can be used as a todr_handle.
ok mpi@
|
|
amd64/arm64/armv7/i386/sparc64 and move it to the end of machdep.c. Rework the
actual implementation for the MC14818 compatible RTC into something that can
be used as a todr_handle just like on amd64.
ok mpi@
|
|
ok deraadt@
|
|
Besides making things simpler, this allows libsndio to figure out that
this is a control affecting all inputs (outputs) that needs to be
exposed.
|
|
synchroniation problems when playing youtube videos in chrome.
ok jsg@
|
|
There's no reliable way to decide whether a control must belong
to "inputs" or to "record". In other words both classes were
used for the same thing. Furthermore we've no "play" class which
tends to make things more confusing.
|
|
All other drivers use "dac" and libsndio needs the control name to
be "dac" for the control to be exposed.
|
|
Makes the code simpler and more flexible as the naming is done in a
single place where the full units list is available.
|
|
No object change.
|
|
This fix simplifies HW decrytion error checking: Frame header contents aren't
relevant because we are going to drop frames that had errors in any case.
I made a mistake by trying to add an exception for multicast frames at this
point. Frame header contents might not even be valid.
This problem was introduced with CCMP hardware offload support and detected
by Coverity (CID 1492755).
ok mestre@ kevlo@
|
|
From Yongqiang Sun
de32c6ad7a4fcb986e0e4f39d7497948b734b8c7 in linux 4.19.y/4.19.119
9941b8129030c9202aaf39114477a0e58c0d6ffc in mainline linux
|
|
|
|
|
|
enable the trickle charger.
|
|
being too clever trying to use the SMBus block reads/writes. Instead
the registers were written with an offset: Seconds were stored in the
minutes, minutes were stored in the hours. No wonder time was ticking
so slowly. Removing the bogus length field and simply writing/reading
the time register values is enough.
ok kettenis@
|
|
from the device tree to configures the RTC to be able to charge
a connected battery or capacitor.
ok kettenis@
|
|
unfortunately did not write the data to the register, but the
register offset. Oops.
ok kettenis@
|
|
DMA remapping in the same way as arm64. This relies on the dma-ranges
property in the device tree and allows us to get rid of the hack for
the Raspberry Pi in the dwctwo(4) driver.
Note that this does not include the hack in simplebus(4) that we have on
arm64 since firmware that has the dma-ranges is in widespread use now.
ok patrick@
|
|
This flag restricts a wireless driver to MCS0 - MCS7 for both transmission
and reception. It can be set to work around packet loss in 11n mode caused
by unused antenna connectors on a MIMO-capable wireless network device.
man page tweak from tracey@
ok deraadt@
|
|
(aka link field) of 0 specifies an empty tuple body. This implies
that a tuple length of 0 is actually allowed, so we don't need to
error out if we encounter one. Seen on an SDIO-connected ath10k.
ok kettenis@
|
|
amd64/arm64/armv7/sparc64 and move it to the end of machdep.c. Rework the
actual implementation for the MC14818 compatible RTC into something that can
be used as a todr_handle just like on amd64.
ok sthen@
|
|
|
|
clear the NOCACHE flag, since if we are doing a delayed write the buffer
must be cached or it is thrown away when the "write" is done.
fixes vnd on mfs regress tests.
ok kettenis@ deraadt@
|
|
fixed values for the divisors, but the imxesdhc(4) nodes for
SD Cards usually have an assigned clock rate of 200 MHz instead of
400 MHz. So instead of just clearing the divisor, we should set it
according to what is asked. This also allows us to add the clock
for the second imxesdhc(4) node to the list, which I have previously
skipped, since otherwise the controller would have been clocked too
high.
ok kettenis@
|
|
those are already on, since on those machines we mostly boot from SD/MMC
and U-Boot prepares them for us. On machines with a WiFi on imxesdhc(4),
U-Boot isn't necessarily configured to do so. Enabling the clocks is the
right thing to do anyway.
ok kettenis@
|
|
imxesdhc(4) device tree nodes.
|
|
and move it to the end of machdep.c. Rework the actual implementation
for te MC14818 compatible RTC into something that can be used as a todr_handle.
ok mpi@
|
|
and move it to the end of machdep.o.
ok mpi@
|
|
From Vitaliy Makkoveev, ok visa@
|
|
ok kevlo@ mpi@
|
|
|
|
A Type-C controller has multiple tasks. Even though the orientation
of the plug doesn't matter for the user, it matters for the hardware.
To be able to know how to route the SuperSpeed pins you need to know
which way the plug is connected. Also you need to know if you're a
sink/source or device/host. To get the first connection, you toggle
between the modes until you find a connection. In case you see that
a sink is connected, you can turn on USB Vbus to power the sink.
This driver explicitly does not implement USB's Type-C state machine,
but if we get more and more of these controllers it might be worth
doing. Also there's no support for Power Delivery messages yet.
"go for it" kettenis@
|
|
can't be enabled.
|
|
to i.MX27, they actually need different bits to be set than the i.MX27.
The i.MX8MM's node instead rightfully only claims to be compatible to
i.MX7D, since it's the same implementation. Thus change imxehci(4) to
also match the i.MX7D compatible.
ok kettenis@
|
|
perfectly happy without it.
ok patrick@
|