Re: [PATCH v3 1/3] bsps/microblaze: Allow copying FDT from U-Boot

On Mon, Apr 10, 2023 at 9:25 PM Chris Johns wrote: > > On 10/4/2023 1:47 pm, Alex White wrote: > > .../microblaze_invalidate_dcache_range.S | 104 ++ > > Why not provide the RTEMS cache API and use that? Hi Chris, Good catch. It would be ideal to provide the existing RTEMS c

[PATCH] print/texinfo: Add texinfo package

From: Chris Johns - MacOS systems do not come with makeinfo - Fix the internal build logic. There was config logic in a bset file that does not support logic operators. Use a special tmp internal path to isolate the internal tools. --- bare/config/print/texinfo-7.0.3.cfg | 12 +++

[PATCH v2 2/2] bsps/powerpc: Fix warnings with PPC_SPECIAL_PURPOSE_REGISTER

From: Chris Johns - This change avoids the GCC extension of blocks in expressions that ISO forbids and is warned about with the pedantic warnings option. --- bsps/powerpc/include/libcpu/powerpc-utility.h | 42 ++- .../powerpc/shared/exceptions/ppc_exc_print.c | 25 ++-

[PATCH v2 1/2] bsps/motorola_powerpc: Change defines from BSP names to avoid clash

From: Chris Johns - Change mvme2100 to mot_pcc_mvme2100 to avoid clashing with the RTEMS_BSP value for the BSP. You cannot have a define that is the BSP name or the RTEMS_BSP name will be the define. --- bsps/mips/include/bsp/i8259.h | 2 +- bsps/powerpc/motorola_po

Re: [PATCH 2/2] bsps/powerpc: Fix warnings with PPC_SPECIAL_PURPOSE_REGISTER

On 11/4/2023 10:29 pm, Joel Sherrill wrote: > Anything to add to the message beyond "fix" to explain this patch? :) > > I think the software engineering guide uses a comment similar to this as an > anti-pattern. Lol How about: - This change avoids the GCC extension of blocks in expressions that

Re: [PATCH 1/2] bsps/motorola_powerpc: Change defines from BSP names to avoid clash

On 11/4/2023 10:44 pm, Joel Sherrill wrote: > On Tue, Apr 11, 2023, 12:00 AM mailto:chr...@rtems.org>> > wrote: > > From: Chris Johns mailto:chr...@rtems.org>> > > - Change mvme2100 to mot_pcc_mvme2100 to avoid clashing with the >   RTEMS_BSP value for the BSP. You cannot have a defi

Re: [PATCH v2] docs/user: add docs for riscv/kendrytek210 BSP variant

Looks good - I generated the HTML and PDF versions. Thanks, Alan On Tue, Apr 11, 2023 at 5:05 PM Joel Sherrill wrote: > Sorry. I didn't realise there were that many revisions and when I searched > my inbox I missed it > > I reverted V2 and applied V6. Hopefully ok now > > On Tue, Apr 11, 2023, 2

Re: [PATCH v2] docs/user: add docs for riscv/kendrytek210 BSP variant

Sorry. I didn't realise there were that many revisions and when I searched my inbox I missed it I reverted V2 and applied V6. Hopefully ok now On Tue, Apr 11, 2023, 2:54 PM Alan Cudmore wrote: > Sorry, meant to reply to the list too.. I think you pushed v2 of my patch. > I was up to v6 that fix

Re: [PATCH v2] docs/user: add docs for riscv/kendrytek210 BSP variant

Sorry, meant to reply to the list too.. I think you pushed v2 of my patch. I was up to v6 that fixed a bunch of issues. What is the best way to fix this? Rewind, or I can submit a new patch based on this. Thanks, Alan On Tue, Apr 11, 2023, 2:29 PM Joel Sherrill wrote: > Pushed. Thanks. > > Pleas

Re: [PATCH v2] docs/user: add docs for riscv/kendrytek210 BSP variant

Pushed. Thanks. Please check that it looks good to you. --joel On Fri, Mar 31, 2023 at 11:15 AM Alan Cudmore wrote: > This patch adds the documentation for building and running RTEMS on the > Kendryte K210 > RISC-V SoC. The generic riscv introducion was re-arranged to list the > multilib varia

Re: Ping for docs/user risc-v doc update

I'm running errands but will push this for you when I get home. On Tue, Apr 11, 2023, 9:28 AM Alan Cudmore wrote: > I think it's in pretty good shape: > https://lists.rtems.org/pipermail/devel/2023-April/074845.html > I did not wrap the existing console sections, but I used line wrap to > format

Ping for docs/user risc-v doc update

I think it's in pretty good shape: https://lists.rtems.org/pipermail/devel/2023-April/074845.html I did not wrap the existing console sections, but I used line wrap to format the other paragraphs to be 80 chars or less. I also updated the hardcoded RTEMS versions to use macros. Thanks, Alan ___

Re: [PATCH 1/2] bsps/motorola_powerpc: Change defines from BSP names to avoid clash

On Tue, Apr 11, 2023, 12:00 AM wrote: > From: Chris Johns > > - Change mvme2100 to mot_pcc_mvme2100 to avoid clashing with the > RTEMS_BSP value for the BSP. You cannot have a define that is the > BSP name. > --- > bsps/mips/include/bsp/i8259.h | 4 ++-- > bsps/pow

Re: [PATCH 2/2] bsps/powerpc: Fix warnings with PPC_SPECIAL_PURPOSE_REGISTER

Anything to add to the message beyond "fix" to explain this patch? :) I think the software engineering guide uses a comment similar to this as an anti-pattern. Lol On Tue, Apr 11, 2023, 12:00 AM wrote: > From: Chris Johns > > --- > bsps/powerpc/include/libcpu/powerpc-utility.h | 40 ++

Re: [PATCH] gdb-common: Fix the python-config library parsing

Thanks for the quick fix. I tested here and indeed this fixes the reported issue. Karel On 4/11/23 08:03, chr...@rtems.org wrote: From: Chris Johns Closes #4894 --- source-builder/config/gdb-common-1.cfg | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source-b