From: Fredrik Tolf <fredrik@dolda2000.com>
To: bluez-devel@lists.sourceforge.net
Cc: ms419@freezone.co.uk
Subject: Re: [Bluez-devel] Fwd: alsa bluetooth module
Date: Thu, 17 Mar 2005 23:42:09 +0100 [thread overview]
Message-ID: <1111099329.19889.91.camel@pc7.dolda2000.com> (raw)
In-Reply-To: <e36f1e61ac13a554d52d2f7b8d7a5df4@freezone.co.uk>
On Thu, 2005-03-17 at 14:05 -0800, ms419@freezone.co.uk wrote:
> I maintain a Debian package of bluetooth-alsa - for my convenience -
> but bluetooth-alsa is so popular, some others use this package also -
> http://cgi.sfu.ca/~jdbates/moin/moin.cgi/Bluetooth&ALSA
>
> Blasco contacted me with this problem, but truth is - I haven't got
> bluetooth-alsa working myself.
Regarding that -- I assume your problem is still getting snd-hwdep as a
module, as you stated on the website? I'm just wondering; can't you just
add one of those modules that require snd-hwdep and not care whether
it's actually being used later on? As long as it gets snd-hwdep built...
Fredrik Tolf
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-17 22:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 22:05 [Bluez-devel] Fwd: alsa bluetooth module ms419
2005-03-17 22:34 ` Fredrik Tolf
2005-03-18 23:33 ` Antonio-Blasco Bonito
2005-03-19 14:18 ` Fredrik Tolf
2005-03-19 23:13 ` Antonio-Blasco Bonito
2005-03-17 22:36 ` Brad Midgley
2005-03-17 22:42 ` Fredrik Tolf [this message]
2005-03-17 22:45 ` Brad Midgley
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=1111099329.19889.91.camel@pc7.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=ms419@freezone.co.uk \
/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