From: "Jackie" <xhx321@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] What's wrong with the l2ping during the cross-compling!
Date: Sun, 20 Apr 2008 23:02:08 +0800 [thread overview]
Message-ID: <fufltc$fre$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Dears:
I meet such question which delayed my schedule for several days.
The issue is that : I compiled the blueZ-2.20 in X86 platform, and execute
the command like "l2ping xx:xx:xx:xx", it can worked well.
but after compiled it with mipsel-compiler,and run the same command in
mipsel platform, the shell tips "Connection failed: invalid arguments". And
in the mipsel platform, the "hcitool scan" could work well already.but
'l2ping' & 'sdptool browse' can work which both tips "invalid argument". And
I have execute the hcidump in mipsel, which show only two lines. One is the
outgoing command data , the other is feedback events data. Compared it with
the result that hcidump in X86, the first outgoning command data is same.
But, the feedback data which has four bytes, the first byte is different
which seems like statue code, the other three bytes is same.
Almost forget that: In x86 the linux kernel version is 2.6.10, while in
mipsel kernel version is 2.4.21(I've done the newest patch).
If anybody met the same thing or knew what the reason, please give me some
help!
[-- 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-20 15:02 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='fufltc$fre$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 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).