From: Sebastian Roth <sebastian.roth@esk.fhg.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: snd-bt-sco built-in (solved)
Date: Tue, 15 Feb 2005 17:07:33 +0100 [thread overview]
Message-ID: <cut6je$4g1$3@sea.gmane.org> (raw)
In-Reply-To: <4211C910.1020204@dark-reality.de>
Hi,
I found the problem! To built it into the kernel I added a directory
under sound called bluetooth. Getting the make-system to compile the
module you have to add this path to sound/Makefile:
cat /usr/src/linux/sound/Makefile
...
obj-$(CONFIG_SND) += bluetooth/ core/ i2c/ drivers/ isa/ pci/ ppc/ arm/
synth/ usb/ sparc/ parisc/ pcmcia/
...
Really don't know why but I've put it in the first position (before
core). This leads to the problem that on bootup ALSA isn't initialized
yet when snd_bt_sco is trying to use it. oops...
cat /usr/src/linux/sound/Makefile #(correct one!)
...
obj-$(CONFIG_SND) += core/ i2c/ drivers/ isa/ pci/ ppc/ arm/ synth/
usb/ sparc/ parisc/ pcmcia/ bluetooth/
...
Now the kernel boots up! A brief test with one of the headsets was ok!
Best regards,
Sebastian
-------------------------------------------------------
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
prev parent reply other threads:[~2005-02-15 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 9:49 [Bluez-devel] snd-bt-sco built-in Sebastian Roth
2005-02-15 10:04 ` Lars Grunewaldt
2005-02-15 12:02 ` [Bluez-devel] " Sebastian Roth
2005-02-15 16:07 ` Sebastian Roth [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='cut6je$4g1$3@sea.gmane.org' \
--to=sebastian.roth@esk.fhg.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