On 14/9/2022 5:02 pm, chr...@rtems.org wrote:
> From: Chris Johns
> diff --git a/bare/config/textproc/gsed-internal.bset
> b/bare/config/textproc/gsed-internal.bset
> new file mode 100644
> index 000..e93e1a5
> --- /dev/null
> +++ b/bare/config/textproc/gsed-internal.bset
> @@ -0,0 +1,12 @@
Probing a SDIO/SDHCI interface that has been disabled by system init via
holding it in reset can cause a CPU hang. This prevents probing of
devices that have been disabled in such a manner on ZynqMP systems.
---
rtemsbsd/sys/dev/sdhci/arasan_sdhci.c | 25 +
1 file changed,
Hi,
There is a bug in this change. I will sort it out today.
Sorry about this.
Chris
On 14/9/22 5:02 pm, chr...@rtems.org wrote:
> From: Chris Johns
>
> - This is a bug introduced in the recent bset tar file changes
> ---
> source-builder/sb/setbuilder.py | 3 ++-
> 1 file changed, 2
Hello Chris,
our CI build the tools (rtems-source-builder git) for revision
c0edd80bcd27b3dad7ee7acf5ea129e81e6a6f64 "rtems/jpeg: Update the checksum"
OK and failed for revision
468fc79e8c7c8076e8b65be82ba2009e41dd6c8e "devel/gcc: Check and build GNU
sed if not available on build host"
On 15/9/22 9:21 pm, Frank Kühndel wrote:
> Hello Chris,
>
> our CI build the tools (rtems-source-builder git) for revision
>
> c0edd80bcd27b3dad7ee7acf5ea129e81e6a6f64 "rtems/jpeg: Update the checksum"
>
> OK and failed for revision
>
> 468fc79e8c7c8076e8b65be82ba2009e41dd6c8e "devel/gcc: