public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Florian Philipp <lists@binarywings.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: PIN Helper
Date: Wed, 16 Sep 2009 19:41:04 +0300	[thread overview]
Message-ID: <20090916164104.GA11739@jh-x301> (raw)
In-Reply-To: <4AB107DE.5070700@binarywings.net>

Hi,

On Wed, Sep 16, 2009, Florian Philipp wrote:
> Of course I can't force you to do the programming but removing
> functionality which worked - more or less - out of the box with an older
> release and not providing any working alternative except of a
> do-it-yourself solution ... well ... just sounds wrong.

I think part of the explanation is lack of knowledge about exactly in
which ways people use BlueZ and how popular these use cases are. To be
honest, I'm not sure I still understand exactly what kind of behavior or
feature you're after.

> Okay, so without some significant work, you could only support legacy
> pairing for those old deamons and I suppose that's all those test apps
> can, right?

Exactly which old daemons are you talking about? I don't see how any old
software that isn't aware of the current pairing/agent interface could be
made to work "without some significant work".

> a) Create and maintain the missing parts myself.

If the functionality makes sense and the implementation follows the usual
coding standards that we have I don't see why you would be stuck
maintaining it yourself. Surely it should be possibe to merge the work
with upstream.

Johan

  reply	other threads:[~2009-09-16 16:41 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 [this message]
2009-09-16 18:39           ` Florian Philipp
2009-09-17 19:49             ` Luiz Augusto von Dentz

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=20090916164104.GA11739@jh-x301 \
    --to=johan.hedberg@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