summaryrefslogtreecommitdiffstats
path: root/sys/netgraph/bluetooth
Commit message (Collapse)AuthorAgeFilesLines
* Add support for the BCM20702A0 chipset, ASUS USB-BT400.eadler2013-09-011-0/+1
| | | | | PR: kern/181728 Submitted by: rakuco
* Sync USB bluetooth product list with Linux.hselasky2013-08-311-0/+60
| | | | MFC after: 1 week
* PR: kern/168520rodrigc2013-07-151-9/+1
| | | | Revert GRN 253255. It is not needed now that GRN 253346 is committed.
* PR: 168520 170096rodrigc2013-07-151-1/+3
| | | | | | | | | | | | | | | | | | | | Submitted by: adrian, zec Fix multiple kernel panics when VIMAGE is enabled in the kernel. These fixes are based on patches submitted by Adrian Chadd and Marko Zec. (1) Set curthread->td_vnet to vnet0 in device_probe_and_attach() just before calling device_attach(). This fixes multiple VIMAGE related kernel panics when trying to attach Bluetooth or USB Ethernet devices because curthread->td_vnet is NULL. (2) Set curthread->td_vnet in if_detach(). This fixes kernel panics when detaching networking interfaces, especially USB Ethernet devices. (3) Use VNET_DOMAIN_SET() in ng_btsocket.c (4) In ng_unref_node() set curthread->td_vnet. This fixes kernel panics when detaching Netgraph nodes.
* PR: kern/168520rodrigc2013-07-121-1/+9
| | | | | | | | | | | | | | | Submitted by: "YAMAMOTO, Shigeru" <shigeru@iij.ad.jp> Reviewed by: adrian In PC-BSD 9.1, VIMAGE is enabled in the kernel config. For laptops with Bluetooth capability, such as the HP Elitebook 8460p, the kernel will panic upon bootup, because curthread->td_vnet is not initialized. Properly initialize curthread->td_vnet when initializing the Bluetooth stack. This allows laptops such as the HP Elitebook 8460p laptop to properly boot with VIMAGE kernels.
* Fix several typoseadler2013-05-121-1/+1
| | | | | | PR: kern/176054 Submitted by: Christoph Mallon <christoph.mallon@gmx.de> MFC after: 3 days
* Fxi a bunch of typos.eadler2013-05-101-1/+1
| | | | | PR: misc/174625 Submitted by: Jeremy Chadwick <jdc@koitsu.org>
* Add blacklist entries for Atheros bluetooth device IDs that are known toadrian2013-04-051-0/+33
| | | | | | | | need firmware before they will re-attach as correctly functioning bluetooth devices. Reviewed by: maksim Obtained from: Linux ath3k device driver
* Use DEVMETHOD_END, as suggested by hselasky@.rakuco2012-12-261-1/+1
| | | | Approved by: glebius
* Use the correct USB interface macros instead of USB_IF_CSI.rakuco2012-12-261-1/+3
| | | | | | | | | | | | As pointed out by hselasky@, USB_IF_CSI is the wrong macro here since we want to declare the device's interface class, subclass and protocol, not class, subclass and driver info. Follow-up to r244704. PR: kern/174707 Approved by: glebius MFC after: 1 week
* Add vendor IDs for Broadcom USB dongles (BCM20702).glebius2012-12-261-0/+4
| | | | | PR: kern/174707 Submitted by: rakuco
* Mechanically substitute flags from historic mbuf allocator withglebius2012-12-0515-46/+46
| | | | | | | | | malloc(9) flags within sys. Exceptions: - sys/contrib not touched - sys/mbuf.h edited manually
* The USB Bluetooth driver should only grab its own interfaces. This allows thehselasky2012-09-301-4/+16
| | | | | | | USB bluetooth driver to co-exist with other USB device classes and drivers. Reported by: Geoffrey Levand MFC after: 1 week
* Fix compiler warnings, mostly signed issues,hselasky2012-04-021-6/+6
| | | | | | when USB modules are compiled with WARNS=9. MFC after: 1 weeks
* Mark all SYSCTL_NODEs static that have no corresponding SYSCTL_DECLs.ed2011-11-075-5/+5
| | | | | | The SYSCTL_NODE macro defines a list that stores all child-elements of that node. If there's no SYSCTL_DECL macro anywhere else, there's no reason why it shouldn't be static.
* Mark MALLOC_DEFINEs static that have no corresponding MALLOC_DECLAREs.ed2011-11-075-6/+6
| | | | This means that their use is restricted to a single C file.
* - Move all USB device ID arrays into so-called sections,hselasky2011-06-242-3/+3
| | | | | | | | | | | | sorted according to the mode which they support: host, device or dual mode - Add generic tool to extract these data: tools/bus_autoconf Discussed with: imp Suggested by: Robert Millan <rmh@debian.org> PR: misc/157903 MFC after: 14 days
* usb: fix a missed use of use_generic in r222051avg2011-05-181-4/+5
| | | | | | | Submitted by: gcooper Pointyhat to: avg MFC after: 1 month X-MFC with: r222051
* Node constructor methods are supposed to be called in syscallglebius2011-04-182-8/+2
| | | | | | | context always. Convert nodes to consistently use M_WAITOK flag for memory allocation. Reviewed by: julian
* Fix typos - remove duplicate "the".brucec2011-02-211-1/+1
| | | | | | PR: bin/154928 Submitted by: Eitan Adler <lists at eitanadler.com> MFC after: 3 days
* Mfp4 CH=177274,177280,177284-177285,177297,177324-177325bz2011-02-163-3/+21
| | | | | | | | | | | | | | | | | | | | | | VNET socket push back: try to minimize the number of places where we have to switch vnets and narrow down the time we stay switched. Add assertions to the socket code to catch possibly unset vnets as seen in r204147. While this reduces the number of vnet recursion in some places like NFS, POSIX local sockets and some netgraph, .. recursions are impossible to fix. The current expectations are documented at the beginning of uipc_socket.c along with the other information there. Sponsored by: The FreeBSD Foundation Sponsored by: CK Software GmbH Reviewed by: jhb Tested by: zec Tested by: Mikolaj Golub (to.my.trociny gmail.com) MFC after: 2 weeks
* sysctl(9) cleanup checkpoint: amd64 GENERIC builds cleanly.mdf2011-01-126-21/+21
| | | | Commit the netgraph piece.
* Remove unneeded includes of <sys/linker_set.h>. Other headers that usejhb2011-01-112-2/+0
| | | | | | it internally contain nested includes. Reviewed by: bde
* Fix typoemax2010-08-021-1/+1
| | | | | PR: kern/140590 MFC after: 3 days
* Get those pesky RFCOMM RPM data bits right. This is likely a noop.emax2009-09-101-2/+2
| | | | MFC after: 1 month
* Introduce and use a sysinit-based initialization scheme for virtualrwatson2009-07-231-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | network stacks, VNET_SYSINIT: - Add VNET_SYSINIT and VNET_SYSUNINIT macros to declare events that will occur each time a network stack is instantiated and destroyed. In the !VIMAGE case, these are simply mapped into regular SYSINIT/SYSUNINIT. For the VIMAGE case, we instead use SYSINIT's to track their order and properties on registration, using them for each vnet when created/ destroyed, or immediately on module load for already-started vnets. - Remove vnet_modinfo mechanism that existed to serve this purpose previously, as well as its dependency scheme: we now just use the SYSINIT ordering scheme. - Implement VNET_DOMAIN_SET() to allow protocol domains to declare that they want init functions to be called for each virtual network stack rather than just once at boot, compiling down to DOMAIN_SET() in the non-VIMAGE case. - Walk all virtualized kernel subsystems and make use of these instead of modinfo or DOMAIN_SET() for init/uninit events. In some cases, convert modular components from using modevent to using sysinit (where appropriate). In some cases, do minor rejuggling of SYSINIT ordering to make room for or better manage events. Portions submitted by: jhb (VNET_SYSINIT), bz (cleanup) Discussed with: jhb, bz, julian, zec Reviewed by: bz Approved by: re (VIMAGE blanket)
* Fix a typeo in the frame len function to unbreak the build, make it shorterthompsa2009-06-231-2/+2
| | | | while I am here.
* - Make struct usb_xfer opaque so that drivers can not access the internalsthompsa2009-06-232-106/+172
| | | | - Reduce the number of headers needed for a usb driver, the common case is just usb.h and usbdi.h
* s/usb2_/usb_|usbd_/ on all function names for the USB stack.thompsa2009-06-152-52/+52
|
* Rework socket upcalls to close some races with setup/teardown of upcalls.jhb2009-06-011-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Each socket upcall is now invoked with the appropriate socket buffer locked. It is not permissible to call soisconnected() with this lock held; however, so socket upcalls now return an integer value. The two possible values are SU_OK and SU_ISCONNECTED. If an upcall returns SU_ISCONNECTED, then the soisconnected() will be invoked on the socket after the socket buffer lock is dropped. - A new API is provided for setting and clearing socket upcalls. The API consists of soupcall_set() and soupcall_clear(). - To simplify locking, each socket buffer now has a separate upcall. - When a socket upcall returns SU_ISCONNECTED, the upcall is cleared from the receive socket buffer automatically. Note that a SO_SND upcall should never return SU_ISCONNECTED. - All this means that accept filters should now return SU_ISCONNECTED instead of calling soisconnected() directly. They also no longer need to explicitly clear the upcall on the new socket. - The HTTP accept filter still uses soupcall_set() to manage its internal state machine, but other accept filters no longer have any explicit knowlege of socket upcall internals aside from their return value. - The various RPC client upcalls currently drop the socket buffer lock while invoking soreceive() as a temporary band-aid. The plan for the future is to add a new flag to allow soreceive() to be called with the socket buffer locked. - The AIO callback for socket I/O is now also invoked with the socket buffer locked. Previously sowakeup() would drop the socket buffer lock only to call aio_swake() which immediately re-acquired the socket buffer lock for the duration of the function call. Discussed with: rwatson, rmacklem
* s/usb2_/usb_/ on all typedefs for the USB stack.thompsa2009-05-292-16/+16
|
* s/usb2_/usb_/ on all C structs for the USB stack.thompsa2009-05-283-42/+42
|
* Hook ubt and ubtbcmfw back up to the build.thompsa2009-05-271-2/+1
|
* move ng_ubt_var.h back to its original placethompsa2009-05-271-0/+131
|
* move ng_ubt.c back to its original placethompsa2009-05-271-0/+1722
|
* move ubtbcmfw.c back to its original placethompsa2009-05-271-0/+427
|
* Delete the bluetooth drivers for the old usb stack.thompsa2009-05-274-3091/+0
|
* Switch ubtbcmfw(4) to use si_drv1 instead of storing the unit number.ed2009-04-171-39/+21
| | | | | | The unit number is still used to store the type of the device node. Approved by: emax
* Update comment. soalloc() is no longer performing M_WAITOK memory allocations.emax2009-02-101-14/+6
| | | | | Submitted by: ru MFC after: 3 days
* Allow unprivileged users to run l2ping(8).emax2009-02-041-5/+0
| | | | MFC after: 1 month
* Properly return error code to the caller. This should fix the followingemax2009-01-191-20/+26
| | | | | | | | | | panic in ng_l2cap(4). panic: ng_l2cap_l2ca_con_req: ubt0l2cap - could not find connection! While i'm here get rid of few goto's. MFC after: 1 week
* Change message severity level from WARN to INFO. This should reduceemax2008-12-241-1/+1
| | | | | | amount of messages sent to syslog MFC after: 1 week
* Fix a number of style issues in the MALLOC / FREE commit. I've tried todes2008-10-231-1/+1
| | | | | be careful not to fix anything that was already broken; the NFSv4 code is particularly bad in this respect.
* Retire the MALLOC and FREE macros. They are an abomination unto style(9).des2008-10-2311-46/+41
| | | | MFC after: 3 months
* Abort transfers on all pipes before closing them. This fixes the crashemax2008-10-031-0/+5
| | | | | | | when Bluetooth USB device is pulled out without stopping the stack first. Submitted by: Vladimir Grebenschikov vova at fbsd dot ru MFC after: 1 week
* Replace all calls to minor() with dev2unit().ed2008-09-271-2/+2
| | | | | | | | | | | | | | | After I removed all the unit2minor()/minor2unit() calls from the kernel yesterday, I realised calling minor() everywhere is quite confusing. Character devices now only have the ability to store a unit number, not a minor number. Remove the confusion by using dev2unit() everywhere. This commit could also be considered as a bug fix. A lot of drivers call minor(), while they should actually be calling dev2unit(). In -CURRENT this isn't a problem, but it turns out we never had any problem reports related to that issue in the past. I suspect not many people connect more than 256 pieces of the same hardware. Reviewed by: kib
* Implement ratelimiting for debug messages. For now, allow at mostemax2008-08-015-20/+50
| | | | | | | one message per second. In the future might add a sysctl knob for each socket family to fine tune this. MFC after: 1 week
* Increase maximum input queue size limit for raw Bluetooth HCI sockets.emax2008-08-011-2/+1
| | | | MFC after: 3 days
* Fix locking bug, i.e. lock "wildcard" matched pcb before return.emax2008-08-011-0/+3
|
* Introduce support for Bluetooth SCO sockets. This is based on olderemax2008-07-303-1/+2132
| | | | | | code that was revisted. MFC after: 3 months
OpenPOWER on IntegriCloud