LIST OF IO BENCHMARKS

mented the process on my blog <http://81.4.107.225/wordpress/index.php/2018/05/17/microsd-card-benchmarking-on-beaglebone-black/> . Regards, Udit Agarwal ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: LIST OF IO BENCHMARKS

io-benchmarks-fio-iozone-and-bonnie/> is the comparison. > > The GPLv2 is not a problem for test suites / benchmarks. It is only a > problem for code that should get merged into the rtems.git. > > Gedare > > On Thu, May 17, 2018 at 5:20 AM, Udit agarwal <dev.mada.

Query regarding disk cache in RTEMS

Hi all, I was looking at the internal working of a benchmark and the way it disables cache for direct IO operations, needed to benchmark storage device drivers. I have a small query regarding how cache is organized in RTEMS: Usually data transfer model is something like: Application address space

Re: LIST OF IO BENCHMARKS

ogger(here <http://nerdyclap.blogspot.in/>). (There are some alignment issues after exporting, mainly due to the custom CSS i was using, i'll fix that ASAP) Regards, Udit Agarwal On Sun, May 20, 2018 at 7:32 PM, Joel Sherrill <j...@rtems.org> wrote: > > > > > > On S

Compiler error with U_FORTIFY_SOURCE, D_FORTIFY_SOURCE options

e compiler opts are raising these error? Also, FIO needs a BSP independent method for determining the size of RAM for it's internal working. I'm unable to figure out any such implementation. Any help on this too, would be great. Regards, Udit agarwal ___ devel m

Re: Query regarding disk cache in RTEMS

On Fri, May 18, 2018 at 11:17 PM, Gedare Bloom <ged...@rtems.org> wrote: > Udit, > > On Thu, May 17, 2018 at 9:13 AM, Udit agarwal <dev.mada...@gmail.com> > wrote: > > Hi all, > > I was looking at the internal working of a benchmark and the way it > disa

[GSoC] Status update: Adding IO Benchmark to RTEMS

overs. Immediate goal after this is to get the generated code merged upstream to fio's main repository, i'm working on that, but that can move in parallel with phase 2 objectives. Regards, Udit AGarwal ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] beagle: Disable WiFi if libbsd is build without it.

Hi, Thanks, that patch worked perfectly. Wifi is now, by default disabled. Regards, Udit agarwal On Wed, May 30, 2018 at 5:04 PM, Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > Update #3351. > --- > rtemsbsd/include/bsp/nexus-devices.h | 3 +++ >

Invalid block size of 512B while setting up RFS on RAMDisk

Hi list, While setting up RFS with a block size of 512B on a RAMDisk, I had an I/O error while formatting /dev/rda using mkrfs shell command. Same procedure repeated for RFS on sd-card/USB-stick did worked with 512B block size. Any advice or a fix? BTW, my ramdisk block size is 512B with block

Re: getentropy() implementation on BBB

335x.h to bbb_getentropy.c . since, keeping it in am335x.h requires including stdint.h (for uint32_t etc) which i don't think would be right, do let me know if this is the right way. Here's the patch: >From f87b39708dd06482957fc7b33e78ab0ee095287b Mon Sep 17 00:00:00 2001 From: Udit agarwal <dev.mada...@gma

