This project is mirrored from The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 10 Jun, 2009 1 commit
  2. 03 Jun, 2009 2 commits
    • Johannes Berg's avatar
      rfkill: create useful userspace interface · c64fb016
      Johannes Berg authored
      The new code added by this patch will make rfkill create
      a misc character device /dev/rfkill that userspace can use
      to control rfkill soft blocks and get status of devices as
      well as events when the status changes.
      Using it is very simple -- when you open it you can read
      a number of times to get the initial state, and every
      further read blocks (you can poll) on getting the next
      event from the kernel. The same structure you read is
      also used when writing to it to change the soft block of
      a given device, all devices of a given type, or all
      This also makes CONFIG_RFKILL_INPUT selectable again in
      order to be able to test without it present since its
      functionality can now be replaced by userspace entirely
      and distros and users may not want the input part of
      rfkill interfering with their userspace code. We will
      also write a userspace daemon to handle all that and
      consequently add the input code to the feature removal
      In order to have rfkilld support both kernels with and
      without CONFIG_RFKILL_INPUT (or new kernels after its
      eventual removal) we also add an ioctl (that only exists
      if rfkill-input is present) to disable rfkill-input.
      It is not very efficient, but at least gives the correct
      behaviour in all cases.
      Signed-off-by: Johannes Berg's avatarJohannes Berg <>
      Acked-by: Marcel Holtmann's avatarMarcel Holtmann <>
      Signed-off-by: default avatarJohn W. Linville <>
    • Johannes Berg's avatar
      rfkill: rewrite · 19d337df
      Johannes Berg authored
      This patch completely rewrites the rfkill core to address
      the following deficiencies:
       * all rfkill drivers need to implement polling where necessary
         rather than having one central implementation
       * updating the rfkill state cannot be done from arbitrary
         contexts, forcing drivers to use schedule_work and requiring
         lots of code
       * rfkill drivers need to keep track of soft/hard blocked
         internally -- the core should do this
       * the rfkill API has many unexpected quirks, for example being
         asymmetric wrt. alloc/free and register/unregister
       * rfkill can call back into a driver from within a function the
         driver called -- this is prone to deadlocks and generally
         should be avoided
       * rfkill-input pointlessly is a separate module
       * drivers need to #ifdef rfkill functions (unless they want to
         depend on or select RFKILL) -- rfkill should provide inlines
         that do nothing if it isn't compiled in
       * the rfkill structure is not opaque -- drivers need to initialise
         it correctly (lots of sanity checking code required) -- instead
         force drivers to pass the right variables to rfkill_alloc()
       * the documentation is hard to read because it always assumes the
         reader is completely clueless and contains way TOO MANY CAPS
       * the rfkill code needlessly uses a lot of locks and atomic
         operations in locked sections
       * fix LED trigger to actually change the LED when the radio state
         changes -- this wasn't done before
      Tested-by: default avatarAlan Jenkins <>
      Signed-off-by: Henrique de Moraes Holschuh <> [thinkpad]
      Signed-off-by: Johannes Berg's avatarJohannes Berg <>
      Signed-off-by: default avatarJohn W. Linville <>
  3. 10 Oct, 2007 2 commits
  4. 07 May, 2007 1 commit