From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] snd-bt-sco problems (Brad, Marcel)
Date: Mon, 29 Nov 2004 13:48:16 -0700 [thread overview]
Message-ID: <41AB8B10.2070303@xmission.com> (raw)
In-Reply-To: <200411291935.12702.carlosarazevedo@netcabo.pt>
Carlos
> Brad : I don't have any other dongle or headset, but I've tested both on
> Windows and they work together; aplay exists after a 9-10 second timeout; I'm
> not running any kind of X because this is a telephony server machine (or will
> be); I've tried with the following modules.conf but to no avail :
...
> since I'm running LFS, a do-it-yourself distro, I don't have a specific
> startup script, I just load the modules (snd-via82xx and snd-bt-sco)
I'm not suggesting you try different hardware because they can't talk to
one another... it's because we have a software problem somewhere and I
want to isolate it.
Your setup looks fine. I haven't dug into the kernel module any more
than I've had to so I don't know where to look there. I haven't wanted
to because it may need to be moved to userspace anyway.
Do we have tools for testing sco audio to and from the headset entirely
in userspace?
Brad
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-11-29 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 19:35 [Bluez-users] snd-bt-sco problems (Brad, Marcel) Carlos Azevedo
2004-11-29 20:48 ` 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=41AB8B10.2070303@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 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.