public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandros Vellis <avel@noc.uoa.gr>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem with link keys
Date: Wed, 10 Aug 2005 17:14:46 +0300	[thread overview]
Message-ID: <1123683286.31383.6.camel@amy> (raw)
In-Reply-To: <20050806090723.GA13065@as.arizona.edu>

John Gruenenfelder wrote:

> 2) btsco allows for creating a .btsco file with regex in it so that you can
>    make it do something on a button press.  How do I learn what those regex
>    should be for my particular headset?  Is it part of one of the packets
>    dumped by hcidump?

If I'm not mistaken, you can watch what is communicated with the headset
with 'btsco -v'.




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-08-10 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06  3:01 [Bluez-devel] Problem with link keys John Gruenenfelder
2005-08-06  4:10 ` Marcel Holtmann
2005-08-06  5:01   ` John Gruenenfelder
2005-08-06  5:07     ` Marcel Holtmann
2005-08-06  9:07       ` John Gruenenfelder
2005-08-10 14:14         ` Alexandros Vellis [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=1123683286.31383.6.camel@amy \
    --to=avel@noc.uoa.gr \
    --cc=bluez-devel@lists.sourceforge.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