From: Filipa Duarte <filipa_duarte@yahoo.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] L2CAP & HCI trace
Date: Thu, 17 Feb 2005 03:14:14 -0800 (PST) [thread overview]
Message-ID: <20050217111414.40743.qmail@web53202.mail.yahoo.com> (raw)
In-Reply-To: <1108570362.11909.35.camel@g-necml5-146.rd.francetelecom.fr>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1937 bytes --]
Hi
Many thanks for your help.
--- zze-COLBUS Emmanuel RD-MAPS-GRE
<emmanuel.colbus@rd.francetelecom.com> wrote:
> Le mercredi 16 février 2005 à 07:57 -0800, Filipa
> Duarte a écrit :
> > Hi,
> >
> > I suppose that this is a quite stupid question but
> I
> > would like to know how can I have the same kind of
> > trace as Victor had (in the end of the e-mail)?
> >
> > The reason why is that I would like to identify
> which
> > are the functions (like l2cap_sock_sendmsg,
> > l2cap_chan_send, hci_send_acl, etc) used to send
> data
> > on the l2cap/hci layers. Could anyone give me any
> > direction to find this?
> >
> > Many thanks,
> >
> > Filipa
> >
>
> Hello,
>
> 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?
>
> I've not tried it myself, but, reading to the code,
> I think it will
> work.
>
> Emmanuel Colbus
By the way, does anybody has the l2cap and hci layers
implemented im User Space? I need to have those layers
running without OS...
Cheers,
Filipa
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
-------------------------------------------------------
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-17 11:14 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 [this message]
2005-02-21 23:15 ` Marcel Holtmann
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=20050217111414.40743.qmail@web53202.mail.yahoo.com \
--to=filipa_duarte@yahoo.com \
--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