linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluetooth 1.2 and 2.0 dongles support (I have AVM Bluefritz! V2.0)
Date: Sun, 02 Oct 2005 14:16:29 -0600	[thread overview]
Message-ID: <4340401D.9040404@xmission.com> (raw)
In-Reply-To: <433D997A.7090105@schugy.de>

Christian,

Is AVM the manufacturer? It's a good idea to start with them. Ask them 
about their support page and why support doesn't include voice audio. 
You can tell them to hire Marcel and provide him documentation. We can 
dream, eh?

Ideally the manufacturer should at least play a role in facilitating 
driver support rather than standing in the way as we've seen some do.

Brad

Christian Schuglitsch wrote:
> Dear Linux Bluetooth users,
> I've bought a bluefritz2.0 dongle because AVM has a page that says that 
> this dongle works with Linux.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-10-02 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 12:15 [Bluez-users] bluetooth 1.2 and 2.0 dongles support Esteban Monturus
2005-09-30 12:23 ` Marcel Holtmann
2005-09-30 20:00   ` [Bluez-users] bluetooth 1.2 and 2.0 dongles support (I have AVM Bluefritz! V2.0) Christian Schuglitsch
2005-10-02 20:16     ` Brad Midgley [this message]
2005-10-01 11:26   ` Christian Schuglitsch
2005-10-01 11:34   ` Christian Schuglitsch
2005-10-01 11:37   ` Christian Schuglitsch

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=4340401D.9040404@xmission.com \
    --to=bmidgley@xmission.com \
    --cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).