From: Marcel Holtmann <marcel@holtmann.org>
To: Choi Sonim <choisonim@gmail.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] immediate unsolicited disconnect after hcitool cc
Date: Sun, 18 Feb 2007 17:58:30 +0100 [thread overview]
Message-ID: <1171817910.2488.5.camel@violet> (raw)
In-Reply-To: <4f436aae0702180546o4c7a7c58x3028230c1f33878e@mail.gmail.com>
Hi Choi,
> > > after I do "hcitool cc xx:xx:xx:xx:xx:xx" I have a connection
> > > I can see with "hcitool con" but after one or two seconds I can
> > > see in hcidump that an HCI disconnect command is sent and
> > > the connection is disconnected.
> >
> > don't use this command for piconet creation. Use higher layer like L2CAP
> > and RFCOMM. The kernel will create the needed ACL link for you and take
> > fully care of it.
>
> are there command line utilities I can use to test file transfers
> (like in OPP or FTP) ?
the obex CVS repository of BlueZ contains btobex and btftp command line
utilities.
Regards
Marcel
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-02-18 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 12:25 [Bluez-devel] immediate unsolicited disconnect after hcitool cc Choi Sonim
2007-02-18 12:44 ` Marcel Holtmann
2007-02-18 13:46 ` Choi Sonim
2007-02-18 16:58 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-26 5:09 Yuchih Liu
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=1171817910.2488.5.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=choisonim@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.