From: ligi <ligi@egabriel.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco crash without daemon
Date: Sat, 15 Jan 2005 19:59:30 +0100 [thread overview]
Message-ID: <41E96812.7030903@egabriel.de> (raw)
In-Reply-To: <41E9349C.8060001@dark-reality.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ok - i have installed the mh1 patch now but that did not solve my
problem. I had a little look on the code and the problematic line
seems to be:
~ /* open hwdep on audio device */
~ if ((err = snd_hwdep_open(&handle, hwdep_name, O_RDWR)) < 0) {
~ error("btsco open (%i-%i): %s\n", card, dev,
snd_strerror(err));
~ return -1;
~ }
I am using Gentoo and here alsa is an ebuild that wants alsa not to be
compiled in the kernel it has to be external( build from
alsa-driver-1.0.8rc2.tar.bz2 by that ebuild of portage ).
But snd_hwdep is loaded and there is no complaining of missing things
- - this method just fails...
Has anyone some Hint ?
ligi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB6WgS3NorRo/jFWIRAtJBAKDchAK+HqeCW/H1DjjRBh2yt4VX9gCfVXR/
USHgCsykPm4tsJmNHSh42GI=
=VQLx
-----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
next prev parent reply other threads:[~2005-01-15 18:59 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
2005-01-15 18:59 ` ligi [this message]
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=41E96812.7030903@egabriel.de \
--to=ligi@egabriel.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