public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco crash without daemon
Date: Sat, 15 Jan 2005 16:19:56 +0100	[thread overview]
Message-ID: <41E9349C.8060001@dark-reality.de> (raw)
In-Reply-To: <41E92C83.8010406@egabriel.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ligi wrote:
| Lars Grunewaldt wrote:
|

| | Why can't you get it working with 2.6.10? It works absolutly flawless
| | here with 2.6.10.
| |
| i dont know - the problems occoured when btsco got rid of the
| kernel-patches in my case when migrating to 2.6.10

did you patch the kernel with the -mh10 patchset from bluez? I did, and
I don't have any problems at all...

|
| | Maybe you should get the latest sources from CVS (module btsco) and give
| | it a fresh start?
| |
| i use them.

OK :)

|
| | Also do NOT use any kernel patches any more!
|
| i dont patch the kernel anymore and neither alsa

any might have been wrong - you should use the mh10 patch from bluez, as
noted above...

|
| | The alternate setting for
| | hci_usb can be set by parameter when loading the module,
|
|
| what do you mean ?

If you don't know, you don't have to bother. This is only important for
multiple headsets (if you don't use only one headset, you have to change
this "alternate setting". If you use only one headset, you don't have to
care :)

But this (or, the absence of the module parameter) was the reason for
the btsco-kernel patch.

| | and the
| | snd-bt-sco resides in the /kernel directory and can be compiled simply
| | by using "make" in this directory :)
| |
| there are no problems in building - just in runnig  wont work
|
| bash-2.05b# ./btsco 00:0E:16:01:06:ED
| Device is 1:0
| Error: btsco open (1-0): No such device or address

yes, that's strange. I don't experience any problems here :(

regards,
~  Lars

- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB6TSbQWC6DTWkDAoRApsfAKCPaUe4+CSv6uIxeBKidQQy+6F5OACgiGJD
sMduvdTYZQSt6nCrTjvVW6Y=
=7qhc
-----END PGP SIGNATURE-----


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-15 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 13:32 [Bluez-devel] btsco crash without daemon ligi
2005-01-15 14:17 ` Lars Grunewaldt
2005-01-15 14:45   ` ligi
2005-01-15 15:19     ` Lars Grunewaldt [this message]
2005-01-15 18:59       ` ligi
2005-01-16  0:32         ` Lars Grunewaldt
2005-01-16 10:41           ` ligi
2005-01-16 17:10             ` Lars Grunewaldt

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=41E9349C.8060001@dark-reality.de \
    --to=lgw@dark-reality.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox