build(deps): bump docker/build-push-action from 5 to 6 #265
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Add release notes for 12.4.0 release Signed-off-by: Alin Jerpelea <[email protected]>
- boots from eNVM - uses lim memory for RAM - has console on uart 0 - has procfs enabled - has most of nsh commands enabled Signed-off-by: Jukka Laitinen <[email protected]>
- Change git repository urls to point to our tiiuae repos for nuttx & nuttx apps - Remove most of the the build steps, leave just arm-12 and riscv; arm-12 has a build for stm32f7, and riscv for mpfs Signed-off-by: Jukka Laitinen <[email protected]>
…ptimized version in tiiuae repo Signed-off-by: Jukka Laitinen <[email protected]>
…iver to re-initialize on rx timeout If the interface is UP, and no packets are received in 30s, re-initialize the interface by calling the already implemented mpfs_txtimeout_expiry. This is a temporary workaround for a bug where IF might be UP and working but packets can only be transmitted. Receive side just doesn't work at all. The original bug can be re-produced easily by disconnecting and reconnecting the ethernet cable while the IF is up. Signed-off-by: Jukka Laitinen <[email protected]>
SD-card clock speed is just forced to 50MHz. Note that to be correct, one should first set the SD-card into high-speed mode, but currently NuttX doesn't support this. With our cards, just setting the interface to 50MHz seems to work fine, and it removes the issue with 25MHZ clock causing disturbance on GPS bands. Typically cards which support high-speed mode just work with 50MHz interface clock. This patch should be reverted when the NuttX supports high-speed mode, and we can properly set it. Signed-off-by: Jukka Laitinen <[email protected]>
Signed-off-by: Jukka Laitinen <[email protected]>
…ootloader This removes the need to have all the DDR/clock configuration related "LIBERODEFS" flags defined, when not building a standalone/coldboot configuration All of this code is unused when not building with CONFIG_MPFS_BOOTLOADER Signed-off-by: Jukka Laitinen <[email protected]>
This is not the correct way to do this, but it gives a nice perf. boost
Disable macOS builds for now.
All other commands are disabled in send_recv(). Signed-off-by: Jani Paalijarvi <[email protected]>
…ef and forward declare devif_loopback Signed-off-by: Jukka Laitinen <[email protected]>
Signed-off-by: Jukka Laitinen <[email protected]>
… that takes care of the need for loopback
Enable LINUX_ON_HART4 in rpmsg-ch2 defconfig of ICICLE board. Remove LINUX_ON_HART4 config from rpmsg-ch1 defconfig of ICICLE board.
Fix build warning when CONFIG_STM32F7_AUTONEG is not set Signed-off-by: Jukka Laitinen <[email protected]>
…ved IO area in protected build Signed-off-by: Jukka Laitinen <[email protected]>
Signed-off-by: Jukka Laitinen <[email protected]>
Signed-off-by: Jukka Laitinen <[email protected]>
Just a temporary patch, need to implement some kind of scalable solution for this. It might be a good idea to map something else for the user to avoid using ecall to enter the kernel for simple reads ? Also, increase the L3 table size
There is no make step executed for this directory before the Kconfigure, so all Kconfig's just need to be in-tree Signed-off-by: Jukka Laitinen <[email protected]>
Signed-off-by: Jukka Laitinen <[email protected]>
sendfifo() function need enable BWR_IE before checking if BWE is enabled to avoid BWE to be activated between the BWE check and BWR interrupt enabling, which causes the interrupt to be missed and Data Timeout error.
This adds a driver for i.MX93 ENET1 MAC block Signed-off-by: Jukka Laitinen <[email protected]>
The L2 table was not connected -> results in random crashes. Also add missing data sync barrier to the end.
Signed-off-by: Jani Paalijarvi <[email protected]>
Signed-off-by: Jani Paalijarvi <[email protected]>
Defining fat_dma_alloc(s) as imx9_dma_alloc(s) causes compiler errors. Signed-off-by: Jani Paalijarvi <[email protected]>
Fix a bug which causes that 1-bit mode is always selected. This happens even if the driver sets SDIO_CAPS_4BIT capability in case of the card and the host support 1- and 4-bit wide bus. Signed-off-by: Jani Paalijarvi <[email protected]>
SPI TX_DONE interrupt can be received after a semaphore timeout, but before interrupts are disabled. This will leave the semaphore to the signaled state. After a timeout the semaphore is always reset to non-signaled state to fix this race condition. Signed-off-by: Tero Salminen <[email protected]>
MPFS_I2C_ST_STOP_SENT interrupt might be received right after semaphore timeout, which would cause the semaphore to be in the incorrect signaled state when the next transfer starts. Signed-off-by: Tero Salminen <[email protected]>
include/nuttx/tls.h:52:4: warning: #warning CONFIG_TLS_NELEM is not defined [-Wcpp]
52 | # warning CONFIG_TLS_NELEM is not defined
| ^~~~~~~
In file included from include/nuttx/sched.h:48,
from include/nuttx/arch.h:87,
from include/nuttx/userspace.h:35,
from include/nuttx/mm/mm.h:30,
from include/nuttx/kmalloc.h:34,
from sim_bringup.c:33:
include/nuttx/tls.h:52:4: warning: #warning CONFIG_TLS_NELEM is not defined [-Wcpp]
52 | # warning CONFIG_TLS_NELEM is not defined
| ^~~~~~~
Signed-off-by: chao an <[email protected]>
…_ram and _esbi_ram The original names are confusing; the symbols' addresses point to the start and end of the sbi executable ram area. This may also reside in l2lim and not in ddr, depending on the configuration, and this is defined in the linker script. Signed-off-by: Jukka Laitinen <[email protected]>
Add partition parsing logic to emmcsd and support for configuring either CDCACM alone or both CDCACM and USBMCS for composite mode. Signed-off-by: Jukka Laitinen <[email protected]>
putreg32() arguments were swapped. Signed-off-by: Eero Nurkkala <[email protected]>
This provides means to run NuttX completely in EL3. This may be useful with NuttX based bootloaders that are executed from OCRAM. Instead of SPL/U-boot combo, NuttX may replace SPL completely. Signed-off-by: Eero Nurkkala <[email protected]>
Currently MMU supports only EL1. Introduce EL3 support as well. Signed-off-by: Eero Nurkkala <[email protected]>
Value 1021, when read from ICC_IAR0_EL1 means: "The GIC returns this value in response to a read of ICC_IAR0_EL1 or ICC_HPPIR0_EL1 at EL3, to indicate that the interrupt being acknowledged is one which is expected to be handled at Non-secure EL1 or EL2. This INTID is only returned when the PE is executing at EL3 using AArch64 state, or when the PE is executing in AArch32 state in Monitor mode." When this happens: - FIQ is fired on group0 - IRQ is pending at group1 So simply check and handle the interrupt. In short, this provides interrupt support for EL3. Signed-off-by: Eero Nurkkala <[email protected]>
This provides a capable bootloader that may be run from OCRAM. The OCRAM contains regions that are always zero, so the linker file avoids those with best effort. iMX9 infrastructure expects: - 0x20480000 (Start of OCRAM, AHAB) - 0x2049a000 (NuttX or SPL) - 0x204e0000 (ARM Trustzone, not used) When started from SD-card, the offsets are: - 0x1f000 with AHAB - 0xa000 without AHAB Signed-off-by: Eero Nurkkala <[email protected]>
Search and replace ARCH_BOOT_EL3 with more generic ARCH_ARM64_EXCEPTION_LEVEL that holds the EL level in an integer variable. Signed-off-by: Eero Nurkkala <[email protected]>
The size must be power-of-two according to the the PMP spec. Signed-off-by: Jani Paalijarvi <[email protected]>
The size must be power-of-two for NAPOT according to the the PMP spec. Signed-off-by: Jani Paalijarvi <[email protected]>
This reverts commit e8bbaf6.
Verify that GMAC RX/TX buffers are 64 byte aligned
Return from exception is common code for both system calls and exceptions
Also, convert the type to union; we don't need the list element once the item has been popped from the free list (the linkage is never needed when the item is in use).
This patch changes how user service calls are executed: Instead of using the common interrupt logic, execute the user service call directly. Why? When a user makes a service call request, all of the service call parameters are already loaded into the correct registers, thus it makes no sense to first clobber them and then reload them, which is what the old logic does. It is much more effective to run the system call directly. During a user system call the interrupts must be re-enabled, which the new logic does as soon as we know the exception is a user service call request. This patch does NOT change the behavior of reserved system calls (like switch_context), only the user service call request is affected.
Check return value of mpfs_board_pmp_setup() and jump to mpfs_board_pmp_error() in case of error. Signed-off-by: Jani Paalijarvi <[email protected]>
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5 to 6. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v5...v6) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps docker/build-push-action from 5 to 6.
Release notes
Sourced from docker/build-push-action's releases.
Commits
31159d4Merge pull request #1149 from docker/dependabot/npm_and_yarn/docker/actions-t...07e1c3echore: update generated contentf7febd6chore(deps): Bump@docker/actions-toolkitfrom 0.26.2 to 0.27.0f6010eaMerge pull request #1147 from docker/dependabot/npm_and_yarn/docker/actions-t...c0a6b96chore: update generated content0dfe9c3chore(deps): Bump@docker/actions-toolkitfrom 0.26.1 to 0.26.294f8f8cMerge pull request #1142 from docker/dependabot/npm_and_yarn/docker/actions-t...22f4433chore: update generated content6721c56chore(deps): Bump@docker/actions-toolkitfrom 0.26.0 to 0.26.14367da9Merge pull request #1140 from docker/dependabot/github_actions/docker/bake-ac...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)