From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hidp and connecting
Date: Sat, 15 May 2004 00:09:40 +0200 [thread overview]
Message-ID: <1084572580.24119.16.camel@pegasus> (raw)
In-Reply-To: <200405142343.04831.cijoml@volny.cz>
Hi Michal,
> > what kind of errors are you talking about? You must be more specific.
>
> hci_acldata_packet: hci0 ACL packet for unknown connection handle 41
> hci_acldata_packet: hci0 ACL packet for unknown connection handle 42
show us the hcidump -x for this reconnect, because it must be a problem
in the Bluetooth core. What does /proc/bluetooth/l2cap show?
> Why not? If kernel knows them via list specified in some config by root, hidd
> should be used only for connecting a new one and killling them.
The HIDP module is not able to accept or create new connections and
actually how should the kernel get the HID report descriptor? We don't
have a kernel SDP client implementation and I will never accept such
stuff. Look at the SDP specification and you will understand why.
> It reminds me, that --kill option kills connection, but device can reconnect.
> Maybe should be implemented option, which will kill device and it will not be
> allowed to reconnect.
The --unplug option is on my list, but I haven't had time to put it in
this release. The kernel already supports the virtual cable unplug.
> Why? After connecting I can kill hidd and devices works. So if under single
> mode will not be control for bdaddr and unknown connections, it should be
> possible to work too.
Same argument as above. A userspace daemon must accept the connection
and it has to retrieve the needed SDP records.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-05-14 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 13:24 [Bluez-users] hidp and connecting Michal Semler
2004-05-14 17:44 ` Marcel Holtmann
2004-05-14 21:43 ` Michal Semler
2004-05-14 22:09 ` 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=1084572580.24119.16.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=cijoml@volny.cz \
/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