public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btsco/alsa-plugins Kernel 2.6.18-mh7 (and mh4-fch)
Date: Mon, 13 Nov 2006 08:29:18 -0700	[thread overview]
Message-ID: <45588F4E.7060800@xmission.com> (raw)
In-Reply-To: <24517632.1163062392189.JavaMail.root@mail.prologistik.com>

Chafik

> 1. pls find attached btsco patch

applied by the way.

> 2. uhhmm ..the Cellink headset is BTST-9000A ... 
> the Cellink dongle is BTA-6030

I have not heard of anyone having trouble with these and bluecore is 
supposed to be our best chance of working.

> well ... fabien has only nonblocking socket communication ...
> i will test further ... i might be mistaken with my previous statement 
> saying "NO effect".

Fabien has been making a lot of changes lately that I need to catch up with.

> i added a small previous fix to "remote volume control" in btsco.c and
> btsco2.c...  the BT-core spec defines host_TO_HS RVC commands (+VGS, +VGM)
> to need prefix \r\n AND postfix the same way!
> (This was the only way to make my RVC capable HS REALLY change volume!)
> Did you know that there exists NO SINGLE bt-stack for windose that makes real
> use of RVC !?
> fortunately headsetd (volctl.c) does it already the right way...

I guess we were lucky it worked for any headset.

> i have checked 4 different CSR based USB dongles:
> - notebook built in IBM R51 BT-dongle (bluecore 2)
> - Cellink BT2.0+EDR dongle (bluecore3)
> - hama BT2.0+EDR dongle (bluecore3-MM)
> - new custom BT-Dongle by Lintech (germany) (bluecore3-MM)
> 
> 3 headsets with HSprofile (SCO + RVC!):
> - Cellink BT-9000ST (only HSProfile tested!)
> - AS-Kabel (sweden) (have you ever used a headset in a disco ? :) 
> (NOISECANCELLING with free2move CSR bluecore 1 class 1! BEST one but BULKY)

probably cost someone a fortune if it was made back when bluecore1 was new.

> - new custom design with Lintech-BT audio module
> 
> i have to admit that the test matrice might be incomplete (sparse) due to the
> fact that i prefer OUR custom design :))

well I look forward to seeing it. I hope you can keep us honest whenever 
we do something wrong in the apps.

brad

-------------------------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-11-13 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 14:08 [Bluez-devel] btsco/alsa-plugins Kernel 2.6.18-mh7 (and mh4-fch) Chafik Moalem
2006-11-08 17:44 ` Chafik Moalem
2006-11-08 19:54   ` Brad Midgley
2006-11-08 22:19     ` Chafik Moalem
2006-11-09  8:53       ` Chafik Moalem
2006-11-13 15:29         ` Brad Midgley [this message]
2006-11-13 16:49           ` Chafik Moalem

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=45588F4E.7060800@xmission.com \
    --to=bmidgley@xmission.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox