From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] L2CAP & HCI trace
Date: Tue, 22 Feb 2005 00:15:46 +0100 [thread overview]
Message-ID: <1109027746.7626.35.camel@pegasus> (raw)
In-Reply-To: <20050217111414.40743.qmail@web53202.mail.yahoo.com>
Hi Filipa,
> > Try recompilating your kernel with the
> > CONFIG_BT_HCI_SOCK_DEBUG, CONFIG_BT_L2CAP_DEBUG,
> > etc... (All the options
> > mentionned at the beginning of the files, in a block
> > like :
> >
> > #ifndef CONFIG_BT_L2CAP_DEBUG
> > #undef BT_DBG
> > #define BT_DBG(D...)
> > #endif
> >
> > ) enabled.
> I am a newbie in Linux/BlueZ matters and I am not sure
> how to do this. Could you please explain?
add a line with "#define CONFIG_BT_L2CAP_DEBUG" before this block and
recompile the module.
> By the way, does anybody has the l2cap and hci layers
> implemented im User Space? I need to have those layers
> running without OS...
Actually it is possible to do this, but you are on the wrong mailing
list for this question ;)
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://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-21 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 15:57 [Bluez-devel] L2CAP & HCI trace Filipa Duarte
2005-02-16 16:12 ` zze-COLBUS Emmanuel RD-MAPS-GRE
2005-02-17 11:14 ` Filipa Duarte
2005-02-21 23:15 ` 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=1109027746.7626.35.camel@pegasus \
--to=marcel@holtmann.org \
--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.