[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 2

Re: [PATCH] Added Getentropy() support to beagle BSP

to implement some sort of flag set/reset variable in shared memory, which can be used to implement a lock for TRNG register access something like a binary semaphore. >From b10e55c7f5cc8ca95b0d9b6a8cc7b8e37330544b Mon Sep 17 00:00:00 2001 From: Udit agarwal <dev.mada...@gmail.com> Date: Tue, 13 Ma

Re: [PATCH] Added Getentropy() support to beagle BSP

lt;j...@rtems.org> wrote: > > > On Mar 13, 2018 1:31 AM, "Sebastian Huber" <sebastian.huber@embedded- > brains.de> wrote: > > > > On 12/03/18 20:02, Udit agarwal wrote: > >> So, It looks like here's the final patch, do let me know if its ready to

Re: [PATCH] Added Getentropy() support to beagle BSP

Patch for BBB: >From a6b3b58a38a6925bf26b6573f36fc652708f9f32 Mon Sep 17 00:00:00 2001 From: Udit agarwal <dev.mada...@gmail.com> Date: Fri, 16 Mar 2018 15:37:05 +0530 Subject: [PATCH] arm/beagle: add TRNG based getentropy implementation --- bsps/arm/include/libcpu

Re: [PATCH] Added Getentropy() support to beagle BSP

Thanks for pointing that out, I have rectified the indentation errors. Here's the patch for atsam: >From 8e5e17525a76e68bc4d869d0af9700aaa5628483 Mon Sep 17 00:00:00 2001 From: Udit agarwal <dev.mada...@gmail.com> Date: Fri, 16 Mar 2018 14:54:53 +0530 Subject: [PATCH] arm/atsam

Suggestions regarding GSoC project

rtems.org/ticket/3222> in my proposal to make it a bit fair and strong. Regards, Udit agarwal ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Suggestions regarding GSoC project

Hi all, On Sat, Mar 10, 2018 at 5:07 PM, Christian Mauderer <l...@c-mauderer.de> wrote: > Am 10.03.2018 um 02:14 schrieb Udit agarwal: > > Hi all, Hi Christian Mauderer, Hi Russel Haley, > > > > I need some reviews/suggestions from the community regarding the idea of

Re: [PATCH] Added Getentropy() support to beagle BSP

On Thu, Mar 15, 2018 at 2:38 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 15/03/18 09:20, Udit agarwal wrote: > >> Also, will it be ok to keep atsam_trng_mutex even after user has finished >> using getentropy() i.e when we don't use destroy(_trng_m

Re: [PATCH] Added Getentropy() support to beagle BSP

n't checking for this bit. Instead they are only using RNG_STATUS_RDY as an indication of successful random data generation. *Patch: atsam* >From ae0c79ae4850503259c64387dea69346e7d7b1d4 Mon Sep 17 00:00:00 2001 From: Udit agarwal <dev.mada...@gmail.com> Date: Thu, 15 Mar 2018 09:43:13 +0530 S

Re: [PATCH] Added Getentropy() support to beagle BSP

On Thu, Mar 15, 2018 at 11:29 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 15/03/18 05:56, Udit agarwal wrote: > >> c/src/lib/libbsp/arm/atsam/startup/getentropy-trng.c | 6 ++ >> 1 file changed, 6 insertions(+) >> >&g

Re: [PATCH] Added Getentropy() support to beagle BSP

On Thu, Mar 15, 2018 at 11:34 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 15/03/18 05:56, Udit agarwal wrote: > >> +/* TRNG Register */ >> + >> +/* RNG base address */ >> > > Is the module name TRNG or RNG? > I

Re: [PATCH] Added Getentropy() support to beagle BSP

On Thu, Mar 15, 2018 at 1:19 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 15/03/18 08:13, Udit agarwal wrote: > >> Oh yes, i think i misinterpreted your previous suggestion of surrounding >> the while loop by mutex, it should be the outer whi

Re: getentropy() implementation on BBB

Hi, I have updated the code, please have a look. >From 74b8f4f5b9dd929b71ed5fb9dd0bc721a6f27a28 Mon Sep 17 00:00:00 2001 From: Udit agarwal <dev.mada...@gmail.com> Date: Wed, 7 Mar 2018 15:52:13 +0530 Subject: [PATCH] Added getentropy support to beagle BSP --- bsps/arm/include/libcpu

Re: getentropy() implementation on BBB

Thanks, I just came across ticket #3053 <https://devel.rtems.org/ticket/3053> , which talks about changing RTEMS license from GNU GPL to BSD-2-Clause (i was initially unaware of this!). I'll make the required changes. Regards, Udit agarwal On Wed, Mar 7, 2018 at 4:23 PM, Sebastian

Re: getentropy() implementation on BBB

Hi, Here's the updated code(I have also attached the patch PFA): >From 96e6e1bfd8cffeef5d309eb0a07fe2bfd086ef0a Mon Sep 17 00:00:00 2001 From: Udit agarwal <dev.mada...@gmail.com> Date: Tue, 6 Mar 2018 20:07:44 +0530 Subject: [PATCH] Added getentropy support to BBB BSP --- bsps/a

GSoC'18 proposal - Porting SDIO driver and benchmarking

unbalance or overlooked task. Regards, Udit agarwal ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Query regarding libbsd update

Hi, Thanks for pointing that out. I think back porting the driver would be the most viable option. So, i'll move ahead with that. Since, my proposal is almost ready, considering other libbsd projects at this time, would be a bit difficult. Thanks and regards, Udit agarwal On Sun, Mar 18, 2018

Query regarding libbsd update

understand the process better, and thus propose a more elaborated and realistic time-line. Thanks and Regards Udit agarwal ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC'18 proposal - Porting SDIO driver and benchmarking

Hi, On Sun, Mar 18, 2018 at 8:48 PM, Christian Mauderer <l...@c-mauderer.de> wrote: > Am 18.03.2018 um 14:22 schrieb Udit agarwal: > > Hi all, > > Here's the link to my proposal: > > https://docs.google.com/document/d/15Ut9FLAV3Y0Up1Qn02ys6KAb2QhtR > e

Re: GSoC'18 proposal - Porting SDIO driver and benchmarking

dio stack, or both? > > On Tue, Mar 20, 2018 at 11:41 AM, Udit agarwal <dev.mada...@gmail.com> > wrote: > > Hi, > > > > On Sun, Mar 18, 2018 at 8:48 PM, Christian Mauderer <l...@c-mauderer.de> > > wrote: > >> > >> Am 18.03.2018 um

getentropy() implementation on BBB

ptr += copy; + } + + return 0; + } + + RTEMS_SYSINIT_ITEM( + beagle_trng_clock_enable, + RTEMS_SYSINIT_DEVICE_DRIVERS, + RTEMS_SYSINIT_ORDER_LAST + ); Regards, Udit agarwal ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Implementing a check on FDT header

be a validy check within uboot itself(Given here <https://lists.denx.de/pipermail/u-boot/2012-March/121281.html>). Moreover, I have a doubt, Why is uboot RTEMS format depreciated as per your discussions in previous threads? Thanks! Regards, Udit agarwal __

Re: Query for GSOC Project

Hello Christian, Vaibhav, Sebastian, On Mon, Mar 4, 2019 at 3:18 PM Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > Am 04.03.19 um 07:47 schrieb Sebastian Huber: > > Hello Vaibhav Gupta, > > > > On 04/03/2019 07:27, Vaibhav Gupta wrote: > >> I am unable to confirm, if the