From: Sebastian Roth <sebastian.roth@esk.fhg.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: snd-bt-sco built-in
Date: Tue, 15 Feb 2005 13:02:52 +0100 [thread overview]
Message-ID: <cuso8n$4g1$2@sea.gmane.org> (raw)
In-Reply-To: <4211C910.1020204@dark-reality.de>
Hi Lars,
thanks for your fast reply!
> | I'm trying to build snd-bt-sco directly into the kernel.
>
> why?
I'm working on a project in which a "communication-server" should use
bluetooth headsets...
So I want to have the kernel with all functions built-in. If this is
not possible I'll have to load it on startup. ;-(
> I can't tell for sure why this function is failing this way. Did you
> build snd-hw-dep and put it in the kernel, too? If it's missing than
> that could be the problem.
That was my first guess too! But it's built-in
grep SND /boot/config-2.6.10-mh4-sr1 | grep -v "^#"
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_EMU10K1=y
CONFIG_SND_USB_AUDIO=y
CONFIG_SND_BT_SCO=y
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
next prev parent reply other threads:[~2005-02-15 12:02 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 ` Sebastian Roth [this message]
2005-02-15 16:07 ` [Bluez-devel] Re: snd-bt-sco built-in (solved) Sebastian Roth
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='cuso8n$4g1$2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.