Mailinglist Archive: opensuse-bugs (14887 mails)
| < Previous | Next > |
[Bug 302539] NetworkManager: permanently send NameOwnerChanged and poll HAL
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 12 Sep 2007 07:04:12 -0600 (MDT)
- Message-id: <20070912130412.8F822CC789@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=302539#c3
--- Comment #3 from JP Rosevear <jpr@xxxxxxxxxx> 2007-09-12 07:04:12 MST ---
(In reply to comment #2 from Danny Kukawka)
> There is no such feature in the upstream SVN trunk as far as I can see. And as
> it currently workit's really better to drop the feature.
Its in the 0.6.x branch only currently, it has not been forward ported because
of all the changes going on in trunk.
> HAL can't send a signal since HAL don't get an info if this change. At least
> also because this all differ from machine to machine. There is no common sysfs
> interface for killshwitch.
>
> NetworkManager could do on ThinkPads the following:
> 1) check initial the status of WLAN/Killswitch
> 2) listen to HAL for ButtonPressed=killswitch event
> 3) call GetPower()
>
> Something like that also for Dell (and other) machines (if it doesn work:
> report it):
> 1) check initial the status of WLAN/Killswitch
> 2) listen on the input device for the keyboard for KEY_WLAN (keycode: 238)
> 3) call GetPower()
Isn't this the type of abstraction hal should deal with?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
--- Comment #3 from JP Rosevear <jpr@xxxxxxxxxx> 2007-09-12 07:04:12 MST ---
(In reply to comment #2 from Danny Kukawka)
> There is no such feature in the upstream SVN trunk as far as I can see. And as
> it currently workit's really better to drop the feature.
Its in the 0.6.x branch only currently, it has not been forward ported because
of all the changes going on in trunk.
> HAL can't send a signal since HAL don't get an info if this change. At least
> also because this all differ from machine to machine. There is no common sysfs
> interface for killshwitch.
>
> NetworkManager could do on ThinkPads the following:
> 1) check initial the status of WLAN/Killswitch
> 2) listen to HAL for ButtonPressed=killswitch event
> 3) call GetPower()
>
> Something like that also for Dell (and other) machines (if it doesn work:
> report it):
> 1) check initial the status of WLAN/Killswitch
> 2) listen on the input device for the keyboard for KEY_WLAN (keycode: 238)
> 3) call GetPower()
Isn't this the type of abstraction hal should deal with?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |