From: Johan Hedberg <johan.hedberg@gmail.com>
To: Kartikey Parmar <kartikey2781@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez PIN generation in non-gui based application
Date: Sat, 4 Apr 2009 12:54:25 +0300 [thread overview]
Message-ID: <20090404095425.GA14455@jh-x301> (raw)
In-Reply-To: <6887eb5d0904032108k73484ee9p7b872bf0c492f0ed@mail.gmail.com>
Hi,
On Sat, Apr 04, 2009, Kartikey Parmar wrote:
> While cross compiling bluez-gnome-1.8, I found that it is dependent on
> GTK+ and GTK+ is dependent on ATK, PANGO, CAIRO.
> Is it possible to run bluez-gnome-1.8 application on simple linux that
> doesn't support GUI? or is there any other application available which
> can be used to generate linkkey from fixed PIN given?
You could e.g. make a minor modification to test/simple-agent to make it return
a fixed PIN in the RequestPinCode callback. Alternatively you try to update
test/agent.c to work with the new Agent interface.
Johan
prev parent reply other threads:[~2009-04-04 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 4:08 bluez PIN generation in non-gui based application Kartikey Parmar
2009-04-04 9:54 ` Johan Hedberg [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=20090404095425.GA14455@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=kartikey2781@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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