From: Peter Wurmsdobler <peter@wurmsdobler.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] #define OGF_TESTING_CMD potentially wrong?
Date: Tue, 22 Jul 2008 14:41:41 +0100 [thread overview]
Message-ID: <4885E395.8090109@wurmsdobler.org> (raw)
In-Reply-To: <1216730752.31819.28.camel@californication>
Hello Marcel,
> that hcidump shows something as unknown, doesn't mean that it didn't
> work. Actually hcidump is only a passive tool like tcpdump. So feel free
> to send a patch to fix hcidump, but this doesn't mean that hcitool is
> not working.
This was my understanding, too. After issuing the command with ogf=0x06
our test equipment could take over the module, which proved for me that
the command had worked. However, the #define hcidump uses is defined in
bluez-libs/include/hci.h. I will send a patch.
peter
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-07-22 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 10:36 [Bluez-users] #define OGF_TESTING_CMD potentially wrong? Peter Wurmsdobler
2008-07-22 12:45 ` Marcel Holtmann
2008-07-22 13:41 ` Peter Wurmsdobler [this message]
2008-07-26 21:35 ` [Bluez-users] compile error: bluetooth/bluetooth.h: No such file or directory thanit sara
2008-07-27 0:32 ` 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=4885E395.8090109@wurmsdobler.org \
--to=peter@wurmsdobler.org \
--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