From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Port parameter negotiation?
Date: Mon, 29 Nov 2004 12:34:38 +0100 [thread overview]
Message-ID: <1101728078.7463.37.camel@pegasus> (raw)
In-Reply-To: <200411291226.52638.harbaum@beecon.de>
Hi Till,
> does BlueZ implement rfcomm port paramater negotiation? This is required to
> allow a bluetooth->rs232 converter so set the baud rate etc according to the
> settings on the hosts virtual serial port. E.g. changing the baudrate on a
> windows bluetooth com port changes the rs232 bit rate on the bt device as
> well (ok, at least my widcomm/win98 notebook does this only for 57600 and
> 115200 correctly).
>
> So using something like
> stty -F /dev/rfcomm0 speed 9600
>
> should IMHO cause a rfcomm port negotiation packet to be sent on client side.
> But i don't see this happen ...
as far as I remember we haven't fully implemented it. We only have code
to fulfill the Bluetooth qualification requirements. However the main
RFCOMM interface are sockets and there you don't have to worry about the
baud rate. Adding support for it should not be that hard. Find out what
IOCTL the command above triggers and prepare the correct negotiation
packet.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-29 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 11:26 [Bluez-devel] Port parameter negotiation? Till Harbaum
2004-11-29 11:34 ` Marcel Holtmann [this message]
2004-12-01 15:16 ` Till Harbaum
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=1101728078.7463.37.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@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