public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BT headset doesn't work: SCO packet for unknown connection
Date: Sun, 17 Feb 2008 14:36:29 -0700	[thread overview]
Message-ID: <d89ddf300802171336k1dbb58fbr352fac67e88eec84@mail.gmail.com> (raw)
In-Reply-To: <200802171917.13813.farcaller@gmail.com>

Vladimir

> On Saturday 16 February 2008 23:35:53 Brad Midgley wrote:
> > I think that error indicates we can't do sco using your bluetooth
> > adapter. Which one is it?
>
> I've just tried windows and it works flawlessly there. So this is not adapter
> problem - toshiba bt stack can do this.

this is probably one of the adapters that the bluez driver cannot use
with sco. That's what I meant by "we can't do sco"

-- 
Brad

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-02-17 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 17:50 [Bluez-users] BT headset doesn't work: SCO packet for unknown connection Vladimir Pouzanov
2008-02-16 21:35 ` Brad Midgley
2008-02-16 21:39   ` Vladimir Pouzanov
2008-02-17 17:17   ` Vladimir Pouzanov
2008-02-17 21:36     ` Brad Midgley [this message]
2008-02-18 13:46 ` Guillaume Bedot
  -- strict thread matches above, loose matches on Subject: below --
2008-02-18  3:55 pramod gurav
2008-02-18 14:42 Guillaume Bedot
2008-02-18 20:53 ` Brad Midgley
2008-02-19 12:24   ` Guillaume Bedot
2008-02-19 13:28     ` Guillaume Bedot

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=d89ddf300802171336k1dbb58fbr352fac67e88eec84@mail.gmail.com \
    --to=bmidgley@gmail.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