Re: GSoC Project | Basic Support for Trace Compass

> > For TCP stream we should have only one file and for the input file, we > > should have as many files as there stored in > > variable RTEMS_RECORD_CLIENT_MAXIMUM_CPU_COUNT right? > > No, you have only one input stream. It doesn't matter if it received via > TCP or read from a file. Why do you th

Re: GSoC Project | Basic Support for Trace Compass

On 02/07/2019 08:33, Ravindra Kumar Meena wrote: Your latest commit has some issues: https://github.com/rmeena840/rtems-tools/commit/85029d39eb26bde2e7519d0bd6b2a8f430f13652 You have exactly one input source, this is either a TCP stream or a input file. For TCP stream we shoul

Re: GSoC Project | Basic Support for Trace Compass

> > Your latest commit has some issues: > > > https://github.com/rmeena840/rtems-tools/commit/85029d39eb26bde2e7519d0bd6b2a8f430f13652 > > You have exactly one input source, this is either a TCP stream or a > input file. > For TCP stream we should have only one file and for the input file, we shoul

Re: GSoC Project | Basic Support for Trace Compass

On 02/07/2019 07:10, Ravindra Kumar Meena wrote: What does binary file you pushed on my workplace has? With the previous file(raw_data), it was generating only one binary file but with the new file(qoriq_e6500_32), it is generating multiple files. It is an event record stream with 24 CPUs so

Re: GSoC Project | Basic Support for Trace Compass

On 02/07/2019 06:48, Ravindra Kumar Meena wrote: *1st July work summary:* Updated the GSoC blog. Worked on the assigned task. Your latest commit has some issues: https://github.com/rmeena840/rtems-tools/commit/85029d39eb26bde2e7519d0bd6b2a8f430f13652 You have exactly one input source, this is

Re: GSoC Project | Basic Support for Trace Compass

Have made changes for the task opening an event stream file for each processor. https://github.com/rmeena840/rtems-tools/commit/85029d39eb26bde2e7519d0bd6b2a8f430f13652 Have a look What does binary file you pushed on my workplace has? With the previous file(raw_data), it was generating only one

Re: GSoC Project | Basic Support for Trace Compass

*1st July work summary:* Updated the GSoC blog. Worked on the assigned task. -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) , Dhanbad ___ devel ma

Re: Error: undefined reference to ndbm functions

On Fri, Jun 28, 2019, 9:57 PM Gedare Bloom wrote: > On Fri, Jun 28, 2019 at 7:20 AM Vaibhav Gupta > wrote: > > > > > > > > On Fri, Jun 28, 2019, 6:19 PM Joel Sherrill wrote: > >> > >> > >> > >> On Fri, Jun 28, 2019, 8:40 AM Vaibhav Gupta > wrote: > >>> > >>> > >>> > >>> On Fri, Jun 28, 2019, 5

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019, 5:20 PM Chris Johns wrote: > On 1/7/19 10:28 pm, Joel Sherrill wrote: > > The hope was to find an already > > implemented optimized version with history for the SPARC. But so far we > haven't > > found one with appropriate license. It will be difficult to implement, > ensure

Re: Error: undefined reference to ndbm functions

On 1/7/19 10:28 pm, Joel Sherrill wrote: > The hope was to find an already > implemented optimized version with history for the SPARC. But so far we > haven't > found one with appropriate license. It will be difficult to implement, ensure > correctness, and really gain speed. Is this suitable ...

Re: Attempt to get rid of -qrtems

