From: Arun Kumar <arunkat@gmail.com>
To: Mumia W <mumia.w.18.spam@earthlink.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Need complete docs on PAN and DUN with bluez 4.66
Date: Tue, 21 Sep 2010 09:26:19 +0530 [thread overview]
Message-ID: <AANLkTi=gRJgyFD2uC-UsjzjQCU11326SSsN4+nsTxk9-@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=hD_U-19oPnQzQemt5wBgAqip3h7esJZpgkr4e@mail.gmail.com>
Depends on what role you want to use pand for ...pand is launched as a
daemon via command line with set of options you may want to use it for
your requirements ...
...
Best Regards,
Arun Kumar Singh
www.crazydaks.com
> On Tue, Sep 21, 2010 at 6:20 AM, Mumia W <mumia.w.18.spam@earthlink.net> wrote:
>>>From: Mumia W <mumia.w.18.spam@earthlink.net>
>>>Sent: Sep 19, 2010 4:49 PM
>>>To: linux-bluetooth@vger.kernel.org
>>>Subject: Need complete docs on PAN and DUN with bluez 4.66
>>>
>>>Where is the documentation on how to use PAN and DUN
>>>with bluez 4.66 (without using the legacy drivers)?
>>>
>>>
>>
>> Evidently the documents do not exist.
>>
>> Does anyone have any advice on how I use PAN with bluez 4.66?
>>
>>
>> --
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
>
> --
>
--
Best Regards,
Arun Kumar Singh
www.crazydaks.com
next prev parent reply other threads:[~2010-09-21 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 0:50 Need complete docs on PAN and DUN with bluez 4.66 Mumia W
[not found] ` <AANLkTi=hD_U-19oPnQzQemt5wBgAqip3h7esJZpgkr4e@mail.gmail.com>
2010-09-21 3:56 ` Arun Kumar [this message]
2010-09-21 11:06 ` Luiz Augusto von Dentz
2010-09-21 18:16 ` Arun Kumar
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 20:21 Mumia W
2010-09-21 20:16 Mumia W
2010-09-19 21:49 Mumia W
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='AANLkTi=gRJgyFD2uC-UsjzjQCU11326SSsN4+nsTxk9-@mail.gmail.com' \
--to=arunkat@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mumia.w.18.spam@earthlink.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).