Close #3459.
---
cpu-supplement/port.rst | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/cpu-supplement/port.rst b/cpu-supplement/port.rst
index dec91a7..bf1de3e 100644
--- a/cpu-supplement/port.rst
+++ b/cpu-supplement/port.rst
@@ -222,9 +222,9 @@ sw
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
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 m
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 c
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 as
Got it! Thanks for letting me know Gedare.
On Tue, Jul 17, 2018 at 11:30 AM, Gedare Bloom wrote:
> 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 gen
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 );
+sta
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
Hello,
As suggested by Joel, I have tried to figure out the structure of
the gcno files and written a gcno dumper.
This is not complete yet, I'm still working on it and I'll keep adding
to it as I "decode" the gcno files.
I'm attaching the c++ code, the gcno file I'm testing on and the txt
file g
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 f...@vger.ker
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 ++
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
12 matches
Mail list logo
