public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: gilboad@gmail.com, BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Suggesting bluez_pinhelper
Date: Sun, 27 May 2007 18:36:36 +0200	[thread overview]
Message-ID: <1180283796.21432.73.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1180273950.15368.42.camel@gilboa-work-dev.localdomain>

Hi Gilboa,

> I'm currently trying to get kdebluetooth reviewed into Fedora Core (and
> RHEL).
> As some of you may be aware, the current version of kdebluetooth has no
> support for recent (>= 3.9) bluez DBUS interface.
> As an interim solution I decided to write a small wrapper that can be
> used as a bridge between kdebluetooth's kbluepin and bluez-utils 3.9
> (running on the about to be released F7) - basing my work around
> bluez-utils' passkey-agent.
> While working on it I decided to further expand it - making it
> configurable and script-able which in turns, makes it entirely possible
> to create passkey dialog boxes in non-X modes (using 'dialog') or in
> low-end machines with minimal WM's (using 'zenity' in
> IceWM/Fluxbox/etc).
> 
> As it stands I got two options:
> A. Use this code as a stop-gate until qt-dbus + kdebluetooth is released
> (KDE 4?) maintaining this code as a Fedora-only blob.
> B. If its of any use to anyone (read, you), get it submitted into
> bluez-utils while maintaining it (and expending it - if so required)
> upstream.

take this up with the KDE Bluetooth guys since it the Bluetooth support
for KDE 3.x got basically abandoned. It is their job to actually fix it
and provide whatever they need to make Bluetooth working. I am not
really open for crazy hacks. The passkey-agent.c source code is mainly
an example on how to write a passkey agent and was used for initial
testing.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-05-27 16:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27 13:52 [Bluez-devel] Suggesting bluez_pinhelper Gilboa Davara
2007-05-27 16:36 ` Marcel Holtmann [this message]
2007-05-27 17:28   ` Gilboa Davara
2007-05-27 18:04     ` Marcel Holtmann
2007-05-27 18:35       ` Gilboa Davara
2007-05-28  8:29         ` Marcel Holtmann
2007-05-27 16:59 ` Petteri Räty
2007-05-27 17:31   ` Gilboa Davara
2007-05-27 17:48     ` Petteri Räty
2007-05-27 18:41       ` Gilboa Davara
2007-05-29 11:27         ` Stefan Seyfried
2007-05-29 12:45           ` Gilboa Davara
2007-05-27 23:19 ` Daniel Gollub
2007-05-27 23:39   ` Denis KENZIOR
2007-05-28 16:48     ` Daniel Gollub
2007-05-28 21:11       ` Denis KENZIOR
2007-05-28 22:21         ` Daniel Gollub
2007-05-28  8:29   ` Marcel Holtmann
2007-05-28 16:53     ` Daniel Gollub
2007-05-29  3:50       ` Marcel Holtmann

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=1180283796.21432.73.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=gilboad@gmail.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