public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-users] hidp and connecting
@ 2004-05-14 13:24 Michal Semler
  2004-05-14 17:44 ` Marcel Holtmann
  0 siblings, 1 reply; 4+ messages in thread
From: Michal Semler @ 2004-05-14 13:24 UTC (permalink / raw)
  To: bluez-users

Hi Marcel,

when hidd is not started and device wants connect, system prints errors about 
unknown connections.

1) Maybe we should have somewhere in /etc/bluetooth list of allowed devices 
which will be accepted without hidd runnnig?

2) When hidp and other modules compiled directly into kernel, we should under 
single mode allow all hid devices to connect without hidd running to allow 
users maintain their system without any daemons running

Michal


-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-users] hidp and connecting
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Marcel Holtmann @ 2004-05-14 17:44 UTC (permalink / raw)
  To: cijoml; +Cc: BlueZ Mailing List

Hi Michal,

> when hidd is not started and device wants connect, system prints errors about 
> unknown connections.

what kind of errors are you talking about? You must be more specific.

> 1) Maybe we should have somewhere in /etc/bluetooth list of allowed devices 
> which will be accepted without hidd runnnig?

Why should we accept a device when hidd is not running?

> 2) When hidp and other modules compiled directly into kernel, we should under 
> single mode allow all hid devices to connect without hidd running to allow 
> users maintain their system without any daemons running

This is impossible. If you need this, you have to go with Bluetooth
dongles that implement HID proxy.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-users] hidp and connecting
  2004-05-14 17:44 ` Marcel Holtmann
@ 2004-05-14 21:43   ` Michal Semler
  2004-05-14 22:09     ` Marcel Holtmann
  0 siblings, 1 reply; 4+ messages in thread
From: Michal Semler @ 2004-05-14 21:43 UTC (permalink / raw)
  To: bluez-users

On Friday 14 of May 2004 19:44, Marcel Holtmann wrote:
> Hi Michal,
>
> > when hidd is not started and device wants connect, system prints errors
> > about unknown connections.
>
> 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
etc...

>
> > 1) Maybe we should have somewhere in /etc/bluetooth list of allowed
> > devices which will be accepted without hidd runnnig?
>
> Why should we accept a device when hidd is not running?

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.

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.

>
> > 2) When hidp and other modules compiled directly into kernel, we should
> > under single mode allow all hid devices to connect without hidd running
> > to allow users maintain their system without any daemons running
>
> This is impossible. If you need this, you have to go with Bluetooth
> dongles that implement HID proxy.

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.

>
> Regards
>
> Marcel

Michal


-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-users] hidp and connecting
  2004-05-14 21:43   ` Michal Semler
@ 2004-05-14 22:09     ` Marcel Holtmann
  0 siblings, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2004-05-14 22:09 UTC (permalink / raw)
  To: cijoml; +Cc: BlueZ Mailing List

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-05-14 22:09 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox