public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Tetsuo Shiraishi <tetsu@s-direct.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcid pin problem
Date: Mon, 14 Jun 2004 18:00:25 +0200	[thread overview]
Message-ID: <1087228825.13792.14.camel@pegasus> (raw)
In-Reply-To: <4.3.2-J.20040613230727.0638bee8@emi.s-direct.com>

Hi Tetsuo,

> I could not get pin_helper to work, 
> since I upgraded to bluez-utils-2.7 from bluez-utils-2.3.
> 
> Using system
> - sh4-linux
> - patch-2.4.24-mh5.gz 
> - bluez-libs-2.7.tar.gz 
> - bluez-utils-2.7.tar.gz 
> - pin_helper in hcid.conf
> 
> I modified bluez-utils-2.7 as follows, so it work fine.
> 
> --- bluez-utils-2.7/hcid/security.c	Sun May  9 19:39:43 2004
> +++ bluez-utils-2.7_mod/hcid/security.c	Sun Jun 13 22:53:29 2004
> @@ -236,7 +236,7 @@
>  {
>  	pin_code_reply_cp pr;
>  	struct sigaction sa;
> -	char addr[12], str[255], *pin, name[20];
> +	char addr[18], str[255], *pin, name[20];
>  	FILE *pipe;
>  	int ret, len;

thanks for this report. I applied your patch.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-06-14 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-13 15:08 [Bluez-users] hcid pin problem Tetsuo Shiraishi
2004-06-14 16:00 ` Marcel Holtmann [this message]

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=1087228825.13792.14.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=tetsu@s-direct.com \
    /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