All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Bluetrek G2
Date: Sun, 23 Jan 2005 01:07:48 -0700	[thread overview]
Message-ID: <41F35B54.4080406@xmission.com> (raw)
In-Reply-To: <1106218017.6052.22.camel@baroque.rococosoft.com>

Hi

I made notes in the docs about PCM routing. Hopefully that was it.

We keep a bug list in sourceforge. If you like the look of any of them, 
jump in.

Brad

Stephen Crane wrote:
> 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


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2005-01-23  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 10:46 [Bluez-devel] Bluetrek G2 Stephen Crane
2005-01-20 12:48 ` Marcel Holtmann
2005-01-23  8:07 ` Brad Midgley [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=41F35B54.4080406@xmission.com \
    --to=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.