public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Florian Philipp <lists@binarywings.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: PIN Helper
Date: Thu, 17 Sep 2009 16:49:22 -0300	[thread overview]
Message-ID: <2d5a2c100909171249g24fc2572rf75723f4c4cb7feb@mail.gmail.com> (raw)
In-Reply-To: <4AB130C4.5030205@binarywings.net>

Hi,

On Wed, Sep 16, 2009 at 3:39 PM, Florian Philipp <lists@binarywings.net> wrote:
> Well, I'm pretty sure some other guys came up with the exact same
> question which was the start of this thread at various occasions last
> year or so (i.e. wanting to have a simple daemon-like pin helper). From
> your post I read that you acknowledge that this functionality which
> those other guys and me miss in bluez is something you'd like to have
> back in, right?
>
> So, if any solution, maybe heavily based on those two test programs
> would really make it back into upstream and would not be dropped because
> it somehow does not fit in the current design or whatever (that's what
> my original question was because the functionality _was already there_
> in 2.x), then why is the answer to those requests always "Do it
> yourself" and not at least "Do it yourself and maybe send it to us so we
> can merge it into upstream"?
>
> That's exactly what I wanted to know in the first place: Why you would
> not want this functionality in bluez but rather put people requesting it
> down with "Do it yourself (and leave us alone)". At least that was my
> impression.

Actually I think agent.c can be used for what seems to be your use
case, you need a pincode helper which handle pincode requests with a
predefined pincode which is what agent will do if you pass a pincode
e.g. agent 1234. Also you are free to suggest improvements, we are
very happy to accept patches from anyone as you can see from the
commit logs.

-- 
Luiz Augusto von Dentz
Engenheiro de Computação

      reply	other threads:[~2009-09-17 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  6:01 PIN Helper Kartikey Parmar
2009-09-15  6:11 ` Johan Hedberg
2009-09-15 16:24   ` Florian Philipp
2009-09-15 16:58     ` Johan Hedberg
2009-09-16 15:44       ` Florian Philipp
2009-09-16 16:41         ` Johan Hedberg
2009-09-16 18:39           ` Florian Philipp
2009-09-17 19:49             ` Luiz Augusto von Dentz [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=2d5a2c100909171249g24fc2572rf75723f4c4cb7feb@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lists@binarywings.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