mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: davem@redhat.com
Cc: linux-kernel@vger.kernel.org, bluez-devel@lists.sourceforge.net
Subject: [BK] Bluetooth updates and fixes for 2.5
Date: Fri, 12 Sep 2003 09:54:29 -0700	[thread overview]
Message-ID: <5.1.0.14.2.20030912095050.06e091e0@unixmail.qualcomm.com> (raw)

Dave, 

We've got a bunch of Bluetooth updates for you to pull at
       bk://linux-bt.bkbits.net/bt-2.5

This will update the following files:

 CREDITS                           |    3 -
 MAINTAINERS                       |   52 ++++++++++++++++-
 drivers/bluetooth/hci_usb.c       |    3 -
 include/net/bluetooth/bluetooth.h |    2 
 include/net/bluetooth/hci.h       |    2 
 include/net/bluetooth/l2cap.h     |    2 
 net/bluetooth/af_bluetooth.c      |   22 +++----
 net/bluetooth/bnep/bnep.h         |    4 -
 net/bluetooth/bnep/core.c         |   36 +++++-------
 net/bluetooth/bnep/netdev.c       |    7 --
 net/bluetooth/hci_core.c          |    9 ++-
 net/bluetooth/hci_event.c         |   13 ++++
 net/bluetooth/hci_sock.c          |    2 
 net/bluetooth/l2cap.c             |   74 ++++++++++++++++--------
 net/bluetooth/rfcomm/core.c       |  102 +++++++++++++++++++++++++++++-----
 net/bluetooth/rfcomm/sock.c       |   75 +++++++++++++------------
 net/bluetooth/rfcomm/tty.c        |  113 ++++++++++++++++++--------------------
 net/bluetooth/sco.c               |   21 +++++--
 net/bluetooth/syms.c              |    2 
 19 files changed, 359 insertions(+), 185 deletions(-)

through these ChangeSets:

<maxk@qualcomm.com> (03/09/11 1.1153.66.2)
   [Bluetooth] Convert BNEP protocol to dynamic allocation of network devices.
   This will allow fixing races with rmmod and sysfs access.
   
   Patch from Stephen Hemminger <shemminger@osdl.org>

<maxk@qualcomm.com> (03/08/20 1.1153.33.2)
   [Bluetooth] L2CAP qualification spec mandates sending additional config request 
   if we receive config response with unacceptable parameters error code. 
   So we now send dummy request to keep tester happy.

<marcel@holtmann.org> (03/07/22 1.1046.306.9)
   [Bluetooth] Add support for FCon and FCoff flow control commands
   
   This patch adds flow control support using FCon and FCoff commands
   to fulfil the requirements of the Bluetooth specification.

<marcel@holtmann.org> (03/07/18 1.1046.306.8)
   [Bluetooth] Add tiocmget() and tiocmset() routines to RFCOMM TTY
   
   This patch adds the routines tiocmget() and tiocmset() to the
   RFCOMM TTY layer for setting and retrieving the modem status.

<marcel@holtmann.org> (03/07/14 1.1046.306.7)
   [Bluetooth] Update the maintainer entries for the Bluetooth subsystem
   
   This patch puts a little bit more detailed information about the
   maintainers of the Bluetooth subsystem into the MAINTAINERS file.

<marcel@holtmann.org> (03/07/14 1.1046.306.6)
   [Bluetooth] Handle command complete event for inquiry cancel
   
   The command complete event of the inquiry cancel command must
   clear the HCI_INQUIRY flag and finish the HCI request.

<marcel@holtmann.org> (03/07/03 1.1046.306.5)
   [Bluetooth] Support for inquiry with unlimited responses
   
   This patch handles the special case if the number of responses
   is set to zero, which means unlimited responses.

<marcel@holtmann.org> (03/06/27 1.1046.306.4)
   [Bluetooth] Make READ_TRANSMIT_POWER_LEVEL available for normal users
   
   This makes the HCI command READ_TRANSMIT_POWER_LEVEL available for
   normal users.

<marcel@holtmann.org> (03/06/19 1.1046.306.3)
   [Bluetooth] Quirk for devices with no ISOC endpoints
   
   This patch checks the existence of ISOC endpoints before it
   starts the URB for them.

<maxk@qualcomm.com> (03/06/16 1.1046.306.2)
   [Bluetooth] Add support for SO_LINGER to L2CAP, RFCOMM and SCO sockets.
   This is required to pass qualification testing.

<maxk@qualcomm.com> (03/06/11 1.1046.271.3)
   [Bluetooth] Fix RFCOMM C/R and Direction bits handling.
   MCC C/R bit does not depend on connection state.
   Direction bit must be set for DLCs located on the initiator.

<maxk@qualcomm.com> (03/06/11 1.1046.270.1)
   Bluetooth: RFCOMM must send MSC when DLC was opened by SABM 

<marcel@holtmann.org> (03/05/29 1.1046.53.4)
   [Bluetooth] Handle bit rate in remote port negotiation
   
   This patch adds handling of the bit rate to rfcomm_recv_rpn().

<marcel@holtmann.org> (03/05/29 1.1046.53.3)
   [Bluetooth] Set EA bit for V.24 signals parameter
   
   This patch always sets the EA bit along with the V.24 signals
   value in rfcomm_send_msc().

<marcel@holtmann.org> (03/05/28 1.1046.53.2)
   [Bluetooth] Send correct RPN response for accepted values
   
   This patch fixes another bug in rfcomm_recv_rpn(), which do
   not respond with the correct values for accepted settings.


Max

http://bluez.sf.net
http://vacum.sf.net
http://vtun.sf.net


             reply	other threads:[~2003-09-12 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 16:54 Max Krasnyansky [this message]
2003-09-13  0:12 ` David S. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.2.20030912095050.06e091e0@unixmail.qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®