From: Martin Xu <martin.xu@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Martin Xu <martin.xu@intel.com>
Subject: [PATCH] Add Unknow after LEMeta Event
Date: Mon, 10 Oct 2011 02:21:57 -0700 [thread overview]
Message-ID: <1318238517-4702-1-git-send-email-martin.xu@intel.com> (raw)
According to Core_v4.0
LE Meta Event Event Code is 0x3E, While Physical Link Complete Event Code is 0x40
So add Unknow after LEMeta Event
---
parser/hci.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/parser/hci.c b/parser/hci.c
index 610177b..d36b54b 100644
--- a/parser/hci.c
+++ b/parser/hci.c
@@ -44,7 +44,7 @@ static inline uint16_t get_manufacturer(void)
return (manufacturer == DEFAULT_COMPID ? parser.defcompid : manufacturer);
}
-#define EVENT_NUM 76
+#define EVENT_NUM 77
static char *event_str[EVENT_NUM + 1] = {
"Unknown",
"Inquiry Complete",
@@ -109,6 +109,7 @@ static char *event_str[EVENT_NUM + 1] = {
"Keypress Notification",
"Remote Host Supported Features Notification",
"LE Meta Event",
+ "Unknown",
"Physical Link Complete",
"Channel Selected",
"Disconnection Physical Link Complete",
--
1.7.2.2
next reply other threads:[~2011-10-10 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 9:21 Martin Xu [this message]
2011-10-10 9:35 ` [PATCH] Add Unknow after LEMeta Event Johan Hedberg
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=1318238517-4702-1-git-send-email-martin.xu@intel.com \
--to=martin.xu@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
/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