1. 25 Nov, 2020 1 commit
  2. 20 Nov, 2020 1 commit
  3. 05 Feb, 2020 4 commits
  4. 29 Jan, 2020 8 commits
  5. 28 Jan, 2020 3 commits
  6. 27 Jan, 2020 1 commit
  7. 26 Jan, 2020 13 commits
    • Anthony DeRobertis's avatar
      Merge branch 'feature/18-ask-for-confirmation-before-proceeding' · 7be366b2
      Anthony DeRobertis authored
      Will now confirm if there is a keyboard present to respond on.
    • Anthony DeRobertis's avatar
      If there is a keyboard, prompt for confirmation. · 51f253ed
      Anthony DeRobertis authored
      If we detect a keyboard (something that claims you can press Y/N), then
      prompt for confirmation before wiping. Otherwise, proceed without
      Closes #18.
    • Anthony DeRobertis's avatar
      Script to detect presence of a keyboard. · 151d1aac
      Anthony DeRobertis authored
      Finally, something obvious progress towards #18. Use the input
      capabilities modules I just wrote to detect if there is a keyboard,
      defined as anything you can press Y and N on.
      Of course, it could be a barcode reader, but then I guess you can scan
      Y. Or it could be a Yubikey, in which case... I guess plug in a USB
    • Anthony DeRobertis's avatar
    • Anthony DeRobertis's avatar
      Capabilities is almost done. · 1f816ce2
      Anthony DeRobertis authored
      One surprise, it turns out Bit::Vector->contains errors out if we ask
      about a bit larger than the vector, instead of just returning 0. So
      protect against that. (And of course it only happened on 32-bit, since
      the size is always a multiple of the word size, so larger on 64-bit).
    • Anthony DeRobertis's avatar
      Input: put constants in own module. · 8316a628
      Anthony DeRobertis authored
      This is just much simpler going forward, and a lot less "magic"
      happening. Just put the autogenerated code in its own module, instead of
      the main one via trickery.
    • Anthony DeRobertis's avatar
      CONTRIBUTING: note author and t-data · 8e6a4e2a
      Anthony DeRobertis authored
      Add author and t-data to the code organization section.
    • Anthony DeRobertis's avatar
      Start of capabilities parsing. · bb3d1ea8
      Anthony DeRobertis authored
      This is mostly done, except the tests aren't (well, they aren't
      automated yet).
    • Anthony DeRobertis's avatar
      Sysfs input capabilities test data. · 6ae2a405
      Anthony DeRobertis authored
      The format differs between 32-bit and 64-bit Linux, unfortunately. So we
      have two sets of test data (one for each), and here is where it came
         - 64-bit: this comes from Watt, an actual machine.
         - 32-bit: from a qemu VM.
    • Anthony DeRobertis's avatar
      Unify KEY_ and BTN_. · 113f5799
      Anthony DeRobertis authored
      Both of these refer to bits in the capabilities/key file, no idea why
      they did that... but they did. So its easier if our reverse-lookup table
      combines them.
    • Anthony DeRobertis's avatar
      Sort some and add some section headers. · ffc5989c
      Anthony DeRobertis authored
      Easy enough to sort the EXPORT_OK and prototypes; the other two use each
      so I'd have to change it. Not sure if there is any reason to (other than
      reducing the diff size of generated code.)
    • Anthony DeRobertis's avatar
      Add prototypes; add strict. · 56df1652
      Anthony DeRobertis authored
      Need prototypes for Perl to know those are function calls (when one
      macro references another). Strict found this.
    • Anthony DeRobertis's avatar
      Auto-generate from <linux/input.h>. · 7a781825
      Anthony DeRobertis authored
      Going to do the work to actually parse the input capabilities, this will
      probably eventually become its own module. At least once someone
      processes my PAUSE ID request.
      This commit includes a Dist::Zilla plugin to do the work. I think its
      still simple enough to be safe from reinventing-h2xs syndrome. The
      Dist::Zilla plugin isn't included in the dist.
      CI config is a little funky because GitLab CI is running this with -o
      pipefail, so need to stop grep returning no output from failing the
  8. 25 Jan, 2020 2 commits
  9. 24 Jan, 2020 7 commits