1. 01 Jul, 2017 3 commits
  2. 24 Jun, 2017 4 commits
  3. 21 Jun, 2017 1 commit
  4. 12 Jun, 2017 1 commit
  5. 08 Jun, 2017 1 commit
  6. 14 May, 2017 1 commit
  7. 07 May, 2017 1 commit
  8. 16 Apr, 2017 1 commit
  9. 20 Mar, 2017 1 commit
  10. 10 Mar, 2017 1 commit
  11. 07 Mar, 2017 1 commit
  12. 05 Mar, 2017 2 commits
    • Jörg Krause's avatar
      board: add support for Banana Pro · 0ad1067d
      Jörg Krause authored
      
      
      The board support package includes the following components:
       - U-Boot 2016.11
       - Linux 4.9.3
       - packages:
         - alsa-utils for basic audio usage of the on-board headphone jack
           and microphone
         - iw and wpa_supplicant for managing the wireless interface
      
      Two Linux patches are necessary to enable audio and wifi support. Both
      patches are fetched from the Linux next branch and are probably mainlined in
      Linux 4.11.
      
      A Linux configuration fragment enables the wireless device driver, which
      is not enabled by default in the mainline defconfig of the board.
      
      The wifi chip needs a NVRAM configuration file which is provided in the
      rootfs overlay.
      Signed-off-by: default avatarJörg Krause <joerg.krause@embedded.rocks>
      [Thomas: remove e2fsprogs from the target packages, add entry in
      DEVELOPERS file, remove C++ support.]
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      0ad1067d
    • Arnout Vandecappelle's avatar
      Add gitlab-CI support · 4f863d77
      Arnout Vandecappelle authored
      The buildroot repository is now mirrored on
      https://gitlab.com/buildroot.org/buildroot so we can use Gitlab-CI to
      test Buildroot. Gitlab-CI is controlled by a .gitlab-ci.yml file
      that exists in the repository.
      
      For now, the only test is building all defconfigs (inspired on
      https://travis-ci.org/buildroot/buildroot-defconfig-testing/
      
      ). Since
      all the defconfigs have to be specified in the .gitlab-ci.yml file,
      we generate the file based on .gitlab-ci.yml.in. The generated
      .gitlab-ci.yml file has to be committed into the repository, though,
      otherwise Gitlab-CI doesn't see it. So there is also a test to verify
      that .gitlab-ci.yml is up-to-date.
      
      Building all the defconfigs takes a long time. Gitlab-CI will do that
      every time it pulls from git.buildroot.org, which is once per hour.
      That is way too often. Therefore, the defconfigs are not built on pull,
      but only on explicit trigger through the API or when a tag is added.
      Signed-off-by: default avatarArnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
      [Thomas:
       - fix typo not -> no
       - add LC_ALL=C when calling 'ls -1' to get a predictable order of the
         defconfigs
       - regenerate .gitlab-ci.yml.]
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      4f863d77