1. 12 Oct, 2011 1 commit
    • Dima Zavin's avatar
      minui: add ability to synchronize current key state · 441031da
      Dima Zavin authored
      
      If a key is down prior to the time of initialization, we would not get the
      down event for the key, and thus think that the key is not pressed.
      
      Add an interface that allows one to provide a callback to execute
      on all keys that are currently down.
      
      Change-Id: I2a4096c0cb4c7c7a9a80d207835f168a0b418413
      Signed-off-by: default avatarDima Zavin <dima@android.com>
      441031da
  2. 02 Sep, 2011 2 commits
    • Dima Zavin's avatar
      minui: events: add ability to poll on non-input fds · 36583673
      Dima Zavin authored
      
      Change-Id: Iad52a6f2adcae0068d252d6163586f9d7b93121d
      Signed-off-by: default avatarDima Zavin <dima@android.com>
      36583673
    • Dima Zavin's avatar
      minui: events: refactor event acquisition · bc29063b
      Dima Zavin authored
      
      Events are now delivered through a callback mechanism during
      a call to ev_dispatch(). This will allow us to extend the events
      code to handle other devices/fds, not just input. One such example
      is the ability to process uevents.
      
      During initialization, we provide an input callback to ev_init
      that gets called when a new event is encountered during dispatch.
      
      ev_get has been removed and replaced with ev_get_input() helper
      function that can be called from inside the callback to attempt
      to get an input event.
      
      The existing client of ev_get in recovery has been split up such
      that the input thread just calls ev_wait(); ev_dispatch(); and
      the input_callback handles individual events by using the
      ev_get_input() helper.
      
      Change-Id: I24d8e71bd1533876b4ab1ae751ba200fea43c049
      Signed-off-by: default avatarDima Zavin <dima@android.com>
      bc29063b
  3. 30 Aug, 2011 2 commits
  4. 13 Nov, 2009 1 commit
  5. 11 Jun, 2009 1 commit
    • Doug Zongker's avatar
      split out device-specific recovery UI code into vendor directories · ddd6a286
      Doug Zongker authored
      Take some device-specific details of the recovery UI (eg, what keys to
      press to bring up the interface and perform actions, exact text of the
      menu, etc.) and split them out into separate C functions.  Arrange to
      take implementations of those functions from the appropriate vendor
      directory at build time.  Provide a default implementation in case no
      vendor-specific one is available.
      ddd6a286
  6. 04 Mar, 2009 2 commits
  7. 21 Oct, 2008 1 commit