What's wrong with the l2ping during the cross-compling!

"Jackie" <[email protected]>
Newsgroups gmane.linux.bluez.user
Message-ID <[email protected]>
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!

-------------------------------------------------------------------------
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

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.