Re: [GSoC - x86_64] Clock driver - which hardware source to support primarily?

2018-07-17 Thread Sebastian Huber
Hello Amaan, On 17/07/18 19:18, Amaan Cheval wrote: Hi! Now that I'm working on the clock driver, we need to pick what we support first. Our options in brief are: The clock driver needs an interrupt. What is the status of the interrupt controller support in the BSP? For timekeeping we use

Re: Gcov support in Covoar

2018-07-17 Thread Joel Sherrill
This definitely looks like the right direction. If we don't understand the file formats, we will never be able to process and correlate them. Please put 0x in front of hex numbers. It does help. Can you explain the fields in gcno_dump.txt? The Version field looks like hex for R37A which doesn't

Re: [GSoC - x86_64] Clock driver - which hardware source to support primarily?

2018-07-17 Thread Joel Sherrill
On Tue, Jul 17, 2018 at 12:18 PM, Amaan Cheval wrote: > Hi! > > Now that I'm working on the clock driver, we need to pick what we > support first. Our options in brief are: > > - rdtsc; will need calibration through the PIT or one of the other options > Can this generate an interrupt? This is

[GSoC - x86_64] Clock driver - which hardware source to support primarily?

2018-07-17 Thread Amaan Cheval
Hi! Now that I'm working on the clock driver, we need to pick what we support first. Our options in brief are: - rdtsc; will need calibration through the PIT or one of the other options - PIT; likely not given how legacy it is, but it may be quite simple - APIC timer[1]; better for long-term

Re: [rtems commit] riscv: Implement CPU counter

2018-07-17 Thread Sebastian Huber
On 13/07/18 11:48, Hesham Almatary wrote: On Thu, Jul 12, 2018 at 9:41 PM, Sebastian Huber wrote: - Am 6. Jul 2018 um 15:11 schrieb Hesham Almatary heshamelmat...@gmail.com: On Fri, 6 Jul 2018 at 1:28 pm, Sebastian Huber wrote: [...] -CPU_Counter_ticks _CPU_Counter_read( void );

Re: (release notes generator) Merge code

2018-07-17 Thread Gedare Bloom
We also have https://git.rtems.org/rtems-release/tree/ as a candidate? On Mon, Jul 16, 2018 at 3:10 PM, Dannie Huang wrote: > Hi, > > Where should I merge the code of release notes generator? I think it should > go in rtems-tools, but not quite sure where it exactly should go. > > Best, > Dannie

[PATCH] Fio's initial RTEMS port

2018-07-17 Thread dev . madaari
Following IOengines are currently working on RTEMS: - psync, sync, vsync, filecreate, ftruncate, null I've attached the patch in my following mail, please have a look. Here's the corresponding ticket:https://devel.rtems.org/ticket/3429 Please note that i have also sent the patch to

[PATCH] Fio's initial RTEMS port

2018-07-17 Thread dev . madaari
From: Udit kumar agarwal - Add rtems-specific config files. - Constructors/Destructors being not supported by RTEMS, should be invoked as normal routines. - Add documentation for RTEMS - Update Makefile, os.h for RTEMS --- Makefile | 11 ++- README| 29

(release notes generator) Merge code

2018-07-17 Thread Dannie Huang
Hi, Where should I merge the code of release notes generator? I think it should go in rtems-tools, but not quite sure where it exactly should go. Best, Dannie ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel