On Saturday 12 April 2008, Henrique de Moraes Holschuh wrote:I disagree Most rfkill hw keys are attached to the device. So I can plug wifi, wimax, 3G, UWB and BT dongles (or cards) into a system and they each provide a HW switch (or should provide). If each overrides another one, we have a problem. Is it that unlikely that a device will have 3G and WiMAX support? Not really. My laptop might have WWAN built in and then when I travel to some place where I need WiMAX, I plug a WiMAX USB dongle. Problem. This is just an example that can be extended to any wireless technology combination. My point is we should keep it kind of separated, where the guy requesting the rfkill stuff says "I need a keycode to generate when my hw switch is operated". And for the rfkill layer to just care about associating that keycode to that card. I guess before I didn't have it as clear as I do now, but I am just seeing more and more that each radio has its own kill switch and then the system might have a generic one (for example fn+F5 on thinkpads) for killing all of them at the same time. -- Inaky --
| Ingo Molnar | [bug] block subsystem related crash with latest -git |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Adrian Bunk | Re: net/ipv4/fib_trie.c - compile error (Re: 2.6.23-rc3-mm1) |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
