public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: walt shekrota <penguinacity@yahoo.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] current Bluez document describing
Date: Wed, 28 Feb 2007 06:09:34 -0800 (PST)	[thread overview]
Message-ID: <75899.4133.qm@web62301.mail.re1.yahoo.com> (raw)
In-Reply-To: <52950c3f0702271456i50da8e9dj3f298ff62eb375dc@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1039 bytes --]



Timur Alperovich <timur.alperovich@gmail.com> wrote: Hi there,

When I was figuring out how to program some network apps over bluetooth the following guide seemed to be pretty helpful: http://people.csail.mit.edu/albert/bluez-intro/ 

Hope that helps,
Timur
   
 Thanks for that info!
   
   
 
   >No idea what's your question. Be more specific.
 
 Ok rfcomm is the transport protocol?
 In the conf file does the  'device' describe the otherside ie headset, phone etc?
 or is it the address of dongle?
 It says just 'device' as comment in rfcomm.conf!
 To use a headset with my computer and a bt dongle does it require this device be  
 defined in that file?
 
 

 The thing I found redundant and confusing is that when communicating with a remote bt like a headset the address is set both in rfcomm.conf and as arg to btsco? Is my understanding incorrect? I did not see clear description of rfcomm.conf anywhere.
 
 Thanks
 -Walt

 
---------------------------------
Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.

[-- Attachment #1.2: Type: text/html, Size: 1588 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-02-28 14:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 10:10 [Bluez-users] pairing from bluez Choi Sonim
2007-02-27 10:35 ` Peter Valdemar Mørch
2007-02-27 20:16   ` Choi Sonim
2007-02-27 20:50     ` [Bluez-users] current Bluez document describing walt shekrota
2007-02-27 22:56       ` Timur Alperovich
2007-02-28 14:09         ` walt shekrota [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-25 16:10 penguinacity
2007-02-25 23:47 ` 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=75899.4133.qm@web62301.mail.re1.yahoo.com \
    --to=penguinacity@yahoo.com \
    --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