public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Roderick Taylor <rtaylor@hcvwireless.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO socket data transmission status
Date: Thu, 15 Jul 2004 13:00:15 +0200	[thread overview]
Message-ID: <1089889215.3569.30.camel@notepaq> (raw)
In-Reply-To: <opsa5i9odng1fi0r@trippin>

Hi Roderick,

> When you send to a SCO socket in BlueZ, is there a way to find out if the  
> bt device has transmitted the data you have written?  Do SCO sockets have  
> any interaction with the select function?
> 
> To me it seems that sending to a bluez SCO socket will work no matter  
> what.  If you send data to fast for the device to handle then, then the  
> data written will be ignored.

the SCO sockets are for audio only. You can expect that every packet is
transmitted and the Bluetooth chip may drop packets if you send to much
to it.

> Is this a question for bluez-users rather than bluez-devel?

It is correct at this place.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-07-15 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 23:52 [Bluez-devel] SCO socket data transmission status Roderick Taylor
2004-07-15 11:00 ` Marcel Holtmann [this message]

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=1089889215.3569.30.camel@notepaq \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=rtaylor@hcvwireless.com \
    /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