Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
No functional change.
|
|
That's what 'bootable' means in the MBR world. GPT
partitions created by '-b' are unaffected.
Pointed out by kettenis@, obviating need for new option.
|
|
This comes from NetBSD:sys/dev/ic/mb89352.c fix by tsutsui:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/ic/mb89352.c.diff?r1=1.57&r2=1.58&f=h
Tested on LUNA-88K2 by me.
|
|
|
|
This driver provides support for battery chargers connected to GPIO pins,
such as those found on the Pinebook Pro.
OK kettenis
|
|
This driver provides support for LEDs connected to GPIO pins,
such as those found on the Pinebook Pro.
OK kettenis
|
|
OK dtucker deraadt djm
|
|
|
|
This prevents a bogus "device timeout" if firmware sends a IWM_BA_NOTIF
instead of IWM_TX_CMD in order to let us know that a frame has been sent
on a Tx aggregation queue. Such behaviour was observed on iwx(4), and there
is reason to believe that iwm(4) might also be affected by this issue.
Tested by Jean-Michel Bessot on 7265 via bugs@ where this change seems
to prevent random device timeouts.
Tested by myself on 8265 with no apparent behaviour change seen.
|
|
|
|
- Use of goto will skip zeroing of 88110-specific comparison bits (bitn
12-17) in some cases. (Move their zeroing closer to the point of
their computation.)
- Computing of the "in interval" bits should not be performed when the
S2 operand is negative.
Spotted by Tetsuya Isaki (nono project), suggested diff and description
from Miod Vallat. Tested on the real hardware by Isaki and me.
|
|
|
|
To issue AT commands (AT+CUSBPIDSWITCH=9003,1,1 and AT+CLANMODE=1) to
change to MBIM mode.
ok deraadt@
|
|
|
|
Upstream removed history file support for secure mode. The history file
feature is off by default already, disallowing it altogether in secure
mode allows us to drop wpath.
Added a note about it to manual page.
ok benno, deraadt
|
|
When multiple frames are sent in a batch on a Tx aggregation queue our
current firmware version does not provide the IWX_TX_CMD notification.
Older versions used to provide this (as observed on iwm(4) devices),
but our current firmware only sends IWX_BA_NOTIF.
This means we need to reset the Tx timer upon BA_NOTIF in order to
avoid a bogus "device timeout" trigger from our watchdog handler.
Do this as soon as the BA notification has been validated.
|
|
The length checks need to be >= rather than > in order to ensure the string
remains NUL terminated. While here consistently check wi before using it
so we have the same idiom throughout this function.
Issue reported by GoldBinocle on GitHub.
ok deraadt@ tb@
|
|
My assumption that frames which are buffered on the power save
queue were already encrypted was wrong. And the issue which this
change intended to fix is still present (reported by Mikolaj Kucharski).
|
|
Throughput goes up to 100 Mbit/s under ideal conditions.
This is mostly working and stable, however rare occasional hangs may occur
where the device stops giving us interrupts for reasons which are not yet
understood.
In such cases ifconfig down/up will recover the interface. Regardless, this
code seems to be stable enough for remaining issues to be resolved in-tree.
My working assumption is that the remaining issues were always present but
only trigger under increased load when firmware is driven with Tx agg enabled.
Feedback is welcome, especially if stability issues turn out to be worse than
expected! As usual, please enable "ifconfig iwx0 debug" when reporting issues.
Tests on ax200/ax201:
myself, dv, hrvoje, Stefan Hagen, kevlo, Eric Auge, mlarkin, jmc, Mark Patruck
Of which only me and jmc have reported seeing a small amount of hangs during
continuous usage over about 2 weeks.
|
|
sessions entirely in firmware. This will be used by iwx(4).
|
|
ok inoguchi
|
|
ok claudio
|
|
length of that key is also a secret, may as well clear it also
|
|
execve can be detected better
reported by Alejandro Colomar, ok millert
|
|
|
|
|
|
OpenBGPD and GoBGP dump so that it works with all the MRT implementations
out there supporting this.
While there do some additional minor cleanup.
OK deraadt@
|
|
|
|
|
|
fixes a bug where ruleset was not evaluated with the expanded address.
reported by Stefan Haller
ok millert@
|
|
ok millert@
|
|
hardware is incorrect. In this case, make sure the amount of "stolen"
memory is at least as large as the EFI framebuffer such that the
driver doesn't use this memory until we've switched to the framebuffer
allocated by the amdgpu(4) driver.
Needs further investigation why the size reported by the hardware is
incorrect.
Tested by djm@
ok jsg@, deraadt@
|
|
ok deraadt@
|
|
again as we go along). ok deraadt
|
|
too much in btrace(8).
OK mpi@ deraadt@
|
|
be in base set, for KARL
spotted by pavel korovin
|
|
them back in special like in the main disklabel Makefile.
OK deraadt@
|
|
Committing on behalf of jmc
OK deraadt
|
|
Fixes issues with dead touchpads after resume on some machines.
ok jcs@, deraadt@
|
|
|
|
|
|
compile options required for sparc64 (partition alignment, in particular)
noticed by bluhm during testing
|
|
encoding is supported. Instead, silently ignore such requests. Gets rid
of the following warning emitted by kbd(8) while booting with a ucc
keyboard attached and /etc/kbdtype being present:
kbd: unsupported encoding uk on /dev/wskbd2
I ended up repurposing KB_MACHDEP as is became unused back in 2008. Note
that running a kernel with this commit applied requires kbd and
wsconsctl to be recompiled in order to show correct encodings.
Problem reported by landry@ and ok deraadt@
|
|
Requested by & OK sthen
mdoc clue by schwarze
|
|
ok deraadt
|
|
block delivery of signals outside of sigsuspend(). With this the test
is more reliable. pause() is implemented as two syscalls and so it is
possible to catch a signal on the first syscall and than be stuck on
the second waiting for something that already happened.
OK millert@ deraadt@ bluhm@
|
|
should be used when the client identifier is not a hardware address,
for example if it's just a string. It turns out that the majority of
dhcp clients (and possibly servers?) does not do this but rather
transmits the client identifier verbatim if a string is
configured. The first character becomes the hardware type.
Make dhcpleased(8) behave the same.
Difference in behavior with dhclient(8) and interoperability issues
with dhcp(8) first pointed out by Olivier Cherrier on misc@
OK sthen
fine to get it in for 7.0 deraadt
|