From: Marcel Holtmann <marcel@holtmann.org>
To: Guennadi Liakhovetski <gl@dsa-ac.de>
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] [REGRESSION] last working kernel 2.6.18
Date: Tue, 07 Aug 2007 18:05:20 +0200 [thread overview]
Message-ID: <1186502720.20129.64.camel@violet> (raw)
In-Reply-To: <Pine.LNX.4.63.0708071754160.8578@pcgl.dsa-ac.de>
Hi Guennadi,
> > as mentioned multiple times in the past, the "hcitool cc" is not a
> > general purpose command. Nobody needs to create an ACL link. The kernel
> > does this for you in the background and you should let the kernel do its
> > job. It has to be the kernel since it has to track these connections and
> > the users of it. Unused ACL links will be disconnected. Period.
> >
> > There are simply no excuses for creating low-level ACL links and there
> > is absolutely no need for it at all.
>
> Thanks, Marcel. Just, what I thought:-) It would've saved us a few minutes
> of typing and a few electrons shifted around the world if this was
> documented somewhere:-) Would be great, if someone could, for example,
> document it in the wiki. I DID look there, and I didn't find anything.
> Which means, either it is not there, or not everybody is able to find it
> there within a reasonable amount of time:-)
the documentation in various online articles is wrong. For some reason
people think that "hciool cc" is a good idea. It has always been a debug
command for developers. Nothing more, nothing less. The mailing list is
full of responses from me about it.
However the wiki is for everybody. Feel free to update it.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-08-07 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 15:07 [Bluez-users] [REGRESSION] last working kernel 2.6.18 Guennadi Liakhovetski
2007-08-07 15:25 ` Guennadi Liakhovetski
2007-08-07 15:32 ` Marcel Holtmann
2007-08-07 15:56 ` Guennadi Liakhovetski
2007-08-07 16:05 ` 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=1186502720.20129.64.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=gl@dsa-ac.de \
/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