All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Barnett <jbarnett@pobox.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Plugz with Dell inbuilt-BT
Date: Thu, 08 Feb 2007 11:54:33 -0500	[thread overview]
Message-ID: <1170953673.3329.11.camel@localhost> (raw)
In-Reply-To: <45CB36E2.7000406@free.fr>


[-- Attachment #1.1: Type: text/plain, Size: 1543 bytes --]

The problem with the bt-hijacker approach is that it is based on the
snd-bt-sco module which creates the necessary /dev/dspX entry for
re-routing sound. The plugz approach doesn't result in the creation of
a /dev/dspX. So the hijacker can't reroute the sound as far as I can
see. Or am I missing something?

Cheers,

JonB

On Thu, 2007-02-08 at 15:42 +0100, Fabien Chevalier wrote:
> Hi,
> 
> Mark Hellman wrote:
> > Jon Barnett wrote:
> > 
> >> The only problem is that skype can't use the plugz device as it doesn't
> >> recognize it  - since it doesn't do detection of available pcm devices.
> > 
> >>From a user's perspective that is, in my opinion, the main problem with
> > using plugz instead of btsco. Skype and Ekiga are the reasons why 90% of
> > users want to install plugz.
> > 
> > Is this an ALSA limitation, or isn't Skype using the right functions from
> > the ALSA's API to enumerate all available devices? Who must be fixes: Skype
> > of ALSA?
> 
> Thing is : sadly, there is no ALSA function to enumerate available PCMs 
> on the system. There are only features to enumerate hardware cards. 
> That's a known ALSA weakness, but this is how things are as of to today 
> in Linux world :-(
> 
> > Could some developer enlighten us on this issue?
> 
> Just use Skype in OSS mode, and use skype_bt_hijacker available in 
> contrib directory to redirect sound to ALSA headset. I haven't tested it 
> myself recently, but theorically this should work.
> 
> Cheers,
> 
> Fabien
> 
> 
> 

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 374 bytes --]

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-02-08 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 18:27 [Bluez-devel] Plugz with Dell inbuilt-BT Jon Barnett
2007-02-06 13:06 ` Mark Hellman
2007-02-08 14:42   ` Fabien Chevalier
2007-02-08 16:54     ` Jon Barnett [this message]
2007-02-06 13:11 ` Mark Hellman

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=1170953673.3329.11.camel@localhost \
    --to=jbarnett@pobox.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.