Krzysztof Burghardt wrote:
> This is simply not true. Where you read it?

/usr/share/doc/bluetooth-alsa/build.html

[...]
"Configure A2DP Driver This driver allows audio to be sent from an alsa
client to a stereo bluetooth headset."
[...]
"Configure SCO (aka mono, aka voice) Driver This driver will let you
do 2-way audio to and from a mono headset."
[...]

By this analogy, it somehow implies it. Apparently I wasn't the only one
who thought the same.
If it's not true, then the docs should be more specific.

> No. I'm not. Moreover I had never been. AFAIK Ubuntu package was
> automatically build from Debian sources without any human interaction.

OK, I wasn't aware of that.

> Bluez-btsco is old and deprecated one. Have you read
> http://bluetooth-alsa.sourceforge.net/build.html (at the end) ?

Yes I did. Below I've written a list why I thought it is a good idea.

> Quoted: "If for some reason you need to try the old driver, instead of
> checking out "plugz" above, check out "btsco" and build it the same
> way." Do we need old driver? New works perfectly for me. What steps
> you follow to configure it?

Steps from html docs in /usr/share/doc/bluetooth-alsa/

> > Could you please make it available for Debian or, since it's only btsco
> > that's in the package, simply merge them together?
> 
> Yes, but why? What is the point?

As I've written before:
1. It was btsco I used the first time, and it worked.
2. Because the above analogy I thought my device is the "old SCO one".
3. Almost every HOWTO/tutorial online on configuring bluetooth headsets
has a part with btsco.
4. Because btsco IS used in Ubuntu. Actually I don't care about Ubuntu
itself but since it is more luser-friendly, I thought ...
5. Because not so long ago a new version of the graphical front-end for
btsco has been released (releasing graphical front-ends for deprecated
software seems a bit odd to me).

That's why I thought it was a good idea. After your reply it seems it's
not, thank you for clarifying that.

> Can it work or can it be ported to use new driver?

Apparently it does work, although one needs to run it as root (IMO it
should use some kind of sudo calling mechanism automatically). It only
works with btsco but it seems that he's planning to include A2DP support
if future releases. It's just a wrapper to btsco, so without knowing the
difference between the drivers I can't say whether it is possible,
and if so, how hard/easy is it going to be - I'm not a programmer.

OK, once again thank you for clarifying it, sorry for the nasty bug
report.
I guess I'll have to take a deeper look into it.

Cheers,
-- 
Raf


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to