src/sys/modules/netgraph/bluetooth, branch stable/13FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=stable%2F132023-08-23T17:43:27Zsys: Remove $FreeBSD$: one-line sh pattern2023-08-23T17:43:27ZWarner Loshimp@FreeBSD.org2023-08-22T01:31:56Zurn:sha1:5510f79042fbd543de55807d0da7f8a2b8be2f89
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Similar commit in current:
(cherry picked from commit 031beb4e239b)
Fix some modules to export more used symbols2021-11-25T01:09:21ZKonstantin Belousovkib@FreeBSD.org2021-11-07T08:42:24Zurn:sha1:83271c68c4f4697ba15d49cc3f31912a5d04ff4b
(cherry picked from commit 5bb3134a8c21cb87b30e135ef168483f0333dabb)
pccard: Remove bt3c(4) driver2021-01-08T03:40:41ZWarner Loshimp@FreeBSD.org2021-01-07T22:52:49Zurn:sha1:23e124c78bcb46ac78d9f06449c4454f43732805
pccard is being removed, so remove bt3c driver since it only has PC
Card attachment. Also remove bt3cfw(8) since it's the firmware for this
driver.
Relnotes: Yes
ng_ubt(4): do not attach Intel Wireless 8260/8265 in bootloader mode.2019-08-18T22:11:42ZVladimir Kondratyevwulf@FreeBSD.org2019-08-18T22:11:42Zurn:sha1:3544d43bb17f9f69f145bccb58ca9bf3dd5810b1
Add helper function for synchronous execution of HCI commands at probe
stage and use this function to check firmware state of Intel Wireless
8260/8265 bluetooth devices found in many post 2016 year laptops.
Attempt to initialize FreeBSD bluetooth stack while such a device is in
bootloader mode locks the adapter hardly so it requires power on/off
cycle to restore.
This change blocks ng_ubt attachment unless operational firmware is
loaded thus preventing the lock up.
PR: 237083
Reviewed by: hps, emax
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D21071
sys/modules: normalize .CURDIR-relative paths to SRCTOP2017-03-04T10:10:17ZEnji Cooperngie@FreeBSD.org2017-03-04T10:10:17Zurn:sha1:193d9e768ba63fcfb187cfd17f461f7d41345048
This simplifies make output/logic
Tested with: `cd sys/modules; make ALL_MODULES=` on amd64
MFC after: 1 month
Sponsored by: Dell EMC Isilon
Hook ubt and ubtbcmfw back up to the build.2009-05-27T16:43:40ZAndrew Thompsonthompsa@FreeBSD.org2009-05-27T16:43:40Zurn:sha1:06079f1405f9c7fb3daaa80f891e6088f9c4cd55Hook up new USB modules.2009-02-23T18:32:59ZAndrew Thompsonthompsa@FreeBSD.org2009-02-23T18:32:59Zurn:sha1:7d0d268b8a67f28ccefdd0b8ce6fb38acac78d80Disconnect drivers that haven't been ported to MPSAFE TTY yet.2008-08-03T10:32:17ZEd Schoutened@FreeBSD.org2008-08-03T10:32:17Zurn:sha1:200d80cd74a8cb0a58383d0cbef063f2575c9f53
As clearly mentioned on the mailing lists, there is a list of drivers
that have not been ported to the MPSAFE TTY layer yet. Remove them from
the kernel configuration files. This means people can now still use
these drivers if they explicitly put them in their kernel configuration
file, which is good.
People should keep in mind that after August 10, these drivers will not
work anymore. Even though owners of the hardware are capable of getting
these drivers working again, I will see if I can at least get them to a
compilable state (if time permits).
Hook up Bluetooth SCO sockets code to the build2008-07-30T22:42:17ZMaksim Yevmenkinemax@FreeBSD.org2008-07-30T22:42:17Zurn:sha1:ecfcbb9f0376351e59850d6a6e528e4dd026cefd
MFC after: 3 months
Make ng_h4(4) MPSAFE. Use similar to ng_tty(4) locking strategy.2007-08-13T17:19:28ZMaksim Yevmenkinemax@FreeBSD.org2007-08-13T17:19:28Zurn:sha1:51713b2a7b128056bae6793e3b10252c1a261d9a
Reconnect ng_h(4) back to the build.
Reviewed by: kensmith
Approved by: re (kensmith)
MFC after: 1 month