From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth-alsa kernel bug and alsa bug too
Date: Thu, 23 Dec 2004 12:38:12 +0100 [thread overview]
Message-ID: <1103801892.20258.64.camel@pegasus> (raw)
In-Reply-To: <200412222331.17330.cijoml@volny.cz>
Hi Michal,
> there is a bug in btsco:
>=20
> when compiled and not CONFIG_SND_HWDEP, module writes bad symboles. It =
should=20
> have snd_hwdep in dependent modules section
>=20
> I have =20
> =E2=94=82 =E2=94=82 <M> Intel i8x0/MX440, SiS=
7012; Ali 5455; NForce=20
> Audio; AMD768/8111 =E2=94=82 =E2=94=82
> =E2=94=82 =E2=94=82 <M> Intel i8x0/MX440; S=
iS 7013; NForce;=20
> AMD768/8111 modems (EXPERIMENTAL) =E2=94=82=
=E2=94=82
>=20
> And this module snd_hwdep is not compiled. Possibly alsa bug too?
it is not that easy to select hwdep from an outside driver. This is an
ALSA bug, because they don't provide a kernel option to compile hwdep
even if no other selected driver uses it. The best way is to select a
USB driver in your kernel that needs hwdep and everything will be fine.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-12-23 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 22:31 [Bluez-users] bluetooth-alsa kernel bug and alsa bug too Michal Semler
2004-12-23 11:38 ` Marcel Holtmann [this message]
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=1103801892.20258.64.camel@pegasus \
--to=marcel@holtmann.org \
--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