Skip to content
Snippets Groups Projects
  1. Dec 19, 2022
  2. Dec 10, 2022
  3. Dec 09, 2022
  4. Dec 08, 2022
  5. Dec 06, 2022
  6. Dec 05, 2022
  7. Nov 30, 2022
  8. Nov 29, 2022
  9. Nov 28, 2022
  10. Nov 21, 2022
  11. Nov 18, 2022
    • GitBot's avatar
      Integrate linux-imx-kuk/dual-espresso_custom-poweroff · c38b4f25
      GitBot authored
      --
      
      Commit: seco-ne/kernel/linux-imx-kuk@65760c59
      
      dts:dual-espresso: Add custom poweroff routine
      
      The power off routine monitors the PW_FAIL24V# signal. If the 24V
      are active or become active again while the system is in the custom
      power off routine, a restart is triggered.
      
      BCS 746-001083
      
      --
      
      Commit: seco-ne/kernel/linux-imx-kuk@858faf2e
      
      drivers:psci: Add possibility to skip the assignment of pm_power_off
      
      Since we need a custom poweroff routine for the dual-espresso project,
      pm_power_off must be assigned to a special function. pm_power_off is
      assigned to psci_sys_poweroff by default. Added a devicetree property
      that allows to skip the assignment of pm_power_off to avoid a potential
      race condition.
      
      BCS 746-001083
      
      --
      
      Commit: seco-ne/kernel/linux-imx-kuk@f005841e
      
      drivers:power: Add a custom poweroff module for dual-espresso
      
      The module monitors a gpio state and calls the kernel restart
      handler when the gpio has a specific state. This done by assigning a
      the monitor routine to the pm_power_off function pointer. In this way,
      the monitoring starts as the last step of a shutdown -P call.
      Devicetree properties:
      * init-delay-ms: Set an initial delay until the monitoring is started
      * monitor-delay-ms: Poll delay of the gpio
      
      BCS 746-001083
      c38b4f25
  12. Nov 11, 2022
  13. Nov 10, 2022
    • GitBot's avatar
      Integrate linux-guf/cherry-pick-seco-logo · 7fb80753
      GitBot authored
      --
      
      Commit: seco-ne/kernel/linux-guf@a14e669b
      
      logo: Removed duplicate of seco boot logo
      
      A duplicate of the seco logo was present in the logos dir.
      
      (cherry picked from commit 348ae9ef8e5439fa62a2d9eceae008bdd5d96348)
      
      --
      
      Commit: seco-ne/kernel/linux-guf@0c15fefb
      
      logo: Enable SECO and FnG logo by default
      
      Both logos need to be enabled by default. The logo that is added to the
      kernel is picked through the defconfig and the override in the kernel
      include file.
      
      (cherry picked from commit 4dd7c7bbba066a73d06fcafe091e7a46454560d8)
      
      --
      
      Commit: seco-ne/kernel/linux-guf@3991915e
      
      logo: Added fngsystem boot logo
      
      Cherry-pick from af765e15
      
      (cherry picked from commit e03aff3ac82c5aadaa1b755f80074c90a57accda)
      
      --
      
      Commit: seco-ne/kernel/linux-guf@8c6557ad
      
      logo: Added SECO and EDGEHOG logo
      
      Updated the seco logo from the marketing's eps file.
      
      (cherry picked from commit fa277d894d440a993ff24cb93f1a5c94b91fb102)
      (cherry picked from commit a70c95c0bac3db1cb2d5c750232bdd2cef634527)
      7fb80753
  14. Nov 08, 2022
  15. Nov 07, 2022
  16. Nov 04, 2022
  17. Nov 01, 2022
  18. Oct 28, 2022
  19. Oct 27, 2022
  20. Oct 24, 2022
  21. Oct 21, 2022
  22. Oct 20, 2022
  23. Oct 18, 2022
    • GitBot's avatar
      Integrate gitlab-ci/add-hide-ftp-upload-flag · fa96bdbb
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@a5e27f6e
      
      FTP upload: Add flag to hide FTP upload stage
      
      This is a workaround to prevent customer releases being uploaded to our
      public FTP area. It should be removed as soon as we support uploading to
      different FTP target folders.
      fa96bdbb
    • GitBot's avatar
      Integrate gitlab-ci/add-release-suffix and 3 more · c64f4a0f
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@543a2170
      
      manifest_package: add release suffix
      
      Customer specific manifest projects can now set the RELEASE_SUFFIX
      variable, which then gets appended to the deployment folder names.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@c763c43f
      
      alphaplan_fwr: change variable "release_name_local" to "release_name"
      
      Otherwise it can be assumed that it might be correlated with
      outputdir_local, which is not the case.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d8d26a5
      
      package_release: more refactoring
      
      - Make output-dir an argument that can be passed multiple times instead
        of hard-coding two dirs with certain meanings.
      - Remove LOCALDIR variable from package.env, because it is not used
        anywhere (only occurence was job class ".uploadsdkftp" which wasn't
        used anywhere either).
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc3698c8
      
      package_release: refactoring
      
      Improve readability of package_release.py and its submodule
      generate_release_metadata.py.
      
      - Add describing comments throughout the file.
      - Remove duplicate code from functions. Simplify them, so that they do
        what their names say (and nothing more).
      - Rename variables and function arguments to make their purpose clearer.
      - Harmonize variable names with their corresponding command line arguments.
      - Add pydoc for functions.
      - Add type declarations to function arguments.
      - Generate MD5 and metadata files in the source directories so that they
        can be copied along with the rest of the files.
      c64f4a0f
  24. Oct 12, 2022
  25. Oct 10, 2022
  26. Sep 28, 2022
    • GitBot's avatar
      Integrate uboot-imx-kuk/ram-size-from-fuses · 49c47495
      GitBot authored
      --
      
      Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@36e07a27
      
      trizeps8plus/mc3: Add fuse decoding for RAM size
      
      The code to readout the fuses that define the installed RAM size have
      not been implemented for trizeps8plus. Merged the related code from
      trizeps8mini into the trizeps8plus board file and adapted the defines
      to use 1GB Ram without fuses, used for MC3.
      
      The PHYS_RAM_SIZE define is now set to 3GB as this is also used to
      define the RAM mapping, where 3GB is addressable.
      
      BCS 746-001065
      fngsystem/30.1
      49c47495
  27. Sep 27, 2022
Loading