From: "Jackie" <xhx321@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Return 'Invalid arguments' status after l2ping
Date: Wed, 23 Apr 2008 23:41:26 +0800 [thread overview]
Message-ID: <funlb1$1om$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Hello all:
I compiled the blueZ-2.20 on the mipsel platform, kernel version is
2.4.21. While execute
the command like "l2ping xx:xx:xx:xx:xx:xx". The shell tips "Connection
failed: invalid arguments"
immediately.
hcidump the data like this:
/tmp/bin # ../sbin/hcidump -x &
/tmp/bin # HCI sniffer - Bluetooth packet analyzer ver 1.22
device: hci0 snap_len: 1028 filter: 0xffffffff
/tmp/bin # ./l2ping 00:17:4b:54:8d:2e
< HCI Command: Create Connection (0x01|0x0005) plen 13
2E 8D 54 4B 17 00 18 CC 02 00 00 00 01
Can't connect: Invalid argument
/tmp/bin # > HCI Event: Command Status (0x0f) plen 4
12 01 05 04
By the way, the bluetooth dongle's HCI version is 1.1
Who could tell me the reason? thanks
[-- Attachment #2: Type: text/plain, Size: 320 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
[-- 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:[~2008-04-23 15:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='funlb1$1om$1@ger.gmane.org' \
--to=xhx321@gmail.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 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.