From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] combination keys support?
Date: Sun, 14 Nov 2004 21:09:57 +0100 [thread overview]
Message-ID: <1100462998.21403.64.camel@pegasus> (raw)
In-Reply-To: <4197B6BD.4080205@gmx.ch>
Hi Marco,
> > and how did you do this? Looking from the
> > HCI there is no difference between these keys.
>
> Is this an firmware-specific (of my bluetooth dongle)?
> Just read a website that told me this...
you said, that you tried it and it fails. What do you wanna know if you
haven't tried it?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-14 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 19:49 [Bluez-devel] combination keys support? Marco Trudel
2004-11-14 20:09 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 7:18 [Bluez-devel] combination keys support? [5] Marco Trudel
2004-11-15 13:26 ` [Bluez-devel] combination keys support? Marcel Holtmann
2004-11-14 22:12 [Bluez-devel] combination keys support? [4] Marco Trudel
2004-11-14 23:09 ` [Bluez-devel] combination keys support? Marcel Holtmann
2004-11-14 20:50 Marco Trudel
2004-11-14 21:05 ` Marcel Holtmann
2004-11-14 18:18 Marco Trudel
2004-11-14 18:31 ` 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=1100462998.21403.64.camel@pegasus \
--to=marcel@holtmann.org \
--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