| Age | Commit message (Collapse) | Author |
|
Tag spdx, improve document description for apropos, improve synopsis
for clarity and consistency, improve description to explain usage,
improve hardware for hardware release notes, mention the sysctl, xref
the application to use this driver, improve history.
MFC: no (unless change adding CH9102/CH343 mfcs)
Fixes: 1395712cab8e9 (add support for CH9102 and CH343)
Reviewed by: carlavilla, kevlo
Differential Revision: https://reviews.freebsd.org/D51036
(cherry picked from commit f0ba0b99ef0a9cf9e7822278d7d2bc0a80911361)
|
|
Merge commit '7e59b238fcf32f3d365e78ddc702ca494e1ff68d'
This commit partially reverts the previous vendor import, given that the
"type" keyword has been historically mandatory and should not be removed
by "-R all". This was clarified in the man page.
Reported by: glebius
PR: 219467
MFC after: 1 week
(cherry picked from commit 4250d2ad991b7bb9915e4c6b6d93b17369747ff0)
|
|
This is required for MSI support on GCE ARM64 instances which is
prerequisite to gve(4) not panicking at boot, and nvme(4) also has
a real sad time without interrupts. Tested on a variety of c4a VMs.
This is meant to be a temporary hack; long term fix would be to
check for the hypervisor and quirk gve(4) device with
PCI_QUIRK_ENABLE_MSI_VM.
PR: kern/292081
(cherry picked from commit 9ae43352c89c776c8171f5881a984bc39acf5d6a)
|
|
Fix the arguments to the debug statement.
(slightly adjusted from the original submission by bz)
PR: 286448
(cherry picked from commit 75556c7e999e9095ce71558ae61f49c1ba61a192)
(cherry picked from commit 2e93d2f39d72e5542781165c368343d7d73643e9)
|
|
Precautiously bump __FreeBSD_version for various LinuxKPI changes
so they could be detected if needed (which they should not need to,
hopefully).
|
|
When lkpi_80211_txq_tx_one() calls into the crypto offloading parts to
possibly make space in the headroom, the beginning of our frame moves.
We have to reset hdr after that call as otherwise later classifications
based on the hdr->frame_control will fail or cause wrong classificaiton
of packets.
This makes sure frames will either be directly sent using (*mo_tx)()
or use the correct tid for the correct queue. This helps to get
rtwx8 packets flowing after BA was negotiated.
Sponsored by: The FreeBSD Foundation
Fixes: 11db70b6057e4
(cherry picked from commit f0395993e1ea83705e0da6623843e7d5d03f7269)
(cherry picked from commit 4d255abe992fef69c97ce10991d815eda638c76d)
|
|
Extend the normal compat.linuxkpi.80211.IF.dump_stas sysctl by
queue information. This was helpful for debugging various issues,
like selecting the outbound queue, stopping queues for BAR and helped
finding multiple bugs.
Sponsored by: The FreeBSD Foundation
(cherry picked from commit 32ea8209825af594cbfa1fc654d45eb9a6aab528)
(cherry picked from commit 6b9c0ac008a9c52b21b05c96ead6def41aa89ead)
|
|
Add a version of __const_bitcount<n> which can be used to get the
numbers at compile-time when __builtin_popcountg() is not available
(see sys/compat/linuxkpi/common/include/linux/bitops.h for LLVM before
19 and gcc before 14).
Obtained from: https://reviews.freebsd.org/D50995#1174884 by obiwac
Sponsored by: The FreeBSD Foundation
Reviewed by: brooks, emaste
Differential Revision: https://reviews.freebsd.org/D54301
(cherry picked from commit 27aa23cee81088b0ffa974eec9f03c654c36438e)
(cherry picked from commit 605389e40b938088718bd8aa75f4919884789927)
|
|
For consistency rename the "scheduled_txqs" tailq to
"txq_scheduled" and add a lock per txq ("txq_scheduled_lock[]").
We use the "_bh" locking as this called from the device driver.
This fixes panics due to concurrent access to the tailq, especially
in between "first" and "remove" on the out-direction and between
"insert" and "elem_init" on the in-direction.
This was easily reproducible just running iperf3 at basic rates for
a few seconds to minutes with multiple chipsets, not only rtw89.
Sponsored by: The FreeBSD Foundation
PR: 290636
Reported by: arved, and others before
(cherry picked from commit 567a097c8ab60d9fcd68a87c3c5ad605fe8715cc)
(cherry picked from commit 2e1156f75836a0e5a4026e13d72b54f272e705cb)
|
|
Always set CONFIG_ARCH_DMA_ADDR_T_64BIT as it is true for all
architectures we support. Add an option for CONFIG_NET_MEDIATEK_SOC_WED,
which we currently do not yet support.
Sponsored by: The FreeBSD Foundation
(cherry picked from commit 87aa494dfca73204516799033821ab1db184933f)
(cherry picked from commit e2ebe56c50e77f3302c85a8203f8fa4050ae0f54)
|
|
If CONFIG_NET_MEDIATEK_SOC_WED is not set then be silent; if
CONFIG_NET_MEDIATEK_SOC_WED is set we will enable logic or rather te
pr_debug("TODO") calls for now.
Spsonsored by: The FreeBSD Foundation
(cherry picked from commit 51c73fc5f5dd95c6a0e3d232091a732a14c7ecc9)
(cherry picked from commit 7ed3a99f3563fce1f1088a376151e7ad68b738d6)
|
|
Move the enum and leave a comment on the struct member for the vif
about the type.
No functional changes.
Sponsored by: The FreeBSD Foundation
(cherry picked from commit b10ff7ed37a9b891bec7e1093e44fa7abb2054b4)
(cherry picked from commit a714641fa5380cc320d23181d4b18f7f89ccd183)
|
|
The logic in device_release_driver() got disabled in 93b14194acaf2
and since left alone. Add a pr_debug() call so we have a chance to
notice if that code is actually still in need to be fixed and re-enabled.
Sponsored by: The FreeBSD Foundation
(cherry picked from commit fc9666d0fc0c2541e44bfbcaa5bb1b670395687c)
(cherry picked from commit 0f496780deee49cfd86f4e02db775b706405fef9)
|
|
We are ways away from implementing "airtime fairness" in LinuxKPI
(or rather net80211). For now make it an 'improve' rather than a
'todo' to get the logging away. Everything will work without it.
Sponsored by: The FreeBSD Foundation
(cherry picked from commit 86bfe5b4d5a7b90d3746059dd1f87cdd5a0bf90c)
(cherry picked from commit c55874da4cf57800fc8a665ee221e4c2e1ac6601)
|
|
cfg80211_chandef_create() gets passed a pointer to a cfg80211_chan_def.
It seems that several users are passing in an uninitialized variable
from the stack and expect cfg80211_chandef_create() to initialize it.
Run memset() on the struct, which for all callers currently seems to do
the right thing, to avoid later accesses to uninitialized struct members
like "punctured".
Reported by: CI (gcc build)
Sponsonred by: The FreeBSD Foundation
(cherry picked from commit 640205bc22c8b2bd31c766f4d0c409c183a8b8dc)
(cherry picked from commit d389d1ac1699aea517a18cf73486e7077cfbda46)
|
|
This includes some type cleanups as well as some shuffling of structs
and functions to sort dependencies out. Few new functions and defines
as well as new struct members. Minor fixes to style and debug logging.
This is the majority of changes. None of these should conflict with
current in-tree drivers. The final bit of changes will come along with
the driver updates adding an extra argument to function pointers.
(cherry picked from commit 0567484734ad9732978e189ebed042f6320e2471)
(cherry picked from commit f2b2d6c18a57abbedb14bf439ed5c69d648c47b6)
|
|
For the moment add skeleton functions for netif_device_attach/detach()
needed by rtw8[89] v6.17.
(cherry picked from commit 5ea941a4fbfd1ba2483e47fe30ed6713fe912284)
(cherry picked from commit 4bdd0e51d7113aadcbfba9a76d72d8e924c5dcdf)
|
|
This likely belongs in socket code which we do not have in LinuxKPI.
Needed by a wirless driver at v6.17.
(cherry picked from commit 88dbf83345feefa7181bd6df47786e1a8d1d304d)
(cherry picked from commit 3ad05fa24a240011a8252140ff6431cb0b7879d9)
|
|
We do not support Wireless Ethernet Dispatch (wed) on the mt76 (yet).
Add pr_debug calls with TODO in case we run into the calls anyway so
we could deal with them.
(cherry picked from commit 224ac9d2a030f85924e44a507ddc412797c3fe87)
(cherry picked from commit b9b571e6146a1b95ba18de065166a1a50eb88dfc)
|
|
page_pool headers were not used yet; they were created for mt76 but
are without functionality. Upstream has migrated them for v6.17 and
split them up into multiple files. Also add netmem.h which the little
needed is directly related to page pools.
(cherry picked from commit 7c31cdfa408a4ebce7a3e10d29056a15c28bc092)
(cherry picked from commit d388ff8016adf0f24b9b846941f1f15f5463c49e)
|
|
Given we do not yet support "wake" bits in device there is little need
doing it in PCI if we cannot check if we are supposed to do the
operation in first place. Once we would implement this, we would need
to also do the appropriate PCI (pme) checks before enabling (disabling)
it.
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D53208
(cherry picked from commit 885e8f272f7515b0325974de72d18b73318eff07)
(cherry picked from commit be52a81be07997f84f454637372a056415f6a2eb)
|
|
We do not currently aim to support crypto FIPS compliance in LinuxKPI
so keep this turned off.
Reviewed by: emaste, dumbbell
Differential Revision: https://reviews.freebsd.org/D53207
(cherry picked from commit 98609f4fecffd0e70293ddd57c2b785e498b1131)
(cherry picked from commit 3aaaba20786966062d1355d4809142b623ffc4b7)
|
|
The return type now is void; I believe no one ever used this
so we can just chnage it. The only active platform_driver_register()
calls seems to be in ath1[01]k and mt76 and there in unsupported code.
Reviewed by: dumbbell, emaste
Differential Revision: https://reviews.freebsd.org/D53205
(cherry picked from commit 0ae4998423e0d513fb88e404dfb1c2a285d11309)
(cherry picked from commit 5434a1635ed3fab8214f3fea8ada9772e4372372)
|
|
We will see how much we will need them and how to fill them at that
point. They are left with a pr_debug("TODO") for now.
Differential Revision: https://reviews.freebsd.org/D53204
(cherry picked from commit cc792250acadd29e80a69501ad326d1340c0c1c6)
(cherry picked from commit 805038b70a23f3f488ecba6e103f2aa1f9dad63c)
|
|
The former is needed by a wireless driver at v6.17.
Reviewed by: dumbbell, emaste
Differential Revision: https://reviews.freebsd.org/D53203
(cherry picked from commit 0a4b11ddb298fa08e1a81af7337995a3769552bf)
(cherry picked from commit 0e30cab0f32ee40e89f59b3a287ae96c084e1e7a)
|
|
igc(4) seems to work fine on arm64 for as much as I could test with
a 2.5Gbit/s interface on a mPCIe card.
Enable the module build so it is available.
(cherry picked from commit 51fbeadac4ccce6aafe51be9377d4114321295e5)
(cherry picked from commit 2c345e94ae0048ecec577ab52bc81510365038d0)
|
|
As found on RTEMS the argument to if_foreach_llmaddr() was wrong
causing crashes.
Fixes: 51e80820552e0
PR: 290314
(cherry picked from commit 33afdf0e356d84ffe5c62c886f84cf12ba147d3e)
(cherry picked from commit 10c71151ade7b5f021b49b7e117059730a2ddb56)
|
|
The port is called wifi-firmware-mt76-kmod not "mediatek" in the
moddle.
Reported by: Lars Tunkrans (drsnx60 gmail.com)
Reviewed by: emaste, jrm, imp
Differential Revision: https://reviews.freebsd.org/D53067
(cherry picked from commit 10d88a7aa670a3cc2bf763e64bd292b4caa3a811)
(cherry picked from commit e0487486279bc0690f65401622deebdbdea6a882)
|
|
MediaTek mt76 WiFi cards are advertising FLR support but after issuing
a FLR the chipset is gone. Add a quirk so we can disable FLR. The
current reset code will automatically fall back to a power reset.
This makes the card show up under bhyve where before it would just not
be discovered at all. That should make wifibox work for it and will help
development for a LinuxKPI based mt76 driver as found in framework laptops
as no dedicated machine and constant reboots are needed anymore.
We will likely need to add more PCI vendor/device IDs once we can test
the other device IDs.
After a lot of help from: jhb
Really implemented by: jhb (I just typed and tested)
GH issue: github.com/pgj/freebsd-wifibox/issues/73
Reviewed by: imp, emaste
Differential Revision: https://reviews.freebsd.org/D52728
(cherry picked from commit 4c0e53aced2251eb5ac7eca44e13a6b947be8582)
(cherry picked from commit 3bd015a1a918d060dbef556ddfa6e236f5212330)
|
|
Like lkpi_pci_get_domain_bus_and_slot() implement lkpi_pci_get_slot()
using pci_find_bsf() instead of pci_find_dbsf() (no domain).
This is needed for a wireless driver.
Unfortunately the name [pci_get_slot()] collides with the native PCI
function. Add a guard around it and disable the use when the native
version is required (in lkpifill_pci_dev() and in bnxt/bnxt_en; if the
latter gets fixed we can probably also fix work around it in the former;
further conflicts in drm-kmod 6.1-lts, 6.6-lts, and master were resolved).
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52065
(cherry picked from commit 4179e6b78297369f0cf0eae1076e01e5151c5cbe)
(cherry picked from commit 62c3b77d1d1084dc46663eed52e288307b5c7e64)
|
|
In linux_pci_attach_device() allocate a LinuxKPI pci_dev for each device in
the hierarchy up to the root port[1] as we cannot do that later on demand
as we may be in a context where we may not sleep.
Take special care of DRM as there is a non-PCI device in the chain which
needs to be skipped.
iwlwifi(4) can hit this case called from a callout.
While here leave a comment as the cleanup order of
linux_pci_attach_device() needs correction seperately.
Sponsored by: The FreeBSD Foundation (initially)
PR: 283027
PR: 289647
Suggested by: jhb [1]
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52069
(cherry picked from commit bbeeb585315645db20118ef349a4e3dc83b148cc)
(cherry picked from commit 3860afe99ec39b9942967941181f28f27f3fc548)
(cherry picked from commit 123c2dc6e15a62ceba3469caf0f1a6801214a7d3)
(cherry picked from commit d8972ad2f6e7113d779d4ec975ce32552030b2a3)
|
|
When freeing the last reference of the net80211 node the net80211
node_free() code may directly call into the crypto code to delete
the keys. While we still holding the wiphy lock this would lead to
a recursion on the non-recursive wiphy lock. Defer freeing the
reference until we are back under the net80211 com lock.
Reported by: Mark Phillips (mark freebsdfoundation.org) on 15.0-ALPHA1
(cherry picked from commit 3c38dce87ecd2c87744e4b7ff1904ee841f88a47)
(cherry picked from commit b0469fa7f10f9fe5510a5445f38d1bf0b832c1e7)
|
|
dem_kfree() is called from all over the place and should actually
do something; contrary to lkpi_devm_kmalloc_release() it can also
take a const void *. We have to __DECONST() that though as the
entire devres framework does otherwise not take a const argument.
This was discovered during the rtw89 update to 6.16.
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52082
(cherry picked from commit 4ab64e34911ab06e567caaf07ed18f7770a61cc8)
(cherry picked from commit f20a09e161f07874c3a01b1579e8a5d2356df8ce)
|
|
Needed by a wifi driver update.
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52080
(cherry picked from commit 2a44e10edb13e6b2be7fa2814b418a6959cb1171)
(cherry picked from commit 88122c8eb70d81decb7c6dd16e551c3df6ad3818)
|
|
These came up during a wifi driver update.
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52079
(cherry picked from commit 7c473933624f701263a83da526cac680b1ca69ed)
(cherry picked from commit 3753913c9e1c3375be29b8f4ab925b054fe1ac4b)
|
|
It seems overflow.h wsa imported directly from Linux in 3208d4ad2b8320a.
Update the file to the newer version as needed for wireless driver updates.
Sponsored by: The FreeBSD Foundation (initially)
Obtained from: git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
038d61fd642278 (tag: v6.16)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52078
(cherry picked from commit 70c508e691de1ed0f70b4a6f0773bfb5d627050d)
(cherry picked from commit cd2bd8bf672cd5925531b6440d57f1c48e025079)
|
|
Use __builtin_object_size() by default.
If __builtin_dynamic_object_size() is available use that instead.
I would hope that in a future version we can remove the conditional
checks but in order to be able to MFC this without checking all
compiler versions simply keep it this way for now.
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52077
(cherry picked from commit ff5bcb742899f8398ccb1b9e292b2e5aeeb7fedb)
(cherry picked from commit 310885b40ad256b054d65353c375b29700ee024c)
|
|
This adds guard support for non-real-types like rcu locking meaning
that we need to keep the lock state separately ourselves. _T is still
special and needs to be updated. Given it may not be used it needs
an __unused attribute (we are using the LinuxKPI __maybe_unused which
indeed is more expressive in this case).
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52076
(cherry picked from commit 3f48a0fe53ca7e001852f4a406c1bdfab1cd2f6d)
(cherry picked from commit 4d5a78c5f40aa2dfd672ccfa4a6fff93e216c32b)
|
|
A wifi driver update needs this.
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52075
(cherry picked from commit 39e9290d890b2aa07b68f2fe956b96e5df9a1da2)
(cherry picked from commit 830cc677d97eebd02ade8b33ec17de38f2705a73)
|
|
del_timer() got renamed to timer_delete() approximately in Linux 6.2
(similar for *_sync and likely others).
Keep the old functions as compat; unclear when we can gc them.
We should also re-define them with a linuxkpi_ prefix to avoid possible
conflicts in the future if we do a full pass over this at some point.
Sponsored by: The FreeBSD Foundation (intiially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52074
(cherry picked from commit 5cb64a1d3fe75526fb879ef4dce5860bbb4e4aea)
(cherry picked from commit 88198564dbd82a97d655e73459c03eccf7031331)
|
|
With Linux 6.16 from_timer() got renamed to timer_container_of(); add
the LINUXKPI_VERSION check with a default to the current version.
Update all in-tree consumers (apart from wireless drivers managed
otherwise).
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52073
(cherry picked from commit 81cb7c4c8e7bc4951c77fe64a63a847ed6abee38)
(cherry picked from commit 352be5b48ba8b3ec1e3e5dd0dbee4da8d1fa78b0)
|
|
The code introduced abs_diff() as migrated from drm to standard
linux headers. The LINUXKPI_VERSION check did not allow this to
be visible by default in-tree. Make sure the v6.6 check is optional.
drm-kmod always defines LINUXKPI_VERSION so this should be fine.
Sponsored by: The FreeBSD Foundation (initially)
Fixes: afc450fac9f04
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52071
(cherry picked from commit 736b16e88d2384f9dd0ec11c0492e825b8d42193)
(cherry picked from commit ab45c859374d750a6b68292cf40889b8ca5db04a)
|
|
This will be used for hooking suspend/resume in for LinuxKPI 802.11
based drivers.
Sponsored by: The FreeBSD Foundation (initially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52070
(cherry picked from commit 627234627b51c2f12c29d10617d7bbd18936ea55)
(cherry picked from commit 8fca57469f7c33367c5f32f738a8fa8af40b6dda)
|
|
Factor out the pci_request_region() implementation into an internal
function and make pci_request_region() a simple wrapperaround it.
Likewise implement pcim_request_all_regions() as a loop calling
pci_request_region() for each entry.
In two cases which we returned an error before (bar index is valid but
bar is not (no len), and neither IO nor MEM) we now reutrn success
(nothing to do for us). Otherwise callers, especially
pcim_request_all_regions() would error out for the wrong reasons.
This seems to also match the expected behaviour of pci_request_region().
Sponsored by: The FreeBSD Foundation (intially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52068
LinuxKPI: pci: undo the pci_resource_len() check in lkpi_pci_request_region()
Creating non-passthru SR-IOV interfaces on a mlx5en(4) failed.
The problem lies in the pci_resource_len() call but not that the BAR length
is tmeporary 0 but in that we call lkpi_pci_get_bar() with a true argument
which will create the BAR resource for us and report the approriate length
back. However, the later call to bus_alloc_resource_any() will then fail
given the resource already exists.
Restore the previous behaviour and let bus_alloc_resource_any() do the
work. Adjust the return values from -ENODEV to -EBUSY to match callers
expectations.
In linuxkpi_pcim_request_all_regions(), like in linuxkpi_pci_request_regions(),
filter out the -EBUSY errors as "not an error" and try the next bar.
This also seems to be consistent with the expectations of the callers.
PR: 290793
Reported by: David BOYER (jcduss13 gmail.com)
Tested on: mlx5en, iwlwifi, mt7921
Reviewed by: kib
Fixes: 7e21158d44cd "implement [linuxkpi_]pcim_request_all_regions()"
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D53902
(cherry picked from commit 7e21158d44cd46e720395604ca6f00f2fa36b20c)
(cherry picked from commit ff31767e530abb4a54131af199fed6ec946a5fa4)
(cherry picked from commit ed29ffd396e522a45ab1980c12a75b3409b51712)
(cherry picked from commit 2032abb31cbe067d41067a81e529d91f1bace4c9)
|
|
Like pci_iomap() add the devres version pcim_iomap() using the former
to get the resource.
Add a helper function to validate that the bar is within a valid range
and sprinkle that check also to other related functions.
Sponsored by: The FreeBSD Foundation (intially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52067
(cherry picked from commit 2f9064a5d2b50f292cc8699d2be5c66c317f1dc7)
(cherry picked from commit cfb8f4bf2c2b9cfc8d5ed5a19b98f4a19f023ba6)
|
|
Implement for_each_pci_dev() needed by a wireless driver update.
For that also improve pci_get_device() and add the functionality to
support the odev argument to start searching from that.
Sponsored by: The FreeBSD Foundation (intially)
Reviewed by: dumbbell
Differential Revision: https://reviews.freebsd.org/D52066
(cherry picked from commit 910cf345d0ee9a5d72856a1ba35382eb4f0db951)
(cherry picked from commit 68f8fa4ada24aaf53a2d463b53259439dfb32146)
|
|
A port using linux(kpi) header files but not using skbuffs is hitting
the case that it cannot find opt_wlan.h. Give up to the idea that
skbuff.h is only used by wireless drivers (or in-tree) and that
IEEE80211_DEBUG (via opt_lwan.h) could autmatically compile in debug
support.
It is likely time to add a LINUXKPI_DEBUG knob in the near future
(also for linuxkpi_debug or linuxkpi_debug_rcu).
PR: 289268
(cherry picked from commit bc222e96d135687aea4e67ee9b11fb9490f42546)
|
|
- one duplcate entry: 0x664*|0x664*) -> 0x664*|0x665*)
- one unneeded glob: 0x98e4*) -> 0x98e4)
- 0x15e7|0x1636|0x1638|0x164c) half of these are green-sardine; split
- a missing entry for skillfish2 : + 0x143f
Reviewed by: imp, manu
Differential Revision: https://reviews.freebsd.org/D52312
(cherry picked from commit 1d12658755930e20904d498398379cad0e4ae396)
|
|
Reviewed by: imp, manu
Differential Revision: https://reviews.freebsd.org/D52311
(cherry picked from commit 50cab1202d39e67cd38b395e3e08e140e7617d95)
|
|
During startup hccontrol reset needs to be run multiple times
for iwbt to work more reliably. Add a loop trying up to
three times.
Tested by: various (original version; I changed test to -eq)
Differential Revision: https://reviews.freebsd.org/D44861
Fix a redirect of stderr to stdout which is going to /dev/null.
A '&' got missing in the original rewrite from the review that
I took and committed. Seems no one had noticed during testing
or review. People may have ended up with a "/1" file in their
root file system.
Fixes: 40652f86b5ef
Reported by: Vladyslav Movchan (vladislav.movchan gmail.com)
(cherry picked from commit 40652f86b5ef17c9016a5eaf4bc89b2f324540e8)
(cherry picked from commit 78807c196c9481cdd88b5ce611b488903f52fbd0)
|