Re: [PATCH 1/7] bsps: Remove unused memcpy() implementations

Thank you for these changes, I have one small question ... On 12/03/2018 21:25, Sebastian Huber wrote: > Update #3285. The patch makes sense once I looked up the ticket. Would it be possible to have in the body of the commit message: Reorganize BSP source directory Update #3285. ? If I have

[PATCH] libfs/jffs2: Force the inode size to a non-zero value if a directory.

Set the inode size to 256 to work around a newlib scandir check where a directory has to have a non-zero size to work. Set the size to greater than 24 bytes, a small dirent size so the allocator in scandir works. The newlib scandir code should be updated to a more recent scandir from FreeBSD

[PATCH 2/3] Add ARM Paravirtualization support

Closes #3305. --- cpukit/score/cpu/arm/cpu_asm.S | 3 +- cpukit/score/cpu/arm/headers.am| 1 + cpukit/score/cpu/arm/include/rtems/score/cpu.h | 9 +++ .../score/cpu/arm/include/rtems/score/paravirt.h | 75 ++ 4 files changed, 87

[PATCH 0/3] Updated Paravirtualization Series

Hi I have reworked the paravirtualization series per everyone's suggestions. I have tested on arm, x86, and powerpc using Deos as the host environment. For now, ARM thread Id register access is disabled because: (1) Deos does not even context switch so us touching it is questionable. (2) RTEMS

[PATCH 1/3] Rework i386 Paravirtualization to have paravirt.h

--- cpukit/score/cpu/i386/cpu.c| 2 +- cpukit/score/cpu/i386/headers.am | 1 + cpukit/score/cpu/i386/include/rtems/score/cpu.h| 5 +- .../cpu/i386/include/rtems/score/interrupts.h | 2 +- .../score/cpu/i386/include/rtems/score/paravirt.h |

[PATCH 3/3] Add PowerPC paravirtualization support

Cannot read or write MSR when executing in user mode. This is used when RTEMS_PARAVIRT is defined. Provide alternate methods to disable/enable interrupts Closes #3306. --- c/src/lib/libcpu/powerpc/new-exceptions/cpu.c | 10 ++- c/src/lib/libcpu/powerpc/new-exceptions/cpu_asm.S | 16 +

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 3:20 PM, Gedare Bloom wrote: > On Mon, Mar 12, 2018 at 12:41 PM, Amaan Cheval > wrote: > > On Mon, Mar 12, 2018 at 9:53 PM Gedare Bloom wrote: > > > >> On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber > >>

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 12:41 PM, Amaan Cheval wrote: > On Mon, Mar 12, 2018 at 9:53 PM Gedare Bloom wrote: > >> On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber >> wrote: >> > On 10/03/18 18:02, Amaan Cheval wrote:

[PATCH] Added Getentropy() support to beagle BSP

So, It looks like here's the final patch, do let me know if its ready to be pushed. Also, it would be really helpful if someone else also tests this patch before pushing(Although i have done that once). Thanks, Udit agarwal >From 454a8ff3e0ea3393818859874705a54b098c6081 Mon Sep 17 00:00:00 2001

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 9:53 PM Gedare Bloom wrote: > On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber > wrote: > > On 10/03/18 18:02, Amaan Cheval wrote: > >> > >> - Improve RTEMS SMP[3] > >> > >> What kinds of improvements to SMP are we

Re: [PATCH] secondpatch

Thanks Salil, Add yourself to the devel.rtems.org wiki "proposal tracking table" if you haven't yet done so at the GSOC 2018 page. Did you send your screenshot to me or to Joel already? if not, please do so. Gedare On Mon, Mar 12, 2018 at 7:30 AM, salil0907 wrote: >

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber wrote: > On 10/03/18 18:02, Amaan Cheval wrote: >> >> - Improve RTEMS SMP[3] >> >> What kinds of improvements to SMP are we considering? > > > The SMP support is quite complete now. In general, an independent

Re: getentropy() implementation on BBB

Udit, See if you can find a 2-clause BSD boilerplate to copy from in the RTEMS already. The one you got seems to have some minor typesetting problems with whitespace issues. It is fine to include stdint.h in the am335x.h if needed, so you can keep the TRNG definitions at that header, which makes

[PATCH] bsp/atsam: Allow setting the drive strength.

This adds a simple function for setting the PIO drive strength. --- bsps/arm/atsam/include/libchip/include/pio.h | 2 ++ .../lib/libbsp/arm/atsam/libraries/libchip/source/pio.c | 16 2 files changed, 18 insertions(+) diff --git

Re: devel Digest, Vol 76, Issue 39

Hi Salil, Have you subscribed newlib mailing list? You need to build newlib for some BSPs. Here, You can clone newlib: git clone git://sourceware.org/git/newlib-cygwin.git For more information about newlib, go through this link: https://sourceware.org/newlib/ Since you have to port the code

Re: [PATCH 1/3] i386/smp: Define unused CPU_Interrupt_frame to fix compiler error

On Mar 12, 2018 7:40 AM, "Amaan Cheval" wrote: Agreed. I'll look into fixing CPU_Interrupt_frame up as time permits. If you get it to compile before addressing the context switch synchronization point, one thought is to put an ifdef RTEMS_SMP with a #error where the fix

Re: [PATCH 1/3] i386/smp: Define unused CPU_Interrupt_frame to fix compiler error

Agreed. I'll look into fixing CPU_Interrupt_frame up as time permits. Appreciate the help and follow-ups, thanks! On Mon, Mar 12, 2018 at 6:06 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 12/03/18 13:32, Amaan Cheval wrote: > > I originally sent this patch with the

Re: [PATCH 1/3] i386/smp: Define unused CPU_Interrupt_frame to fix compiler error

