On 20/03/2020 05:15, Chris Johns wrote:
On 19/3/20 7:52 pm, Sebastian Huber wrote:
The ARMv7-M architecture has no CP-15. The inline assembly for the
CP-15 access leads to assembler errors if compiled with -O0.
I would like to understand this one in detail to see why there is cp15 in the
version8March20.docx
Description: MS-Word 2007 document
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 20/3/20 3:18 pm, Anmol Mishra wrote:
> Hello,
> How does the community test the rtems-tools changes?
> In the README I can see a few steps, Is that the standard method?, It is my
> first patch for rtems, help is really appreciated.
These files are hard to test because python is linked into
Hello,
How does the community test the rtems-tools changes?
In the README I can see a few steps, Is that the standard method?, It is my
first patch for rtems, help is really appreciated.
Best Regards
On Fri, Mar 20, 2020 at 3:45 AM Gedare Bloom wrote:
> Hi Anmol,
>
> On Thu, Mar 19, 2020 at
On 19/3/20 7:52 pm, Sebastian Huber wrote:
> The ARMv7-M architecture has no CP-15. The inline assembly for the
> CP-15 access leads to assembler errors if compiled with -O0.
I would like to understand this one in detail to see why there is cp15 in the
build.
> ---
>
Hi,
The last snapshot
https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2003/
has a release process bug. The bug is due to the way the sources are collected
and packaged. I end up with two copies of the top level sources, the top level
file and an almost identical copy in `sources`.
On 20/3/20 9:05 am, William wrote:
> Been sitting on this patch for a while now, figured I should finally submit
> it...
Thank you for posting the patch.
> About a month ago I saw someone saying that they wanted to have this section
> of
> the users guide added in, followed all of the steps of
Looks good and thanks.
Plus there is this ...
https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#gdbarmsim
:)
Chris
On 20/3/20 7:56 am, Joel Sherrill wrote:
> Closes #3611.
> ---
> .../arm/gdbarmsim/config/arm1136jfs-testsuite.tcfg | 5 -
>
Thank you. Please push.
Chris
On 20/3/20 2:35 am, Gedare Bloom wrote:
> ---
> rtemstoolkit/execute.py | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/rtemstoolkit/execute.py b/rtemstoolkit/execute.py
> index 35f616c..3a79f50 100755
> --- a/rtemstoolkit/execute.py
Hi Anmol,
On Thu, Mar 19, 2020 at 1:41 PM Anmol Mishra wrote:
>
> Hello,
> I can understand your requests, I also thought to squash/combine all changes
> in 1 patch. I will complete the task in a day and resend the patch. I did not
> know the protocol/contributing guide. I will keep a note of
Been sitting on this patch for a while now, figured I should finally
submit it...
About a month ago I saw someone saying that they wanted to have this
section of the users guide added in, followed all of the steps of the
userguide up to the point just prior and then wrote this.
One thing to
Closes #3611.
---
.../arm/gdbarmsim/config/arm1136jfs-testsuite.tcfg | 5 -
bsps/arm/gdbarmsim/config/arm1136jfs.cfg | 18 -
bsps/arm/gdbarmsim/config/arm1136js-testsuite.tcfg | 5 -
bsps/arm/gdbarmsim/config/arm1136js.cfg| 18 -
Hello,
On Thu, Mar 19, 2020 at 9:56 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello,
>
> I checked in the first version of the guide:
>
> https://docs.rtems.org/branches/master/eng/python-devel.html
> We should refine it now step by step. In particular, it would be
Hello,
I can understand your requests, I also thought to squash/combine all
changes in 1 patch. I will complete the task in a day and resend the patch.
I did not know the protocol/contributing guide. I will keep a note of this.
Sorry for the trouble.
Regards
On Thu, Mar 19, 2020 at 9:53 PM
On Thu, Mar 19, 2020 at 1:13 PM Gedare Bloom wrote:
> On Thu, Mar 19, 2020 at 11:56 AM Niteesh G. S.
> wrote:
> >
> > Hello,
> >
> > While looking for small tasks to take up, Gedare mentioned about adding
> GDB BSPs
> > to rtems-tester. Can some please explain a bit more of what has to be
>
On 2020-03-19 10:00 -0600, Gedare Bloom wrote:
> Thank you for kicking off this discussion. As with most style issues,
> a lot of personal preferences came out, but also some good reasoning
> was given on both sides.
Yeah, I know these conversations sometimes don't go well but everyone has been
On Thu, Mar 19, 2020 at 11:56 AM Niteesh G. S. wrote:
>
> Hello,
>
> While looking for small tasks to take up, Gedare mentioned about adding GDB
> BSPs
> to rtems-tester. Can some please explain a bit more of what has to be done? I
> guess
> we have to write configuration files for BSPs that
Hello,
I checked in the first version of the guide:
https://docs.rtems.org/branches/master/eng/python-devel.html
We should refine it now step by step. In particular, it would be good to
add some best practice parts to the Testing section.
An open issue is how we would like to run the
Hi Anmol,
Thanks for your patches. I have a few requests.
Can you please provide some details in your commit message? In
particular, since few of us right now know how to make code compliant
between Python 2 and 3, can you provide a brief
justification/description for what the changes are and
On Wed, Mar 18, 2020 at 12:25 PM Amar Takhar wrote:
>
> The only one I would like to propose is the 80 character limit. This should
> be
> moved to something more reasonable such as 120.
>
> Code comments should remain below 80 however.
>
Thank you for kicking off this discussion. As with most
On Thu, Mar 19, 2020 at 1:25 AM Sebastian Huber
wrote:
>
> On 19/03/2020 07:31, Sebastian Huber wrote:
>
> > Hello Gedare,
> >
> > I am open for all exceptions provided
> >
> > * there is a well known tool available which can format the code
> > automatically with the exceptions,
> >
> > * the
Hi all,
I think the consensus is forming to have 80-character line limits as
per PEP-8. So far I only heard 1 vote in favor of anything else, with
several in favor of 80 characters and some abstaining to vote.
FWIW: I strongly prefer 80-character lines as well, both for
readability and
---
rtemstoolkit/execute.py | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/rtemstoolkit/execute.py b/rtemstoolkit/execute.py
index 35f616c..3a79f50 100755
--- a/rtemstoolkit/execute.py
+++ b/rtemstoolkit/execute.py
@@ -576,8 +576,10 @@ if __name__ == "__main__":
On Thu, Mar 19, 2020 at 6:27 AM Thanassis Tsiodras (external) <
thanassis.tsiod...@esa.int> wrote:
> *> I think we should stay with the traditional 80 characters per line.*
>
> Seconded.
>
>
>
> When I was younger I thought this was a silly requirement, a remnant from
> the age of serial
On Thu, Mar 19, 2020 at 4:20 AM wrote:
>
>
> > Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Joel Sherrill
> > Gesendet: Mittwoch, 18. März 2020 22:18
> > An: Heinz Junkes
> > Cc: rtems-de...@rtems.org
> > Betreff: Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100
> >
> >
> >
Congrats Vijay!!
--Vaibhav Gupta
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hi Gedare and everyone,
I'm excited and grateful to be added as a maintainer!
It's a great opportunity and I'm looking forward to adding more value to
the community.
Thanks and regards.
Vijay
On Thu, Mar 19, 2020, 2:44 AM Gedare Bloom wrote:
> Hello all,
>
> I'm pleased to announce Vijay
> I think we should stay with the traditional 80 characters per line.
Seconded.
When I was younger I thought this was a silly requirement, a remnant from
the age of serial terminals
So I allowed myself to relax these checks - and indeed, the tools allow
developers to do so.
But with
On Thu, Mar 19, 2020, 11:54 AM Christian Mauderer <
christian.maude...@embedded-brains.de> wrote:
> On 18/03/2020 22:17, Gedare Bloom wrote:
> > Hi everyone,
> >
> > I'm pleased to announce that the rtems-littlevgl package will be
> > maintained (officially) by Christian Mauderer and Vijay Kumar
Thank you so much and all the more for this great initiative of providing
me with an MVME6100 to get the first hand feeling for target development.
I have started working on the next step to get EPICS7 running with RTEMS5
on qemu. As of now, it's looking a bit challenging because I am a bit new
to
> Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Joel Sherrill
> Gesendet: Mittwoch, 18. März 2020 22:18
> An: Heinz Junkes
> Cc: rtems-de...@rtems.org
> Betreff: Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100
>
>
>
> On Wed, Mar 18, 2020 at 2:38 PM Heinz Junkes wrote:
Thanks for pushing it.
-Niteesh.
On Thu, Mar 19, 2020 at 11:47 AM Christian Mauderer <
christian.maude...@embedded-brains.de> wrote:
> Hello Niteesh,
>
> thanks for finding and fixing that. It's a very small patch and no one
> objected in the last days. So I pushed it.
>
> Best regards
>
>
The ARMv7-M architecture has no CP-15. The inline assembly for the
CP-15 access leads to assembler errors if compiled with -O0.
---
cpukit/libdebugger/rtems-debugger-arm.c | 24 +---
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git
Hello,
I started to work on a BSP for the STM32H7:
https://devel.rtems.org/ticket/3910
I will use the new build system for this BSP.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
> On 18. Mar 2020, at 22:17, Joel Sherrill wrote:
>
> We have had good experiences with RTEMS+libbsd with the Qemu ARM Zynq.
> We have been able to telnet to the RTEMS target from Linux and use the RTEMS
> NFS client to mount Linux files plus dynamic loading works. Personally I
> would
>
I created this patch with a generator script and these two specification
items:
https://git.rtems.org/sebh/rtems-qual.git/commit/?id=a8d896dd7871cf9a3def6813727a57815b4bbe77
___
devel mailing list
devel@rtems.org
Update #3904.
---
c-user/config/event-record.rst | 64 ++
1 file changed, 64 insertions(+)
diff --git a/c-user/config/event-record.rst b/c-user/config/event-record.rst
index 7071c77..1dc7204 100644
--- a/c-user/config/event-record.rst
+++
On 19/03/2020 08:20, Chris Johns wrote:
It would be good if we can tag static dicts as discussed previously. If we
cannot I am ok to revisiting to design to remove them. I am sure this can be
done, it just takes time.
I think this is already covered by the examples in:
On 19/03/2020 07:31, Sebastian Huber wrote:
Hello Gedare,
I am open for all exceptions provided
* there is a well known tool available which can format the code
automatically with the exceptions,
* the static analyzer tools can be configured to give good results
with the exceptions, and
> On 19 Mar 2020, at 5:31 pm, Sebastian Huber
> wrote:
>
> Hello Gedare,
>
> I am open for all exceptions provided
>
> * there is a well known tool available which can format the code
> automatically with the exceptions,
>
> * the static analyzer tools can be configured to give good
Path on computer
-home
-rtems-tools
Rtems tools project
https://github.com/RTEMS/rtems-tools
Personal fork of Rtems tools
https://github.com/suyashsingh234/rtems-tools
My notes
https://github.com/suyashsingh234/rtems-notes/blob/master/README.md
Gsoc proposal (draft)
---
clanganalyzer/first | 1 +
1 file changed, 1 insertion(+)
create mode 100644 clanganalyzer/first
diff --git a/clanganalyzer/first b/clanganalyzer/first
new file mode 100644
index 000..0b3ee12
--- /dev/null
+++ b/clanganalyzer/first
@@ -0,0 +1 @@
+Clang analyzer will be added here
\ No
Hello Gedare,
I am open for all exceptions provided
* there is a well known tool available which can format the code
automatically with the exceptions,
* the static analyzer tools can be configured to give good results with
the exceptions, and
* the exceptions are a best practice in a
On 18/03/2020 22:17, Gedare Bloom wrote:
> Hi everyone,
>
> I'm pleased to announce that the rtems-littlevgl package will be
> maintained (officially) by Christian Mauderer and Vijay Kumar
> Bannerjee. Christian/Vijay, please add a README file to the
> rtems-littlevgl package and include some
On 19/03/2020 07:07, Christian Mauderer wrote:
I think we will have a really hard time to set up tools like formatters
or pylint to check and use these rules. I think setting a line length to
120 should be easy to possible for nearly any tool. But I expect that
setting it to 120 for code and 80
Hello Niteesh,
thanks for finding and fixing that. It's a very small patch and no one
objected in the last days. So I pushed it.
Best regards
Christian
On 16/03/2020 15:42, G S Niteesh Babu wrote:
> enable-uart should be enable_uart in config.txt
> ---
> user/bsps/arm/raspberrypi.rst | 2 +-
>
Hello Chris and Amar,
On 19/03/2020 04:01, Chris Johns wrote:
> On 19/3/20 7:06 am, Christian Mauderer wrote:
>> Hello Amar,
>>
>> On 18/03/2020 19:24, Amar Takhar wrote:
>>> The only one I would like to propose is the 80 character limit. This
>>> should be
>>> moved to something more
47 matches
Mail list logo
