public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Matthew Reimer <mreimer@vpop.net>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] How to configure a 723kbps connection?
Date: Wed, 25 Feb 2004 15:03:10 +0000	[thread overview]
Message-ID: <403CB92E.1000009@grupopie.com> (raw)
In-Reply-To: 403AC9D1.1000902@vpop.net

Matthew Reimer wrote:

> 
> I tried setting the divisor to 1 manually, but then bluetooth wouldn't 
> work. Maybe PPC2003 isn't fast enough to handle interrupts at that rate?
> 

That wouldn't work because the zeevo chip would also have to be configured for 
921.6kbps. AFAIK only modems try hard to autodetected baudrate from the "at" 
command string.

There is probably a good reason for the HP guys to set up the port like that. If 
it would work at 921.6kbps they would probably use the extra bandwidth. This is 
really a shame, because I was thinking of buying a 2215 myself, but I would like 
to have a "full-speed" bluetooth (and Linux support) :(

-- 
Paulo Marques
Software Development Department - Restinfor, Lda.
Phone: +351 252 290600, Fax: +351 252 290601
Web: www.grupopie.com

"In a world without walls and fences who needs windows and gates?"



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-02-25 15:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lists.bluez.users.1077037423.2665.72.camel@pegasus.SOMEWHERE>
     [not found] ` <lists.bluez.users.403291AD.7080601@csr.com>
2004-02-17 23:09   ` [Bluez-users] How to configure a 723kbps connection? Matthew Reimer
2004-02-17 23:36     ` Marcel Holtmann
2004-02-18  3:51       ` Matthew Reimer
2004-02-24  3:49   ` Matthew Reimer
2004-02-25 15:03     ` Paulo Marques [this message]
     [not found] <lists.bluez.users.1077061006.2665.141.camel@pegasus.SOMEWHERE>
     [not found] ` <lists.bluez.users.4032E137.7080902@vpop.net>
2004-02-18  3:56   ` Matthew Reimer
     [not found] <lists.bluez.users.40327430.2090807@grupopie.com>
2004-02-17 20:45 ` Matthew Reimer
     [not found] <200402160913.i1G9DCP02222@webserver.restinfor.pt>
2004-02-17 20:06 ` Paulo Marques
     [not found] <lists.bluez.users.40323EC2.8080203@csr.com>
2004-02-17 10:50 ` grpmind+bluez.users
2004-02-17 18:58   ` Marcel Holtmann
2004-02-17  6:36 grpmind+bluez.users
2004-02-17 15:37 ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-02-17  3:42 grpmind+bluez.users
2004-02-17 11:52 ` Marcel Holtmann
2004-02-17 16:18   ` Steven Singer
2004-02-17 17:03     ` Marcel Holtmann
2004-02-17 22:11       ` Steven Singer
2004-02-17 22:51         ` Marcel Holtmann
2004-02-14 17:06 grpmind+bluez.users
2004-02-15 14:33 ` Marcel Holtmann
2004-02-16 22:20   ` Michel Planques
2004-02-16 22:58     ` 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=403CB92E.1000009@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=mreimer@vpop.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