1. 02 6月, 2009 1 次提交
    • D
      UBI: add notification API · 0e0ee1cc
      Dmitry Pervushin 提交于
      UBI volume notifications are intended to create the API to get clients
      notified about volume creation/deletion, renaming and re-sizing. A
      client can subscribe to these notifications using 'ubi_volume_register()'
      and cancel the subscription using 'ubi_volume_unregister()'. When UBI
      volumes change, a blocking notifier is called. Clients also can request
      "added" events on all volumes that existed before client subscribed
      to the notifications.
      
      If we use notifications instead of calling functions like 'ubi_gluebi_xxx()',
      we can make the MTD emulation layer to be more flexible: build it as a
      separate module and load/unload it on demand.
      
      [Artem: many cleanups, rework locking, add "updated" event, provide
       device/volume info in notifiers]
      Signed-off-by: NDmitry Pervushin <dpervushin@embeddedalley.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      0e0ee1cc
  2. 18 5月, 2009 3 次提交
  3. 20 2月, 2009 1 次提交
  4. 27 1月, 2009 1 次提交
  5. 18 1月, 2009 8 次提交
  6. 28 12月, 2008 1 次提交
  7. 05 9月, 2008 1 次提交
  8. 24 7月, 2008 6 次提交
  9. 21 6月, 2008 1 次提交
  10. 03 2月, 2008 1 次提交
  11. 25 1月, 2008 4 次提交
  12. 27 12月, 2007 9 次提交
  13. 18 7月, 2007 3 次提交