On 01/07/2019 07:23, Sebastian Huber wrote: On 01/07/2019 02:41, Joel Sherrill wrote: On Sun, Jun 30, 2019, 7:09 PM Chris Johns > wrote:     On 28/6/19 6:02 pm, Sebastian Huber wrote: > On 28/06/2019 01:37, Chris Johns wrote: >> On 27/6/19 10:08 pm, Sebasti

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019 at 8:05 AM Vaibhav Gupta wrote: > > > On Mon, Jul 1, 2019 at 6:21 PM Vaibhav Gupta > wrote: > >> >> >> On Mon, Jul 1, 2019 at 6:18 PM Aditya Upadhyay >> wrote: >> >>> On Mon, Jul 1, 2019 at 6:10 PM Vaibhav Gupta >>> wrote: >>> > >>> > >>> > >>> > On Mon, Jul 1, 2019 at 6:07

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019 at 6:21 PM Vaibhav Gupta wrote: > > > On Mon, Jul 1, 2019 at 6:18 PM Aditya Upadhyay > wrote: > >> On Mon, Jul 1, 2019 at 6:10 PM Vaibhav Gupta >> wrote: >> > >> > >> > >> > On Mon, Jul 1, 2019 at 6:07 PM Aditya Upadhyay >> wrote: >> >> >> >> On Mon, Jul 1, 2019 at 5:58 PM

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019 at 6:18 PM Aditya Upadhyay wrote: > On Mon, Jul 1, 2019 at 6:10 PM Vaibhav Gupta > wrote: > > > > > > > > On Mon, Jul 1, 2019 at 6:07 PM Aditya Upadhyay > wrote: > >> > >> On Mon, Jul 1, 2019 at 5:58 PM Joel Sherrill wrote: > >> > > >> > If you have finished ndbm, please do

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019 at 6:10 PM Vaibhav Gupta wrote: > > > > On Mon, Jul 1, 2019 at 6:07 PM Aditya Upadhyay wrote: >> >> On Mon, Jul 1, 2019 at 5:58 PM Joel Sherrill wrote: >> > >> > If you have finished ndbm, please do not attempt to write memcpy for >> > SPARC. It is not as important as having

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019 at 6:07 PM Aditya Upadhyay wrote: > On Mon, Jul 1, 2019 at 5:58 PM Joel Sherrill wrote: > > > > If you have finished ndbm, please do not attempt to write memcpy for > SPARC. It is not as important as having fenv.h methods. We have a default > memcpy implementation for all arc

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019 at 5:58 PM Joel Sherrill wrote: > > If you have finished ndbm, please do not attempt to write memcpy for SPARC. > It is not as important as having fenv.h methods. We have a default memcpy > implementation for all architectures. The hope was to find an already > implemented o

Re: Error: undefined reference to ndbm functions

On Mon, Jul 1, 2019 at 5:58 PM Joel Sherrill wrote: > If you have finished ndbm, please do not attempt to write memcpy for > SPARC. It is not as important as having fenv.h methods. We have a default > memcpy implementation for all architectures. The hope was to find an > already implemented optim

Re: Error: undefined reference to ndbm functions

If you have finished ndbm, please do not attempt to write memcpy for SPARC. It is not as important as having fenv.h methods. We have a default memcpy implementation for all architectures. The hope was to find an already implemented optimized version with history for the SPARC. But so far we haven't

[PATCH v2 4/6] am335x display drivers: Port to RTEMS

--- Makefile.todo | 13 ++ libbsd.py | 12 + rtemsbsd/include/bsp/nexus-devices.h | 2 + .../machine/rtems-bsd-kernel-namespace.h | 2 + rtemsbsd/include/rtems/bsd/local/fb_if.h | 45 ++

[PATCH v2 6/6] fbd: Port to RTEMS

--- freebsd/sys/dev/fb/fbd.c | 8 + libbsd.py | 4 +++ rtemsbsd/include/bsp/nexus-devices.h | 3 ++ .../machine/rtems-bsd-kernel-namespace.h | 35 +++ rtemsbsd/include/rtems/bsd/local/opt_fb.h | 0 5

[PATCH v2 2/6] TDA19988: Port to RTEMS

--- Makefile.todo | 27 ++ buildset/default.ini | 1 + libbsd.py | 45 + rtemsbsd/include/bsp/nexus-devices.h | 1 + .../machine/rtems-bsd-kernel-namespace.h | 65 +

[PATCH v2] Port Display drivers from FreeBSD

Hello all, In this version 2 of the patch, I have fixed the issues pointed out in review of the first version. I've only sent the port patches here as the import ones are just copy of FreeBSD sources. With this patchset the tda0 device is created and attached to the iicbus, the am335x_lcd drive

Re: GSoC Project | Basic Support for Trace Compass

On 01/07/2019 13:28, Ravindra Kumar Meena wrote: Have made changes for task writing the events of a processor (CPU) to the corresponding file. https://github.com/rmeena840/rtems-tools/commit/111ee2f3f92a0371241d31542d28687431d18097 This cannot work. If you write into N files, then you have to

Re: GSoC Project | Basic Support for Trace Compass

Have made changes for task writing the events of a processor (CPU) to the corresponding file. https://github.com/rmeena840/rtems-tools/commit/111ee2f3f92a0371241d31542d28687431d18097 Have a look -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technolog

Re: Error: undefined reference to ndbm functions

Hello, I am reading about memcpy to write it for newlib. Should I also write wmemcpy along with it? https://pubs.opengroup.org/onlinepubs/009695399/functions/wmemcpy.html . Regarding ndbm reference. RSB has not generated library files. - but in newlib source tree, when I compiled newlib, while port