public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BNEP transferrate limitation?
Date: Thu, 19 Jul 2007 12:02:42 +0200	[thread overview]
Message-ID: <1184839362.6357.29.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <469E6A4A.4000804@krevsbech.dk>

Hi Kasper,

> Hey we are using BNEP as a part of our student project but we have 
> reached a limitation on the transfer speed of approx 8 KB/s. We have 
> tried to switch the hardware dongles but it is still the same. We have 
> another scheme where we use the L2CAP layer directly trough a socket 
> with the the BNEP profile. This gives the same limit. If we use the same 
> hardware dongles with a OBEX transfer we can reach much higher limitations.
> Therefore we would like to know if it is a known limitation on the BNEP 
> profile or if there is known limitations with some of the drivers.

there exists no such limitation. The BNEP support works perfectly fine
and you might have messed up the packet type settings. Don't modify
them, because BlueZ knows what to do.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-07-19 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 19:30 [Bluez-users] BNEP transferrate limitation? Kasper Revsbech
2007-07-19 10:02 ` 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=1184839362.6357.29.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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