From: Marcel Holtmann <marcel@holtmann.org>
To: Dan ABITBOL <d.abitbol@bloophone.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] CLASS OF DEVICE AND L2CAP INCOMING CONNECTION REQUESTS
Date: 29 Oct 2003 15:33:18 +0100 [thread overview]
Message-ID: <1067438006.24041.272.camel@pegasus> (raw)
In-Reply-To: <006c01c39e27$f3d324c0$0900a8c0@Silicium>
Hi Dan,
first of all, start sending emails without background images and don't
write the subject complete in upper cases. Some spam filter can kick you
away and I tend to delete such mails without reading it ;)
> 1/ get the class of device of the remote device when I accept an l2cap incoming connection request...
I already thought of this. First we should add a class of device field
to the kernel structure hci_conn. The HCI core layer must fill in the
correct values on HCI connection request events.
> 2/ and/or make a filter to allow l2cap incoming connections requests only from devices that have a specific class of device .
I don't have any real thought about this. Any comments from other
people?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2003-10-29 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 14:21 [Bluez-users] CLASS OF DEVICE AND L2CAP INCOMING CONNECTION REQUESTS Dan ABITBOL
2003-10-29 14:33 ` Marcel Holtmann [this message]
2003-10-29 15:07 ` Xavier Garreau
2003-10-29 15: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=1067438006.24041.272.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=d.abitbol@bloophone.com \
/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.