All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerhard Killesreiter <gerhard@killesreiter.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] SCO for non-CSR based devices?
Date: Wed, 10 May 2006 10:24:31 +0200	[thread overview]
Message-ID: <4461A33F.1060702@killesreiter.de> (raw)

Hi there!

I've recently purchased a bluetooth headset and discovered that my 
bluetooth adapter (a pcmcia card, 
http://www.sphinx-elektronik.de/deutsch/bluetooth/picocard.htm) isn't 
supported by bluetooth-alsa as there is no SCO support for this type of 
device.

During my searches on the web I noticed a kernel patch that was recently 
posted to this list 
(http://article.gmane.org/gmane.linux.bluez.devel/7579). I had a look 
and indeed my card has the problem which is mentioned there, namely it 
displays SCO MTU: 64:0 (Complete output of hciconf -a is at the end of 
this mail).

Now my question is: Would this kernel patch potentially allow me to use 
my card with bluetooth-alsa? Or is the actual problem unrelated? I am 
willing to recompile my kernel and apply this patch or test others, but 
I am really no kernel hacker and so I'd appreciate some input.

Of course, I could simply go and buy a CSR based bluetooth adapter, but 
that's boring. ;)

Cheers,
    Gerhard


hci0:   Type: PCCARD
        BD Address: 00:80:37:15:74:E6 ACL MTU: 672:10 SCO MTU: 64:0
        UP RUNNING PSCAN ISCAN
        RX bytes:125 acl:0 sco:0 events:15 errors:0
        TX bytes:322 acl:0 sco:0 commands:14 errors:0
        Features: 0x07 0xea 0x31 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'theo-dhcp-42-0'
        Class: 0x100100
        Service Classes:
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0xb LMP Ver: 1.1 (0x1) LMP Subver: 0x300
        Manufacturer: Ericsson Technology Licensing (0)



-------------------------------------------------------
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-05-10  8:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  8:24 Gerhard Killesreiter [this message]
2006-05-11 14:20 ` [Bluez-devel] SCO for non-CSR based devices? Brad Midgley
2006-05-11 15:31   ` Peter Wippich
2006-05-10 14:53     ` Gerhard Killesreiter
2006-05-11 18:00       ` [Bluez-devel] documentation for a newbie Özkan Gümüs
2006-05-11 18:35         ` Jan Benes
2006-05-22  0:28       ` broadcom in disguise... (was: [Bluez-devel] SCO for non-CSR based devices?) Gerhard Killesreiter
2006-05-22  4:40         ` [Bluez-devel] Re: broadcom in disguise Brad Midgley
2006-05-22  9:49           ` Gerhard Killesreiter
2006-05-22 15:51             ` Brad Midgley
2006-05-25 15:53               ` Gerhard Killesreiter
2006-05-29  6:49                 ` [Bluez-devel] " Brad Midgley
2006-05-29 11:40                   ` Gerhard Killesreiter

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=4461A33F.1060702@killesreiter.de \
    --to=gerhard@killesreiter.de \
    --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.