From: Marcel Holtmann <marcel@holtmann.org>
To: Volker <kokor.hekkus@gmx.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] pairing on x86_64
Date: Sat, 21 Feb 2004 14:56:11 +0100 [thread overview]
Message-ID: <1077371771.2716.5.camel@pegasus> (raw)
In-Reply-To: <200402211434.54164.kokor.hekkus@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Hi Volker,
> security.c loads the right pin at startup.
> during pairing, it enters
>
> gboolean io_security_event(GIOChannel *chan, GIOCondition cond, gpointer data)
>
> and leaves the method at this point:
>
> if (type != HCI_EVENT_PKT) {
> syslog(LOG_INFO, "** type not HCI_EVENT_PKT");
> return TRUE;
> }
>
> any more points, where I should've a look at?
try the attached patch.
Regards
Marcel
[-- Attachment #2: patch --]
[-- Type: text/x-patch, Size: 393 bytes --]
diff -urN utils/hcid/security.c utils-mh/hcid/security.c
--- utils/hcid/security.c 2004-02-17 19:34:30.000000000 +0100
+++ utils-mh/hcid/security.c 2004-02-21 14:54:37.000000000 +0100
@@ -367,7 +367,8 @@
{
char buf[HCI_MAX_EVENT_SIZE], *ptr = buf;
struct hci_dev_info *di = (void *) data;
- int len, type, dev;
+ unsigned char type;
+ int len, dev;
hci_event_hdr *eh;
GIOError err;
next prev parent reply other threads:[~2004-02-21 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 11:52 [Bluez-users] pairing on x86_64 Volker Fritzsch
2004-02-21 12:09 ` Marcel Holtmann
2004-02-21 13:34 ` Volker
2004-02-21 13:56 ` Marcel Holtmann [this message]
2004-02-21 14:08 ` Volker Fritzsch
2004-02-21 14:18 ` Marcel Holtmann
2004-02-21 15:48 ` Volker Fritzsch
2004-02-21 16:11 ` Marcel Holtmann
2004-02-21 20:00 ` Volker Fritzsch
2004-02-22 2:15 ` Marcel Holtmann
2004-02-22 13:24 ` Volker Fritzsch
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=1077371771.2716.5.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=kokor.hekkus@gmx.de \
/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.