From: walt shekrota <penguinacity@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Bluez and Alsa vs OSS!
Date: Mon, 5 Mar 2007 12:41:34 -0800 (PST) [thread overview]
Message-ID: <190537.59911.qm@web62311.mail.re1.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]
I have my headset working reasonably with a kernel that has Alsa enabled but not the OSS emulation ie I do not have a /dev/dsp sym link. Works good.
Now I decided I needed the OSS enabled as there are some older apps I cannot use without the emulation. I redid the kernel and came up with it. The proper OSS device sym links show up in dev and work properly yet the whole headset discovery issue goes out the window. Alsa appears to work fine
When invoking btsco it discovers the proper card and device but the open fails saying device does not exist.
Does anyone know this issue?
Thanks for any help.
-Walt
---------------------------------
Now that's room service! Choose from over 150,000 hotels
in 45,000 destinations on Yahoo! Travel to find your fit.
[-- Attachment #1.2: Type: text/html, Size: 929 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2007-03-05 20:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=190537.59911.qm@web62311.mail.re1.yahoo.com \
--to=penguinacity@yahoo.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