From: Stephen Crane <steve.crane@rococosoft.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Bluetrek G2
Date: Thu, 20 Jan 2005 10:46:57 +0000 [thread overview]
Message-ID: <1106218017.6052.22.camel@baroque.rococosoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
Hello world,
Just to let you know that the above headset works fine with btsco and
2.6.10-mh1 on Mandrake 10.1. (I tried it with 2.6.10 and while it was
detected and connected, I couldn't get any sound out of it --- could
have been my fault though.)
About the web-page: it would be useful to have a TO-DO list so people
could dive in and fix/implement things.
Nice work!
Steve
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-01-20 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 10:46 Stephen Crane [this message]
2005-01-20 12:48 ` [Bluez-devel] Bluetrek G2 Marcel Holtmann
2005-01-23 8:07 ` Brad Midgley
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=1106218017.6052.22.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--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