From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluez-users Digest, Vol 25, Issue 18
Date: Sat, 24 May 2008 09:41:55 -0500 [thread overview]
Message-ID: <48382933.3030209@earthlink.net> (raw)
In-Reply-To: <1211618718.4244.27.camel@goya.uc3m.es>
On 05/24/2008 03:45 AM, Javi F Gorostiza wrote:
> Hello,
> I've parched and compiled the kernel-2.6.23.17 to get headsetd working.
> And everything is allright BUT one detail. When I open an alsa pcm_sco
> device to capture the data form a BT headset, in the console a lot of
> DEBUG messages arises. They are so much that the functionality of my
> application decreases, and I cannot see the usefull information in the
> console...it's really horrible.
> I think that all those DEBUG messages are relationated with an option in
> the kernel (.config file) but I can find it at all.
> Does anybody know how to switch off these information, please?
> Thanks,
> J
>
You can control what kernel messages get to the console by using the
"dmesg" program. For example, try this:
dmesg -n4
By the way, your message was confusing because you replied to the digest
message rather than to an individual message in the digest.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-05-24 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.308836.1211604429.29930.bluez-users@lists.sourceforge.net>
2008-05-24 8:45 ` [Bluez-users] Bluez-users Digest, Vol 25, Issue 18 Javi F Gorostiza
2008-05-24 14:41 ` Mumia W.. [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=48382933.3030209@earthlink.net \
--to=paduille.4061.mumia.w+nospam@earthlink.net \
--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 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.