hal: Branch 'master' - 2 commits

Danny Kukawka danny.kukawka at web.de
Mon Apr 23 14:43:23 PDT 2007


On Montag, 23. April 2007, David Zeuthen wrote:
> diff-tree 192f5284c77846f4537209fde4a945f7d2159eee (from
> f849652ff11b22b8685c9bd4728e8eb2299a4c96) Author: Luiz Augusto von Dentz
> <luiz.dentz at gmail.com>
> Date:   Mon Apr 23 15:25:35 2007 -0400
>
>     recognize bluetooth network capabilities
>
>     This is fd.o #10577
>
>     http://bugs.freedesktop.org/show_bug.cgi?id=10577
[...]
> diff --git a/hald/linux/probing/probe-net-bluetooth.c
> b/hald/linux/probing/probe-net-bluetooth.c new file mode 100644
> index 0000000..2abaa70
> --- /dev/null
> +++ b/hald/linux/probing/probe-net-bluetooth.c

Would it not make more sence that the bluez package would provide the prober 
and HAL would provide a infrastructure to allow other packages to attach a 
prober to the device detection (maybe in this case a addon/callout would also 
work, not complete sure about this atm)?

If there is not really a need to do this in the probing the bluez daemon could 
listen to hal and set the needed keys automatically as networkmanager should 
(as we discussed in the past - I know this is not implemented yet, but it 
should) set information back to HAL.

This would prevent to start a prober if the needed bluez daemon is not 
installed in the system. 

Danny


More information about the hal mailing list