1. 21 Dec, 2020 1 commit
    • Julius Werner's avatar
      image: Expand kernel buffer size to 512MB · 1af4a350
      Julius Werner authored
      
      
      This patch expands the kernel buffer to 512MB (or to 128MB on arm32
      devices where that's the Linux ABI limit anyway, or to less on some
      older specialty platforms where it otherwise wouldn't fit). The kernel
      partition size on disk has traditionally only been 16MB, and we don't
      plan on changing that... however, on a recovery USB stick we can make
      the partition as large as we want, and we may need to do that if we want
      to add more stuff to the recovery initramfs. Unfortunately we'll be
      stuck with the exisiting limits on old platforms since recovery firmware
      is not updateable, but this CL is meant to ensure that we'll at least
      have lots of headroom to grow on future platforms.
      
      Some memory layouts had to be adjusted to fit the new buffer. Also
      document the individual arch-dependent constraints for placing various
      regions in the Kconfig help (some of these only apply to older Linux
      versions, but since we don't update our kernels it's better to mention
      everything that might apply... boards can still violate them after they
      made sure that they're unaffected).
      
      BRANCH=None
      BUG=chromium:873135
      TEST=Booted Cheza (not feasible to test *every* platform, I've
      double-checked everything manually as best as I could).
      
      Change-Id: I23f1a2c78f4e82c1f1e4a16d823ab36d2e90ef1d
      Signed-off-by: default avatarJulius Werner <jwerner@chromium.org>
      Reviewed-on: https://chromium-review.googlesource.com/1179122
      
      Reviewed-by: default avatarAaron Durbin <adurbin@chromium.org>
      1af4a350
  2. 21 Oct, 2016 1 commit
  3. 20 Jul, 2016 1 commit
    • Aseda Aboagye's avatar
      cros_ec: Change keyboard scanning method. · f88af26b
      Aseda Aboagye authored
      
      
      The Matrix KeyBoard Protocol (MKBP) was recently extended to support
      reporting button and switch events. Consequently, support for the
      EC_CMD_MKBP_GET_STATE host command was dropped since the keyboard FIFO
      became a general MKBP events FIFO and that host command assumed that the
      FIFO was strictly for keyboard matrices.  This has been superseded by the
      EC_CMD_GET_NEXT_EVENT host command.
      
      Currently, button and switch events may be present in the FIFO, but we
      will just ignore those and drop them on the floor.  For those buttons
      and switches that we care about, they are handled in different ways.
      
      This commit introduces a new Kconfig:
      
          CONFIG_DRIVER_INPUT_MKBP_OLD_COMMAND
      
      This config option should be used to enable retrieving of key matrix
      changes via EC_CMD_MKBP_GET_STATE. This is for legacy Chrome ECs where
      the MKBP FIFO was solely just a key matrix FIFO.
      
      BUG=chromium:626863
      BRANCH=None
      TEST=Verify that keypresses are recognized during FW screens on kevin.
      TEST=Verify that button presses and other events are ignored during FW
      screens on kevin.
      
      CQ-DEPEND=CL:358926
      
      Change-Id: Ia9cf29b063178b9eca20e9d2602dc91308e56d4a
      Signed-off-by: default avatarAseda Aboagye <aaboagye@google.com>
      Reviewed-on: https://chromium-review.googlesource.com/358989
      
      
      Commit-Ready: Aseda Aboagye <aaboagye@chromium.org>
      Tested-by: default avatarAseda Aboagye <aaboagye@chromium.org>
      Reviewed-by: default avatarJulius Werner <jwerner@chromium.org>
      f88af26b
  4. 09 May, 2016 1 commit
  5. 04 May, 2016 1 commit
  6. 31 Aug, 2015 1 commit
    • Julius Werner's avatar
      veyron: Unify identical mainboards · f1843827
      Julius Werner authored
      
      
      This patch removes a lot of code duplication between the virtually
      identical Veyron Chromebook variants by merging the code into a single
      directory and handling the different names solely within Kconfig. This
      also allows us to easily add all the other Chromebook variants that have
      only been kept in the firmware branch to avoid cluttering ToT too much.
      
      The only effective change this will have (actually already the previous
      patch) is that we lose Pinky's quirky compatible string revision number
      calculation. Since nobody uses Pinky anymore and the kernel device
      tree's have long been removed from the kernel repository, I doubt anyone
      will care.
      
      Leaving all non-Chromebook boards as they are for now since they often
      contain more extensive differences.
      
      BRANCH=None
      BUG=None
      TEST=Booted Jerry.
      
      Change-Id: I75c972cb96c545f0251a4225859c494ad6204a4f
      Signed-off-by: default avatarJulius Werner <jwerner@chromium.org>
      Reviewed-on: https://chromium-review.googlesource.com/296062
      
      Reviewed-by: default avatarAaron Durbin <adurbin@chromium.org>
      f1843827
  7. 21 Jan, 2015 1 commit
  8. 16 Dec, 2014 1 commit
  9. 09 Dec, 2014 1 commit
  10. 21 Nov, 2014 1 commit
  11. 09 Oct, 2014 1 commit
  12. 01 Oct, 2014 1 commit
  13. 12 Sep, 2014 2 commits
  14. 09 Sep, 2014 1 commit
  15. 04 Sep, 2014 6 commits