All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Williams, Richard" <Richard.Williams@VITRONICS.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Problem with hci_usb
Date: Tue, 02 Mar 2004 23:15:08 +0100	[thread overview]
Message-ID: <1078265708.2787.7.camel@pegasus> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A45BDAFA@goofy.vitronics.com>

Hi Richard,

> I'm trying to get my Linux machine to support audio to a headset. There's
> been several replies in the last week to my questions about SCO support 
> in Linux. But I haven't found a package or instructions that explain how
> to get it to work. A couple of people have said "hstest" or "scotest", but
> nothing really works. Now I see the above posting. Does this mean I should 
> abandon my headset work until SCO is working ?

everything depends on what you are trying to achieve. In general we have
SCO support, but it is not perfect and not very easy to use.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-03-02 22:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 21:47 [Bluez-devel] Problem with hci_usb Williams, Richard
2004-03-02 22:15 ` Marcel Holtmann [this message]
2004-03-03  0:52 ` James Courtier-Dutton
  -- strict thread matches above, loose matches on Subject: below --
2004-03-03 12:50 Williams, Richard
2004-03-02 17:05 Nils Faerber
2004-03-02 17:30 ` Marcel Holtmann
2004-03-02 18:42   ` Nils Faerber
2004-03-02 19:42     ` Marcel Holtmann
2004-03-02 21:03 ` James Courtier-Dutton

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=1078265708.2787.7.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Richard.Williams@VITRONICS.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.