Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Jan 20, 2023
    • Tom Rini's avatar
      CI: Make check for new defined CONFIG symbols even more robust · a03efb6f
      Tom Rini authored 
      
Now that all remaining in-tree cases where we define or undef a CONFIG
symbol have been migrated to Kconfig or renamed to CFG we can make the
CI check more robust. We will exclude the doc, tools and arch/arm/dts
directories from this check as they are special cases. Further, we can
exclude the scripts/kconfig/lkc.h and include/linux/kconfig.h files as
the CONFIG values they define are special tooling cases and not real
symbols.

In the case of docs, the only places that currently fail this test are
old documentation that should be rewritten so that we can remove this
special case.

Signed-off-by: default avatarTom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      a03efb6f
  3. Jan 13, 2023
  5. Jan 11, 2023
  7. Dec 23, 2022
  9. Dec 06, 2022
  11. Nov 24, 2022
  13. Nov 22, 2022
  15. Oct 17, 2022
  17. Oct 07, 2022
  19. Sep 02, 2022
  21. Aug 31, 2022
  23. Aug 22, 2022
    • Tom Rini's avatar
      CI: Move to Ubuntu 2022.04 "Jammy" for CI base · b6d4e085
      Tom Rini authored 
      
- We now have a new enough sbsigntools in the distro, stop building.
- Use the 20220801 tag for Jammy.
- Move to pygit2 1.9.2 (current version) as the old one doesn't build on
 "Jammy".
- Add the working directory to the list of safe directories for git.
- Move to pytest 6.2.5 to address other issues.
- This move exposed a number of minor issues in the existing scripts we
  used within CI to perform the jobs themselves.  The most notable changes
  here involve using 'set +e / set -e' to enforce when we should or should
  not make non-zero buildman status be a fatal error.

Signed-off-by: default avatarTom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      b6d4e085
  25. Aug 05, 2022
  27. Jul 06, 2022
  29. May 02, 2022
  31. Apr 15, 2022
  33. Apr 01, 2022
  35. Mar 25, 2022
  37. Mar 18, 2022
    • Tom Rini's avatar
      CI: Fix unmigrated symbol test · 576eac85
      Tom Rini authored 
      
When calling comm to compare the CONFIG symbols a defconfig uses with
the symbols that have been migrated, we need to suppress all output as
the summary line will have everything we need.  Failure to do this leads
to the test blowing up, but in non-fatal ways.

Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      576eac85
  39. Mar 15, 2022
  41. Mar 02, 2022
  43. Feb 03, 2022
  45. Jan 28, 2022
  47. Jan 13, 2022
  49. Dec 27, 2021
  51. Nov 14, 2021
  53. Oct 21, 2021
  55. Oct 14, 2021
  57. Sep 30, 2021
  59. Sep 24, 2021
    • Kristian Amlie's avatar
      ARM: vexpress_ca9x4: Reintroduce board in order to use with QEMU. · 15e30106
      Kristian Amlie authored and Tom Rini's avatar Tom Rini committed 
      
vexpress_ca9x4 is seemingly the only board except for qemu_arm which
is able to run U-Boot correctly, using the `-M vexpress-a9` option to
QEMU. Building for qemu_arm and running qemu-system-arm with the `-M
virt` argument has a number of downsides, most importantly that it
only supports virtio storage drivers. This significantly reduces its
usefulness in testing memory card and Flash solutions, especially when
the tested images are from a third party source.

So therefore we reintroduce the vexpress_ca9x4 board in this commit,
with the explicit goal of using it with QEMU.

A number of differences to note from the original:

* Since the board was apparently unmaintained, I have now set myself
  as the maintainer.

* The board has been converted to use the driver model, which was the
  reason it was removed in the first place.

* The vexpress_ca15_tc2 and vexpress_ca5x2 boards, which were removed
  in the same commit, are not necessary for the QEMU use case, and
  have been omitted.

* An `mmc0` alias was introduced in the dts file. The mmc is not
  detected correctly without this, now that it's based on the device
  tree instead of the board's init function.

* A couple of other nodes were removed because they were problematic
  when trying to run the UEFI bootmgr. Once again, the primary use
  case here is QEMU, and these nodes are not needed for that to work.

* Unnecessary board init code has been removed, thanks to driver model
  and device tree.

* `CONFIG_OF_EMBED` has been enabled. I know this goes against
  recommended practice, but there doesn't seem to be any other way to
  pass the dtb to U-Boot in the QEMU scenario. Using the -dtb argument
  does not work, I suppose because U-Boot doesn't use the same
  mechanics as the kernel when it's booting.

* Load addresses have been changed to fit QEMU use case.

People wanting to get a more detailed, yet somewhat isolated, diff
between this and the original, can run this command:

  git diff c6c26a05~1 -- \
      $( git diff-tree --diff-filter=A -r --name-only HEAD~1 HEAD)

(Make sure to either check out this commit first, or replace HEAD with
the commit ID of this commit)

Signed-off-by: default avatarKristian Amlie <kristian.amlie@northern.tech>
      15e30106
  61. Sep 11, 2021
  63. Aug 04, 2021
  65. Jul 07, 2021
    • Tom Rini's avatar
      Azure/GitLab: Move to gcc-11.1.0 and LLVM-11 · 7bb1cc3b
      Tom Rini authored 
      - Move to gcc-11.1.0 builds from kernel.org for supported platforms and
  LLVM-11 for those tests.
- As Heinrich has noted, the RISC-V platform specification has a profile
  OS-A for running rich operating systems like Linux and BSD. This profile
  requires 64bit and UEFI conforming to the EBBR. Only the 'embedded'
  profile may use 32bit.  Given this, drop grub for 32bit RISC-V as it no
  longer compiles with gcc-11.1 and upstream is unlikely to fix it:
  https://www.mail-archive.com/grub-devel@gnu.org/msg30736.html


- Update to grub-2.06 release to address other issues of building with
  gcc-11.1.
- Update to newer Xtensa (gcc-9.2.0) and ARC (gcc-10.2) toolchains

Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Bin Meng <bmeng.cn@gmail.com>
Cc: Simon Glass <sjg@chromium.org>
Cc: Rick Chen <rick@andestech.com>
Signed-off-by: default avatarTom Rini <trini@konsulko.com>
Reviewed-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
      7bb1cc3b
  67. Jul 05, 2021
  69. May 26, 2021
  71. May 25, 2021
    • Daniel Schwierzeck's avatar
      MIPS: remove deprecated qemu_mips board · 5308a71d
      Daniel Schwierzeck authored 
      
Remove qemu_mips boards because DM migration doesn't make sense.
The board support for qemu_mips is already marked as deprecated
in Qemu in favour of the Malta board. Also qemu_mips support
has been removed from Linux a long time ago.

The official replacement is the Malta board. The same Malta U-Boot
image can be used with Qemu and on physical hardware.
All combinations of Big Endian and Little Endian as well as 32 bit
and 64 bit are supported.

Signed-off-by: Daniel Schwierzeck's avatarDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
      5308a71d
  73. Apr 29, 2021
  75. Apr 10, 2021

Imprint & Privacy Policy