summaryrefslogtreecommitdiffstats
path: root/usr.bin/bluetooth
Commit message (Collapse)AuthorAgeFilesLines
* MFC r313656:ngie2017-02-211-1/+1
| | | | Use SRCTOP to define .include with usr.bin/Makefile.inc
* Update dependencies after r291406 added libelf to libkvm.bdrewery2015-12-011-0/+1
| | | | | | | | Unfortunately filemon/meta mode tracks all indirect dependencies here since ld(1) is reading libelf when linking in libkvm. Churn would be reduced if this was able to be limited to direct dependencies. Sponsored by: EMC / Isilon Storage Division
* Drop group privileges after opening the kvm descriptor, otherwise, the codedelphij2015-09-011-10/+4
| | | | | | | | | would not drop privileges as expected. While there also add checks for the drop and bail out immediately if we failed. MFC after: 3 days
* Add META_MODE support.sjg2015-06-133-0/+60
|\ | | | | | | | | | | | | | | | | | | | | Off by default, build behaves normally. WITH_META_MODE we get auto objdir creation, the ability to start build from anywhere in the tree. Still need to add real targets under targets/ to build packages. Differential Revision: D2796 Reviewed by: brooks imp
| * dirdeps.mk now sets DEP_RELDIRsjg2015-06-083-6/+0
| |
| * Merge sync of headsjg2015-05-277-16/+15
| |\ | |/ |/|
| * Updated/new dependenciessjg2014-11-191-0/+1
| |
| * Merge from head@274682sjg2014-11-193-89/+44
| |\
| * \ Merge head from 7/28sjg2014-08-193-3/+3
| |\ \
| * | | Updated dependenciessjg2014-05-163-3/+0
| | | |
| * | | Updated dependenciessjg2014-05-103-0/+6
| | | |
| * | | Updated dependenciessjg2013-03-113-0/+3
| | | |
| * | | Updated dependenciessjg2013-02-163-6/+0
| | | |
| * | | Sync FreeBSD's bmake branch with Juniper's internal bmake branch.marcel2012-08-223-0/+62
| | | | | | | | | | | | | | | | Requested by: Simon Gerraty <sjg@juniper.net>
* | | | Check l2cap socket initialisation and define L2CAP_SOCKET_CHECKEDtakawata2015-04-074-1/+4
| | | | | | | | | | | | | | | | This will fix build.
* | | | Stop including if_var.h from userland.glebius2015-04-061-1/+0
| | | | | | | | | | | | | | | | Sponsored by: Nginx, Inc.
* | | | Merge from projects/sendfile:glebius2014-11-301-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | o Introduce a notion of "not ready" mbufs in socket buffers. These mbufs are now being populated by some I/O in background and are referenced outside. This forces following implications: - An mbuf which is "not ready" can't be taken out of the buffer. - An mbuf that is behind a "not ready" in the queue neither. - If sockbet buffer is flushed, then "not ready" mbufs shouln't be freed. o In struct sockbuf the sb_cc field is split into sb_ccc and sb_acc. The sb_ccc stands for ""claimed character count", or "committed character count". And the sb_acc is "available character count". Consumers of socket buffer API shouldn't already access them directly, but use sbused() and sbavail() respectively. o Not ready mbufs are marked with M_NOTREADY, and ready but blocked ones with M_BLOCKED. o New field sb_fnrdy points to the first not ready mbuf, to avoid linear search. o New function sbready() is provided to activate certain amount of mbufs in a socket buffer. A special note on SCTP: SCTP has its own sockbufs. Unfortunately, FreeBSD stack doesn't yet allow protocol specific sockbufs. Thus, SCTP does some hacks to make itself compatible with FreeBSD: it manages sockbufs on its own, but keeps sb_cc updated to inform the stack of amount of data in them. The new notion of "not ready" data isn't supported by SCTP. Instead, only a mechanical substitute is done: s/sb_cc/sb_ccc/. A proper solution would be to take away struct sockbuf from struct socket and allow protocols to implement their own socket buffers, like SCTP already does. This was discussed with rrs@. Sponsored by: Netflix Sponsored by: Nginx, Inc.
* | | | Convert to usr.bin/ to LIBADDbapt2014-11-253-6/+3
| |_|/ |/| | | | | | | | Reduce overlinking
* | | Change the code to use the openpty(3) API which uses the pts(4) driveremax2014-10-233-89/+44
| |/ |/| | | | | | | | | | | | | instead of the pty(4) driver. PR: 184597 Submitted by: tobias.rehbein MFC after: 2 weeks
* | use .Mt to mark up email addresses consistently (part3)bapt2014-06-233-3/+3
|/ | | | | PR: 191174 Submitted by: Franco Fichtner <franco at lastsummer.de>
* Build usr.bin/ with WARNS=6 by default.ed2010-01-021-1/+0
| | | | Also add some missing $FreeBSD$ to keep svn happy.
* Clenup code a bit and do not call fork(2) before dameon(3) where not needed.emax2009-02-041-16/+2
| | | | MFC after: 1 month
* Fix buildemax2008-07-291-0/+1
|
* Make -t <tty> optional in server mode. If not specified use stdin/stdout.emax2008-05-142-24/+34
| | | | | | | | | | | Document this. Do not require channel number in server mode. If not specified - bind to ''wildcard'' channel zero. Real channel number will be obtained automatically and registered with local sdpd(8). While I'm here fix serial port service registration. Submitted by: luigi Tested by: Helge Oldach <freebsd-bluetooth at oldach dot net> MFC after: 3 days
* Check return value of listen().kevlo2007-09-111-1/+2
| | | | | Reviewed by: emax Approved by: re (kensmith)
* Add "server mode" to rfcomm_sppd(1).emax2007-01-252-40/+153
| | | | | Submitted by: Dave Eckhardt, bms Tested by: Dave Eckhardt, Eric Anderson, bms
* Teach rfcomm_sppd(8) to recognize "lan" (for LAN Access Using PPP) serviceemax2005-12-072-1/+7
| | | | | | name in '-c' (RFCOMM channel) option. MFC after: 3 days
* Teach rfcomm_sppd(1) about service names, so it is possible to specifyemax2005-11-232-8/+39
| | | | | | | service name instead of channel number with -c command option. Supported service names are: DUN (Dial-Up Networking), FAX (Fax) and SP (Serial Port). MFC after: 1 week
* Let bsd.prog.mk set SRCS and MAN to their default values.ru2005-01-283-5/+0
|
* Sort sections.ru2005-01-182-14/+14
|
* Added the EXIT STATUS section where appropriate.ru2005-01-173-3/+3
|
* Make -t <tty> optional. If not specified use stdin/stdout.emax2004-09-302-14/+35
| | | | | | | | | | | Document this. These changes make it possible to write something like set device "!/usr/bin/rfcomm_sppd -a BD_ADDR" inside the /etc/ppp/ppp.conf file. Very convenient for the users :) Submitted by: Konstantin Stepanenkov <kstepanenkov AT oilspace DOT com> MFC after: 3 days
* - One can use both BD_ADDR or name to specify address of the Bluetooth device.emax2004-08-052-7/+13
| | | | | | | | Update man pages to document this fact. - Update usage messages - Change u_intXXX to uintXXX
* Clean up language and markup.ru2004-05-191-37/+41
|
* Bumped document date.ru2004-05-191-2/+3
| | | | Removed hard sentence break.
* Use uint instead of u_intemax2004-04-091-10/+10
|
* Make sure Bluetooth stuff can be compiled on amd64emax2004-04-091-16/+16
| | | | Submitted by: ps
* Fix a couple of stylistic issuesemax2003-12-221-2/+2
| | | | | Reviewed by: imp (mentor), ru Approved by: imp (mentor)
* Fix uncontrolled access to the buffer in rfcomm_sppd(1).emax2003-12-191-4/+21
| | | | | | | | Fix typo in hcsecd(8) man page. Submitted by: Guido Falsi <mad@madpilot.net> Reviewed by: imp (mentor) Approved by: imp (mentor)
* Include <nlist.h> for nlist-related declarations instead of depending onbde2003-10-131-0/+1
| | | | namespace pollution in <kvm.h>.
* Update Bluetooth code.emax2003-10-1212-128/+650
| | | | | Reviewed by: M. Warner Losh <imp@bsdimp.com>; John Hay <jhay@freebsd.org> Approved by: M. Warner Losh <imp@bsdimp.com> (mentor)
* Reapply mdoc(7) fixes that got accidentally lost in the lastru2003-05-202-55/+62
| | | | | | | Bluetooth update, and fix a few more issues. Submitted by: Maksim Yevmenkin <m_evmenkin@yahoo.com>, ru Approved by: re (blanket)
* Part one of undating the bluetooth code to the newest versionjulian2003-05-107-31/+716
| | | | | Submitted by: Maksim Yevmenkin <m_evmenkin@yahoo.com> Approved by: re@
* mdoc(7) police: markup fixes.ru2002-12-121-16/+18
| | | | Approved by: re
* The second try a committing the bluetooth codejulian2002-11-204-0/+579
Has been seen to work on several cards and communicating with several mobile phones to use them as modems etc. We are still talking with 3com to try get them to allow us to include the firmware for their pccard in the driver but the driver is here.. In the mean time it can be downloaded from the 3com website and loaded using the utility bt3cfw(8) (supplied) (instructions in the man page) Not yet linked to the build Submitted by: Maksim Yevmenkin <myevmenk@exodus.net> Approved by: re
OpenPOWER on IntegriCloud