Thank you Chris, I’ll give it a try
Lin
> On 26/08/2020, at 1:45 PM, Chris Johns wrote:
>
> On 26/8/20 3:09 pm, me wrote:
>>> On 26/08/2020, at 1:04 PM, Chris Johns wrote:
>>> Yes the plan is to have the waf build system in the RTEMS 6 release.
>> Cool, could you point me to a link of the RTEM
On 26/08/2020 07:45, Chris Johns wrote:
> On 26/8/20 3:09 pm, me wrote:
>>> On 26/08/2020, at 1:04 PM, Chris Johns wrote:
>>> Yes the plan is to have the waf build system in the RTEMS 6 release.
>> Cool, could you point me to a link of the RTEMS 6?
>
> https://devel.rtems.org/wiki/Release/6
>
>
On 26/8/20 3:09 pm, me wrote:
>> On 26/08/2020, at 1:04 PM, Chris Johns wrote:
>> Yes the plan is to have the waf build system in the RTEMS 6 release.
> Cool, could you point me to a link of the RTEMS 6?
https://devel.rtems.org/wiki/Release/6
The waf build system is still under development in Se
> On 26/08/2020, at 1:04 PM, Chris Johns wrote:
>
> On 26/8/20 3:00 pm, me wrote:
>> Thank you and the RTEMS team for hard work for this release.
>
> Thank you.
>
>> From a quick look, this release still uses the automake build system, but I
>> want to try the waf based new one, is there a
On 26/8/20 3:00 pm, me wrote:
> Thank you and the RTEMS team for hard work for this release.
Thank you.
> From a quick look, this release still uses the automake build system, but I
> want to try the waf based new one, is there a seperate release using the waf
> system?
Yes the plan is to hav
Hi Chris,
Thank you and the RTEMS team for hard work for this release. From a quick look,
this release still uses the automake build system, but I want to try the waf
based new one, is there a seperate release using the waf system?
cheers,
Lin
> On 26/08/2020, at 10:01 AM, Chris Johns wrote:
>
The RTEMS 5.1 Release is available. The release can be found at:
https://ftp.rtems.org/pub/rtems/releases/5/5.1
Please follow the release instructions provided by the link.
The RTEMS 5 release is a significant milestone for the RTEMS project with many
years of effort from many people as we cont
On 24/8/20 9:59 am, Chris Johns wrote:
> How is EPICS used in real systems? Is the production executable built by EPICS
> from the EPICS source tree? Is it a set of libraries that get installed and an
> application links in these libraries?
Ping?
Chris
On 26/8/20 8:48 am, Mritunjay Sharma wrote:
> First of all, Apologies for the little delay in response. I was actually a
> little stuck with assignments in classes.
Thanks for letting us know. You will need to make up the lost time somehow.
> There's one problem although, while building using:
Hello, everyone!
First of all, Apologies for the little delay in response. I was actually a
little stuck with assignments in classes.
Thank you so much, Chris, for such a nice explanation and detailed review.
It cleared a lot of things even for me.
I have tried to respond to further suggestions a
This patch add supports for EPICS7 Package to RTEMS RSB.
Signed-off-by: Mritunjay Sharma
---
rtems/config/epics/epics-7-1.cfg| 22 +++
rtems/config/epics/epics-base.bset | 26 +
source-builder/config/epics-7-1.cfg | 57 +
3 files changed, 105 i
On 25/8/20 10:48 pm, Heinz Junkes wrote:
> yes it works as described. The header file (librtemsNfs.h) is also there.
> I must have done something wrong the day before yesterday. Unfortunately
> I can't reproduce it anymore. Sorry for the "false alarm”.
Great and no problem.
> I no longer use libr
hello everyone,
I after building arm-rtems6 toolchain with my ftw patch
when i build rtems i receive this error
The error comes on the patches that were earlier version of the
successfully tested patch:)
Error log :
/home/eshan/development/rtems/kernel/rtems/c/src/../../testsuites/sptests/spcxx01/
Hallo Chris,
yes it works as described. The header file (librtemsNfs.h) is also there.
I must have done something wrong the day before yesterday. Unfortunately
I can't reproduce it anymore. Sorry for the "false alarm”.
I no longer use librtemNfs.h when using the libbsd stack.
It is no longer nece
From: Chris Johns
Closes #4037
---
source-builder/pkg-config | 236 +++---
source-builder/sb-check | 24 +--
source-builder/sb-defaults| 23 +--
source-builder/sb-get-sources | 23 +--
source-builder/sb-reports | 2
Hi,
Thanks a lot for this detailed review. I will work on each point that you
mentioned.
On Mon, Aug 24, 2020 at 11:07 PM Gedare Bloom wrote:
> On Mon, Aug 24, 2020 at 10:14 AM Richi Dubey wrote:
> >
> > ---
> > cpukit/include/rtems/scheduler.h | 6 +-
> > .../include/rtems/sco
This second version of the patch includes:
- improved documentation
- addition of void* user argument to interrupt callback
- addition of position value arg to interrupt callback
James Fitzsimons (2):
Adding QEP driver to Beaglebone bsp
bsp: improved documentation in Beaglebone qep driver
---
bsps/arm/beagle/headers.am | 2 +
bsps/arm/beagle/include/bsp/bbb-pwm.h | 11 -
bsps/arm/beagle/include/bsp/pwmss.h | 54 +++
bsps/arm/beagle/include/bsp/qep.h | 331 ++
bsps/arm/beagle/pwm/pwm.c | 64 +---
bsps/arm/beagle/pwmss/pwmss
---
bsps/arm/beagle/include/bsp/qep.h | 59 ---
bsps/arm/beagle/qep/qep.c | 14 ++--
2 files changed, 67 insertions(+), 6 deletions(-)
diff --git a/bsps/arm/beagle/include/bsp/qep.h
b/bsps/arm/beagle/include/bsp/qep.h
index 671d9cca6c..fc086e3c80 100644
--
19 matches
Mail list logo
