On 30.01.23 23:33, Karel Gardas wrote:
I'm debugging crash inside the select call from libbsd library. The code
comes from few days old RTEMS and few days old libbsd trees. My naive
configuration for the RTEMS is below.
The crash backtrace is:
_CPU_Fatal_halt (source=source@entry=9, error
Sorry, I'll make sure to avoid this going forward.
Kinsey
On Mon, Jan 30, 2023 at 5:41 PM Chris Johns wrote:
> On 31/1/2023 10:23 am, Kinsey Moore wrote:
> > On 1/30/2023 5:13 PM, Chris Johns wrote:
> >> Can the subject please be:
> >>
> >> dtc: Add patch to build for cygwin builds
> >>
> >> ?
On 31/1/2023 10:23 am, Kinsey Moore wrote:
> On 1/30/2023 5:13 PM, Chris Johns wrote:
>> Can the subject please be:
>>
>> dtc: Add patch to build for cygwin builds
>>
>> ?
>
> Unfortunately, Joel pushed this and a tools hash bump along with the other two
> patches, so that would require rewriting
On 1/30/2023 5:13 PM, Chris Johns wrote:
Can the subject please be:
dtc: Add patch to build for cygwin builds
?
Unfortunately, Joel pushed this and a tools hash bump along with the
other two patches, so that would require rewriting history.
Kinsey
_
Can the subject please be:
dtc: Add patch to build for cygwin builds
?
Chris
On 31/1/2023 4:30 am, Kinsey Moore wrote:
> This patch resolves a build error with dtc on cygwin until upstream
> adopts a fix.
> ---
> bare/config/devel/dtc-1.6.1-1.cfg | 3 +++
> 1 file changed, 3 insertions(+)
>
>
OK
Thanks
Chris
On 31/1/2023 9:55 am, Kinsey Moore wrote:
> Include paths must use the full file name with extension. This was
> causing errors because it couldn't resolve the include.
> ---
> bare/config/devel/gnu-default-tools.bset | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> d
OK
Thanks
Chris
On 31/1/2023 9:40 am, Kinsey Moore wrote:
> Github has changed the way it generates on-the-fly tarball requests
> which has changed the hashes of the resulting tarballs. This adjusts the
> affected tarball hashes as a stop-gap until a more permanent solution
> can be devised.
> --
Include paths must use the full file name with extension. This was
causing errors because it couldn't resolve the include.
---
bare/config/devel/gnu-default-tools.bset | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bare/config/devel/gnu-default-tools.bset
b/bare/config/devel/
Github has changed the way it generates on-the-fly tarball requests
which has changed the hashes of the resulting tarballs. This adjusts the
affected tarball hashes as a stop-gap until a more permanent solution
can be devised.
---
bare/config/devel/capstone-4.0.1-1.cfg| 2 +-
bare/conf
Hello,
I'm debugging crash inside the select call from libbsd library. The code
comes from few days old RTEMS and few days old libbsd trees. My naive
configuration for the RTEMS is below.
The crash backtrace is:
_CPU_Fatal_halt (source=source@entry=9, error=,
error@entry=604203640) at ..
OK to push
Thanks
Chris
On 31/1/2023 1:44 am, Joel Sherrill wrote:
> Closes #4555.
> ---
> rtems/config/5/rtems-aarch64.bset| 4
> rtems/config/5/rtems-all.bset| 2 --
> rtems/config/5/rtems-microblaze.bset | 3 ---
> rtems/config/5/rtems-tier-4.bset | 1 -
> 4 files changed
This patch resolves a build error with dtc on cygwin until upstream
adopts a fix.
---
bare/config/devel/dtc-1.6.1-1.cfg | 3 +++
1 file changed, 3 insertions(+)
diff --git a/bare/config/devel/dtc-1.6.1-1.cfg
b/bare/config/devel/dtc-1.6.1-1.cfg
index 54aed09..acf2cd8 100644
--- a/bare/config/deve
ok
On Mon, Jan 30, 2023 at 7:44 AM Joel Sherrill wrote:
>
> Closes #4555.
> ---
> rtems/config/5/rtems-aarch64.bset| 4
> rtems/config/5/rtems-all.bset| 2 --
> rtems/config/5/rtems-microblaze.bset | 3 ---
> rtems/config/5/rtems-tier-4.bset | 1 -
> 4 files changed, 10 dele
On Mon, Jan 30, 2023 at 8:33 AM Sebastian Huber
wrote:
>
>
>
> On 30.01.23 16:11, Gedare Bloom wrote:
> > Ping. I think we have now some patches and process to use
> > "Sponsored-By: ..." in commit messages. I can't find the guidance in
> > the docs.
>
> These are commits from third-party sources,
On 1/30/23 16:13, Gedare Bloom wrote:
On Fri, Jan 27, 2023 at 11:41 AM Karel Gardas wrote:
Sponsored-By: Precidata
---
No issue with the patch, but I think it is awkward to have this
"Sponsored-By" in an import patch.
Was also thinking about that. Whole work was sponsored including import
On 30.01.23 16:11, Gedare Bloom wrote:
Ping. I think we have now some patches and process to use
"Sponsored-By: ..." in commit messages. I can't find the guidance in
the docs.
These are commits from third-party sources, for example FreeBSD.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornie
ok to these two
On Thu, Jan 26, 2023 at 11:31 AM Kinsey Moore wrote:
>
> This resovles gcc warnings by updating to the latest Xilinx NAND
> controller driver.
> ---
> bsps/include/dev/nand/xnandpsu.h | 4 +++-
> bsps/include/dev/nand/xnandpsu_bbm.h | 2 +-
> bsps/include/dev/nand/xnandps
This looks ok to me, just need to address the import patches
On Fri, Jan 27, 2023 at 11:42 AM Karel Gardas wrote:
>
> The QSPI memory is initialized and used only when the BSP configure file
> sets QSPI memory size to non-zero value. Currently QSPI is run in memory
> mapped mode which allows futu
On Fri, Jan 27, 2023 at 11:41 AM Karel Gardas wrote:
>
> Sponsored-By: Precidata
> ---
No issue with the patch, but I think it is awkward to have this
"Sponsored-By" in an import patch.
> .../stm/Components/mt25tl01g/mt25tl01g.c | 1046 +
> .../stm/Components/mt25tl01g/mt2
On Fri, Oct 1, 2021 at 6:11 PM Chris Johns wrote:
>
> On 30/9/21 4:55 pm, Christian MAUDERER wrote:
> > Am 30.09.21 um 02:23 schrieb Chris Johns:
> >> On 29/9/21 6:38 pm, Christian MAUDERER wrote:
> >>> Am 29.09.21 um 02:40 schrieb Chris Johns:
> On 28/9/21 11:11 pm, Christian MAUDERER wrote:
This is OK. Not ideal, but consistent with the current code at least.
The commit message is a bit wrong since it also fixes sprintf() messages.
We should probably replace the sprintf with snprintf especially where
there is a string being used (prefix). The prefix is usually (always?)
32 byte arra
Closes #4555.
---
rtems/config/5/rtems-aarch64.bset| 4
rtems/config/5/rtems-all.bset| 2 --
rtems/config/5/rtems-microblaze.bset | 3 ---
rtems/config/5/rtems-tier-4.bset | 1 -
4 files changed, 10 deletions(-)
delete mode 100644 rtems/config/5/rtems-aarch64.bset
delete mod
Hello,
I'm looking at the filesystem options for RTEMS (on top of a 4GB eMMC
chip), but I need something that behaves properly in case of a sudden
power loss.
I probably missed something, but:
Regarding RFS, I found this:
https://lists.rtems.org/pipermail/users/2013-December/060969.html
i
Hello,
recently the following tickets were added (beneath a few more related ones):
https://devel.rtems.org/ticket/4790 - Setup Gitlab instance
https://devel.rtems.org/ticket/4791 - Update BuildBot
It's great that a patch review system and a CI/CD that builds every
patch for RTEMS starts to ge
24 matches
Mail list logo