On 12/03/18 13:32, Amaan Cheval wrote: I originally sent this patch with the intent of merely ridding the i386 targets of compiler errors, for anyone interested in looking into SMP issues on the arch. Do you believe that I should look into fixing i386's incomplete SMP context-switch support for

Re: [PATCH 1/3] i386/smp: Define unused CPU_Interrupt_frame to fix compiler error

Brilliant, thanks a ton! That should keep me occupied for a bit. I originally sent this patch with the intent of merely ridding the i386 targets of compiler errors, for anyone interested in looking into SMP issues on the arch. Do you believe that I should look into fixing i386's incomplete SMP

Re: [PATCH 1/3] i386/smp: Define unused CPU_Interrupt_frame to fix compiler error

On 12/03/18 13:13, Amaan Cheval wrote: Hey! Thanks for the guidance! I did look at cpu_asm.S, but I don't quite get how Interrupt_frame is being used, where by "used" I mean it in the sense that fields within it are being set to the actual register values, the way they are with stm/ltm for the

Re: [PATCH 1/3] i386/smp: Define unused CPU_Interrupt_frame to fix compiler error

Hey! Thanks for the guidance! I did look at cpu_asm.S, but I don't quite get how Interrupt_frame is being used, where by "used" I mean it in the sense that fields within it are being set to the actual register values, the way they are with stm/ltm for the Context_Control structure. The reason

[PATCH] secondpatch

From: salil0907 --- testsuites/samples/hello/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c index 6c4f475b1a..522f793d39 100644 --- a/testsuites/samples/hello/init.c +++

[PATCH 5/7] bsps/arm: Move libcpu content to bsps

Update #3285. --- .../arm920/mmu.c => bsps/arm/shared/arm920-mmu.c | 0 c/src/lib/libbsp/arm/csb336/Makefile.am| 2 +- c/src/lib/libbsp/arm/csb336/make/custom/csb336.cfg | 1 - c/src/lib/libbsp/arm/csb337/Makefile.am| 2 +-

[PATCH 7/7] sparc64: Move libcpu content to cpukit

Update #3285. --- c/src/lib/libbsp/sparc64/niagara/Makefile.am | 4 - .../libbsp/sparc64/niagara/make/custom/niagara.cfg | 4 - c/src/lib/libbsp/sparc64/usiii/Makefile.am | 4 - .../lib/libbsp/sparc64/usiii/make/custom/usiii.cfg | 4 - c/src/lib/libcpu/sparc64/Makefile.am

[PATCH 6/7] sparc: Move libcpu content to cpukit

Update #3285. --- bsps/sparc/headers.am | 4 --- c/src/lib/libbsp/sparc/erc32/Makefile.am | 5 c/src/lib/libbsp/sparc/erc32/make/custom/erc32.cfg | 1 - c/src/lib/libbsp/sparc/leon2/Makefile.am | 5

[PATCH 1/7] bsps: Remove unused memcpy() implementations

Update #3285. --- c/src/lib/libcpu/lm32/Makefile.am | 18 --- c/src/lib/libcpu/lm32/configure.ac | 35 - c/src/lib/libcpu/lm32/shared/misc/memcpy.c | 21 - c/src/lib/libcpu/nios2/Makefile.am | 18 ---

[PATCH 4/7] bsps/mips: Move libcpu content to bsps

Update #3285. --- .../mips/shared/irq}/installisrentries.c | 0 .../mips/shared/irq}/isr_entries.S | 0 .../mips => bsps/mips/shared}/timer/gettime.S | 0 .../libcpu/mips => bsps/mips/shared}/timer/timer.c | 0 c/src/lib/libbsp/mips/csb350/Makefile.am

[PATCH 2/7] bsps: Remove unused RTEMS_CPU_MODEL

Update #3285. --- c/src/lib/libbsp/lm32/lm32_evr/make/custom/lm32_evr.cfg| 1 - c/src/lib/libbsp/lm32/milkymist/make/custom/milkymist.cfg | 1 - c/src/lib/libbsp/m32c/m32cbsp/make/custom/m32csim.cfg | 1 - c/src/lib/libbsp/moxie/moxiesim/make/custom/moxiesim.cfg | 3 +--

[PATCH 3/7] bsps/mips: Remove Mongoose-V README

--- c/src/lib/libcpu/mips/mongoosev/README | 56 -- 1 file changed, 56 deletions(-) delete mode 100644 c/src/lib/libcpu/mips/mongoosev/README diff --git a/c/src/lib/libcpu/mips/mongoosev/README b/c/src/lib/libcpu/mips/mongoosev/README deleted file mode 100644

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On 10/03/18 18:02, Amaan Cheval wrote: - Improve RTEMS SMP[3] What kinds of improvements to SMP are we considering? The SMP support is quite complete now. In general, an independent review is required, but this is probably not a GSoC project. Some areas in the implementation are a bit too

Re: [PATCH 1/3] i386/smp: Define unused CPU_Interrupt_frame to fix compiler error

On 10/03/18 15:11, Amaan Cheval wrote: CPU_INTERRUPT_FRAME_SIZE needs to also be set to allow the RTEMS_STATIC_ASSERT in percpuasm.c to be fulfilled. The CPU_Interrupt_frame must properly defined. It must be used by the SMP context switch code (which is incomplete for i386). Please have a

Re: no-preinstall: Ready to merge

Hello Amaan, On 11/03/18 13:27, Amaan Cheval wrote: The docs haven't been updated to reflect the new "bootstrap -H" option, even on master[1], by the way. It seems like "./bootstrap -p" has been replaced with "./bootstrap -g" followed by "./bootstrap -H". Is that right? The "./boostrap -p"