From: Mario Demontis <mario.demontis@email.it>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluetooth connection too slow
Date: Mon, 12 Dec 2005 22:59:04 +0100 [thread overview]
Message-ID: <1134424744.8666.10.camel@localhost.localdomain> (raw)
In-Reply-To: <1133029959.15981.0.camel@blade>
Hello Marcel
I made several efforts in order to try different combinations of ppp
parameters, but I didn't get any improvement: my ppp connection over
bluetooth is still 3 times slower than in windows :(
Now I'm trying to use different parameters for the terminal settings
(over rfcomm). Just a question:
If I set the speed of /dev/rfcomm0 to 1200 rather than 115200 or more,
how does the driver react? Does it ignore the setting? What about other
terminal settings (flow control, parity,...)
Thanks in advance
Mario
Il giorno sab, 26/11/2005 alle 19.32 +0100, Marcel Holtmann ha scritto:
> Hi Mario,
>
> > > If you reach 32 kB/s then this is a good result. With Bluetooth prior
> > > EDR you will reach max something around 80 kB/s, but this is not really
> > > doable with PPP in between. The bottleneck can also be the UART inside
> > > your mobile phone.
> >
> > That wouldn't explain the reason why under Windows I'm getting 32kB/s...
> > By the way, what I'm willing to do is just to have the same performance
> > under Linux
>
> try to tweak your PPP settings, because I don't think that RFCOMM is the
> bottleneck here. I could be, but I doubt it.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Cartucce, toner, ricariche...scegli a chi rivolgerti per la tua stampante. Clicca qui
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=4198&d=12-12
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-12-12 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 18:04 [Bluez-users] Bluetooth connection too slow Mario Demontis
2005-11-26 18:13 ` Marcel Holtmann
2005-11-26 18:27 ` Mario Demontis
2005-11-26 18:32 ` Marcel Holtmann
2005-12-12 21:59 ` Mario Demontis [this message]
2005-12-12 23:35 ` Marcel Holtmann
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=1134424744.8666.10.camel@localhost.localdomain \
--to=mario.demontis@email.it \
--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;
as well as URLs for NNTP newsgroup(s).