Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Torez Smith <torez@us.ibm.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] usb to serial verification
Date: Wed, 11 Feb 2004 00:49:56 +0100	[thread overview]
Message-ID: <1076456996.2777.55.camel@pegasus> (raw)
In-Reply-To: <OF5A385DC1.2BE48959-ON87256E36.007C6942-86256E36.007CBA73@us.ibm.com>

Hi Torez,

> The serial dongle is a BT125S dongle. It's connected to a com port on
> a
> linux box. Theoretically, I should be able to cat /dev/ttyS0 on that
> linux box
> to read the data coming across from the usb dongle. 

this was not my question. Maybe I should be more specific. Is this
serial dongle a simply host adapter or a full "cable replacement"
product?

> Do I still need to hciattach the serial dongle on the linux box? 

If it is a host adapter then you have to attach to your Bluetooth stack
and you must use RFCOMM on both sides.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

       reply	other threads:[~2004-02-10 23:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF5A385DC1.2BE48959-ON87256E36.007C6942-86256E36.007CBA73@us.ibm.com>
2004-02-10 23:49 ` Marcel Holtmann [this message]
2004-02-10 21:02 [Bluez-devel] usb to serial verification Torez Smith
2004-02-10 22:27 ` 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=1076456996.2777.55.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=torez@us.ibm.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