On 2014-11-20 11:27 -0600, Joel Sherrill wrote:
Hi
Images do not seem to be in place. Two examples.
https://devel.rtems.org/wiki/Developer/Git
https://devel.rtems.org/wiki/TBR/UserManual/RTEMS_Software_Architecture
Yes, that is another item I'm working on. Restoring the images is going
On 2014-11-23 10:28 -0500, Gedare Bloom wrote:
snip
RTEMS (rtems.git) components:
* One component for each architecture family; for problems that affect
those archs or their bsps
We have a 'tag cloud' that can be viewed here: https://devel.rtems.org/tags
both tickets and wiki pages can be
On 2014-12-04 13:37 -0500, Gedare Bloom wrote:
Hi,
I did not see a commit message on rtems-vc for
http://git.rtems.org/rtems/commit/?id=4081032ce01d206d2c8e7d7b73dcdc59f85683d4
Probably Ben's account must be added to something?
I forgot to ask him to sign up. I just did that for him.
This email explains the changes involved in making this work as well as the
introduction of several tools that did not exist before.
There are two main components to this. 'RTEMS Config' and 'waf'. The two are
not connected. RTEMS Config holds ALL configuration information for RTEMS. It
I would like to announce the availability of the 'waf' branch for RTEMS for
testing and review.
This represents a complete, ground-up rewrite of the RTEMS build system that
has
taken me roughly 3 years to complete off/on in my spare time / self-funded.
The new build system from a clean
This email covers a brief overview of how to build the branch and some details.
It handy for 'trying it out' without getting too far into the details.
Here is the timing for the build at the moment:
verm@peach# waf config --bsp sparc/sis --prefix /mnt/devel/rtems/prefix/rtems
--path-tools
On 2015-02-07 10:27 +1100, Chris Johns wrote:
On 6/02/2015 6:04 pm, Amar Takhar wrote:
Onto the BSP configuration.
For my Zynq board at the moment has 256M and I have L2 cache disabled
and with the autotools configure I need use BSPOPTS as:
BSP_DATA_CACHE_ENABLED
On 2015-02-07 19:22 +1100, Chris Johns wrote:
MacPro (Maverick)
snip
I have added a page here for this:
https://devel.rtems.org/wiki/waf/Timing
Note the performance on Debian. There is something serious going on with
FreeBSD and python that also hits OS X. Not sure what it is yet.
On 2015-02-08 18:34 +1100, Chris Johns wrote:
On 6/02/2015 6:03 pm, Amar Takhar wrote:
verm@peach# waf -j 14 --enable-tests
'build' finished successfully (13.414s)
note: the above is 881 targets.
snip
I am not sure if this is the total number of tests. I thought it was
around
On 2015-02-08 09:40 +0100, Sebastian Huber wrote:
One issue I found is that the test are not re-built in case the
librtemscpu.a changes, e.g.
sh@linux-p471:~/git-rtems-waf (waf) touch
./build/sparc/sis/cpukit/librtemscpu.a
To clarify, you cannot make a change in the ./build/ directory
On 2015-02-08 09:40 +0100, Sebastian Huber wrote:
Thanks for your great work in the background.
Thanks and you're welcome!
I tested it on a five year old low budget laptop with an up to date
openSUSE and it worked out of the box.
I updated the timing page (2m with waf and 14m with the
On 2015-02-11 14:16 +1100, Chris Johns wrote:
And as I see below options can be altered in a controlled manner instead
of a local patch applied after the config phase. This is what I was meaning.
Ah, yes it's very controlled in config.cfg. The options are verified (not
fully, yet) for sanity
On 2015-02-09 17:32 +, Cudmore, Alan P. (GSFC-5820) wrote:
Hi Amar,
I have tried the sparc/sis waf build on Ubuntu 14.04 and Debian 7. The
build is very fast!
I will try to get some timing numbers with building RTEMS on the Rasberry
Pi 2 later this week..
That is fantastic, thank you!
On 2015-02-09 17:32 +, Cudmore, Alan P. (GSFC-5820) wrote:
I would like to request Raspberry Pi, LEON3, and m68k/mcf5235.
LEON3 is working now.
Amar.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 2015-02-10 08:15 +1100, Chris Johns wrote:
snip
Look in config.cfg when you do a 'waf' configure for all the available
options
these are exposed there.
Do I just edit these options ?
Yes.
If so, is this temporary or the way we do this ? I am considering the
use case of a
On 2015-02-09 18:34 +, Cl??udio Silva wrote:
Hello Amar,
I was also able to build sparc/sis in? a Fedora 18 (Core 2 Duo @ 2.93 Ghz).
Build time was about 1m10s. However, I had to update waf; the version
available
in Fedora doesn't seem to work with RTEMS' waf.
Please also add the
On 2015-02-09 17:32 +, Cudmore, Alan P. (GSFC-5820) wrote:
I would like to request Raspberry Pi, LEON3, and m68k/mcf5235.
arm/raspberrypi has been added.
From scratch it took me exactly 4m10s to add this including the time to build
RTEMS + all tests:
The following is a proposal for a new source layout that will be included in
the
new 'waf' build system. The current layout is a product of years of laying and
requirements for the auto* build system. Since we are no longer restricted by
this it makes sense to take the time and give RTEMS a
The following is a proposal to lay out the beginnings of a plan to move from
the
current auto* build system to the new waf build located at
http://git.rtems.org/amar/waf.git.
This is meant as an initial overview open for discussion. The entire project
will be fleshed out on the wiki and
On 2015-03-07 09:44 +0100, Dominik Taborsky wrote:
I am a newbie to RTEMS, but this sounds great. The current layout is
very confusing to newcomers. Kudos to you, Amar!
Please, see my notes further on.
Great to hear input from new users, thank you!
include locations
~
On 2015-03-07 09:44 +0100, Dominik Taborsky wrote:
Just one question here: Why have the public API hidden in a subdir of
private APIs? Shouldn't this be the other way around?
I just noticed the layout I gave above was wrong! Gedare sent me an
email (he could not email the list directly from
Please ignore the previous include layout the correct is below copied from
another email in this thread:
I just noticed the layout I gave above was wrong! Gedare sent me an
email (he could not email the list directly from his device). I had a typo in
the original one and also didn't copy
On 2015-03-12 14:10 +0100, Sebastian Huber wrote:
#include rtems/sparc/cpu.h
#include rtems/score/percpu.h
This will not work. We have sparc, arm, powerpc etc. and they must not
be visible at the same time.
What do you mean by 'visible'?
The names of some headers would have to be
On 2015-03-12 14:19 +0100, Sebastian Huber wrote:
On 12/03/15 14:13, Amar Takhar wrote:
On 2015-03-12 14:10 +0100, Sebastian Huber wrote:
#include rtems/sparc/cpu.h
#include rtems/score/percpu.h
This will not work. We have sparc, arm, powerpc etc. and they must not
be visible
On 11/03/2015 1:27 am, Karel Gardas wrote:
Yes, this is a big patch but if you do not merge it now and later
following waf work you do tree/file placement refactoring than the patch
would be even harder to merge.
I was thinking this would land in 4.12 then waf would be based off of that.
On 2015-03-11 09:44 +0100, Sebastian Huber wrote:
We need at least three -I options, one for the BSP headers, one for the
CPU headers and one for the rest.
The current one uses only one -I because all paths will be explicit. Right now
I've hacked around the problem with the header
On 2015-03-12 13:57 +0100, Sebastian Huber wrote:
On 11/03/15 13:04, Amar Takhar wrote:
On 2015-03-11 09:44 +0100, Sebastian Huber wrote:
We need at least three -I options, one for the BSP headers, one for the
CPU headers and one for the rest.
The current one uses only one -I because
On 2015-03-09 08:39 +1100, Chris Johns wrote:
On 8/03/2015 12:51 pm, Amar Takhar wrote:
Thanks for starting this thread. Reorganising the source tree in RTEMS
is long over due.
You're welcome! The source layout was the second biggest issue I had with
navigating the code.
I assume
On 2015-03-24 11:05 -0400, Gedare Bloom wrote:
On Tue, Mar 24, 2015 at 10:52 AM, Charith Eranga
eranga.char...@gmail.com wrote:
Hi All,
I'm Charith Eranga from University of Moratuwa, Sri Lanka. I'm
currently a second year student specializing in embedded software
development.
I'm
On 2015-02-18 11:18 -0500, Gedare Bloom wrote:
Hi,
There aren't any great ways in Trac directly to establish relations
between tickets. One simple way is to reference other tickets in
comments. If we also install TracBacks [1] then any comments that
refer to another ticket will
We're getting hit with a lot of spam at the moment. Some may get through for
those of you with permission you can delete a ticket. The location of the
button is here:
https://trac-hacks.org/attachment/ticket/10841/DeleteButton.png
It will ask for a conformation.
Amar.
On 2015-04-17 07:59 -0500, Joel Sherrill wrote:
What about the account that filed it?
I added that user to the 'SPAM' group. This will trash any changes they make
and have the system learn it as SPAM (Bayesian).
Developers have access to do this noone else.
Amar.
On 2015-04-17 15:34 -0600, Eduardo Silva wrote:
just my 5c: on our project we faced the same problem with Trac. Bots create
accounts and start commenting tickets with Ads and general trash. The solution
for us was to start using Github Issues, no more spam.
RTEMS is dedicated to hosting all of
On 2015-06-18 05:57 +0530, Anand Krishnan wrote:
Hi all,
I've almost prepared the basic layout for the GUI. Also added some dummy event
handlers for File Menu.
Any more suggestions before fetching the options?
This is a great start!
Have you thought about how you are going to lay out the
On 2015-07-04 19:10 +0530, Anand Krishnan wrote:
Hi,
Thanks for approving my midterm evaluation.
You're welcome.
Anyways, I have added the GUI class for String options. Will work on
StringList
now.
OK, this week I want to clean up the classes to simplify how it's stored
internally for
On 2016-01-06 08:03 -0600, Joel Sherrill wrote:
> Amar, etc.
>
> I committed this patch from rtbf64c. Where do I need to look for my name
> being??
> spelled incorrectly on this next line? I can't find it this morning.
Either in /.git/config or ~/.gitconfig or /etc/password
It checks these in
On 2016-01-06 14:42 -0600, Joel Sherrill wrote:
>
> Ahh.. that would be under Amar's control. :)
Oh, it was a vc email sorry I didn't notice.
I've fixed it now, surprised it took this long for someone to notice. :)
Amar.
___
devel mailing list
On 2016-04-29 17:39 +1000, Chris Johns wrote:
> I had a long chat to Amar about this topic today and he told me we
> should follow the FreeBSD model for vendor software. FreeBSD has
> https://svnweb.freebsd.org/base/vendor/ and it contains the vendor
> source untouched and then the version
On 2016-04-30 23:50 +0800, printk wrote:
> Hi, will the new build system copy the headers to include too?
No, the new build system which you can see here:
https://git.rtems.org/amar/waf.git/
Does not do this.
You can see how to build it and get more details by following this thread:
On 2016-05-02 09:57 +0200, Christian Mauderer wrote:
>
> Just two thoughts on the tools. Both doesn't need instant answers.
> Please note that I don't intend to contradict the tools.
>
> I just took a quick glance on the linked pages but from that it seems
> that both tools are quite
The site is going down for some unplanned maintenance. While investigating
another issue I decided it was better to redo the entire site with a full
upgrade.
Sorry for the inconvenience it will be back tomorrow (2017-02-25) sometime!
Amar.
___
On 2017-03-28 12:43 -0400, Gedare Bloom wrote:
> The main thing to avoid is any dependency between you and another
> student. If you can both work productively and create new code in
> parallel, then #1 can work out. But if it requires close interaction
> to work, and there is a chance one
I've mucked about with the Git hooks in a question to fix the issue with not
all
tickets updating in track. I belive I've fixed it see my note here:
https://devel.rtems.org/ticket/3561#comment:9
If you see any errors when committing please let me know directly it should be
fine but just in
I've had to deal with this issue quite a lot in the past it can be really
annoying having to maintain separate repositories where we have to 'pin' a
version to the main repo. We don't really have a choice here however I would
suggest we do a mix of the two.
1. Any source/permissive files
On 2020-02-26 15:27 +1100, Chris Johns wrote:
>
> Great, I am OK with the patch being pused. If it breaks on sync it will show
> in
> the build not updating and I am sure we can sort it out.
Okay great I'll do that now then thank you!
Amar.
___
I've been working on setting up hardware testing in my lab at home. The Device
Tree documentation we have currently is horrible:
https://docs.rtems.org/branches/master/user/exe/device-tree.html
It's a list of command and descriptions about what it is but not what they do.
For instance look
Hi Niteesh, I have pushed the upgrade to the latest version of the theme.
Can you confirm this fixes the search box for you?
Thank you!
Amar.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 2020-02-26 13:59 +1100, Chris Johns wrote:
>
> Does this work on sync.rtems.org with a suitable virtualenv?
>
> This is how I build the online docs. :)
Shouldn't be an issue at all it's in-source no new dependencies. Try the patch
and see if it works? :) Works here!
Amar.
On 2020-02-26 18:46 +0100, Christian Mauderer wrote:
> Hello Amar,
>
> somehow I missed your response this morning. My filter for the mailing
> list normally keeps stuff with my name in the inbox but your answer
> didn't contain it and therefore it was hidden in the mailing list folder.
No
On 2020-03-02 09:41 +1100, Chris Johns wrote:
>
> I have managed to hack around the issue with the following command ...
>
> pip install sphinxcontrib-bibtex==0.4.1
>
> I am waiting for the build to be posted in the web server.
That sounds annoying sorry for the trouble. I use Python 3.7
On 2020-03-04 20:02 +1100, Chris Johns wrote:
>
> I am wondering how a user runs just the mkimake.py file once install. The
> rtems-tools repo normally packages a command in a wrapper that has has
> `/usr/bin/env python` and so $PATH etc works.
I added a python2 shebang in the 2nd commit it can
---
rtems/config/tools/rtems-tools-5-1.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rtems/config/tools/rtems-tools-5-1.cfg
b/rtems/config/tools/rtems-tools-5-1.cfg
index da22b4c..0c67901 100644
--- a/rtems/config/tools/rtems-tools-5-1.cfg
+++
On 2020-03-04 18:02 -0600, Joel Sherrill wrote:
> I think this is OK.??
>
> I will bump the newlib hash as soon as my patch to newlib is merged.
Great, thanks!
Amar.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 2020-03-04 19:43 -0700, Gedare Bloom wrote:
> Reviewing on my phone: I see added blank lines, try to avoid unnecessary
> whitespace/format changes with functional changes in same commit. Although we
> haven't settled in a style, none of the proposed ones use more than 2 blank
> lines between
On 2020-03-04 19:37 -0700, Gedare Bloom wrote:
> Quick note sort copyright lines??earlier years below later years.
Whoops, I know this already I'll fix it thanks.
Amar.
___
devel mailing list
devel@rtems.org
---
misc/tools/mkimage.py | 42 +-
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/misc/tools/mkimage.py b/misc/tools/mkimage.py
index 39a12a0..2b1524c 100755
--- a/misc/tools/mkimage.py
+++ b/misc/tools/mkimage.py
@@ -2,28 +2,28 @@
# A
Also changed 'python2' to 'python' in the shebang.
---
misc/tools/mkimage.py | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/misc/tools/mkimage.py b/misc/tools/mkimage.py
index 0845ee4..38ed11e 100755
--- a/misc/tools/mkimage.py
+++ b/misc/tools/mkimage.py
--- a/misc/tools/mkimage.py
+++ b/misc/tools/mkimage.py
@@ -3,6 +3,7 @@
# A quickly bashed together replacement for u-boot's mkimage written in python
#
# Copyright 2010 Craig Barker
+# Copyright 2020 Amar Takhar
#
# Redistribution and use in source and binary forms, with or without
This is limited to Python 2.6+
---
misc/tools/mkimage.py | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/misc/tools/mkimage.py b/misc/tools/mkimage.py
index 38ed11e..fd75f0a 100755
--- a/misc/tools/mkimage.py
+++ b/misc/tools/mkimage.py
@@ -27,6 +27,8 @@
#
This script does work but needs some user friendliness added which is
acknowledged by the author as it was meant as a quick replacement.
---
misc/tools/mkimage.py | 2 ++
misc/wscript | 1 +
2 files changed, 3 insertions(+)
mode change 100644 => 100755 misc/tools/mkimage.py
diff --git
I emailed Craig Barker to ask if he would release his mkimage Python rewrite
as 2BSD. He graciously accepted and you can see his work here:
https://github.com/cmbarker83/pythonmkimage
This is a verbatim commit of 35d6d from his repository.
---
misc/tools/mkimage.py | 139
On 2020-02-27 08:45 +0100, Christian Mauderer wrote:
>
> It's just another problem that I noted sometimes on the mailing list
> with RTEMS and libbsd: Sometimes libbsd doesn't compile with some odd
> error messages like unresolved symbols. Most of the time the problem is
> that libbsd has been
On 2020-02-28 09:25 -0700, Gedare Bloom wrote:
> >
> If there is enough work, and the work can be suitably identified, then
> it can also be a possible GSoC. There are also other possibilities to
> improve our existing Python code bases to adhere to some proposed
> Python coding conventions, which
---
misc/wscript | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/misc/wscript b/misc/wscript
index d82bde3..b3faf7b 100644
--- a/misc/wscript
+++ b/misc/wscript
@@ -79,13 +79,13 @@ def build(bld):
'tools/cmd-tftpproxy.py',
On 2020-02-28 12:39 -0600, Joel Sherrill wrote:
>
> We can't blanket upgrade tools to Python 3. The only thing I think we agreed
> when this was recently discussed is that we have categories of tools in Python
> and some have to be compatible with Python 2 and 3.
I wasn't suggesting that. I
On 2020-02-28 09:01 +1100, Chris Johns wrote:
> The issue of RTEMS version mismatch of blobs is a real issue waiting to hit
> our
> users and simply linking the blobs into the executable would solve this.
> This also looks like a blocker for CI testing.
I agree with everything you said but
On 2020-02-27 20:06 +0100, Christian Mauderer wrote:
> > The only good way to handle this is to have it all in 1 giant repository we
> > work
> > with. Every other solution is a pain no matter how well thought out it is.
> > I
> > personally lean more on the service side of things that it
caught breakage from a commit made.
Currently only Joel, Chris and myself are on this list. If you wish to be
added
please send me your full email that you use to commit with in the format of:
Amar Takhar
Otherwise realtime status is available at
https://buildbot.rtems.org/
Found by Buildbot here!
https://buildbot.rtems.org/#/builders/19/builds/47
FYI if anyone does want to make a quick check to see if the error is
reproducible Buildbot creates a snapshot with bootstrap already run on every
build for example for this build:
On 2020-02-05 07:49 +0100, Sebastian Huber wrote:
> Hello Amar,
>
> thanks for setting up the Buildbot. I will probably receive most of the
> Working -> Broken emails.
Sure. Yes I agree that is what I've seen. :)
> If you are subscribed to the bu...@rtems.org mailing list, do you
> already
Currently emails sent out directly are limited to Joel, Chris and myself. This
was setup during a testing phase.
Typically what will happen is if a Builder within Buildbot changes from:
Working -> Broken
Broken -> Working
It will send an email to the 'responsible users'. You can see a
On 2020-02-06 08:31 +1100, Chris Johns wrote:
> Can we enable this for one BSP from each tier 1 architectures?
Yes, can you provide a list?
> > Buildbot does support both Pushover and Pushjet as well.
>
> Is this like social media and that stuff? ;)
Both are apps that allow for android / ios
On 2020-02-05 20:28 -0700, Gedare Bloom wrote:
> I would like it to be a single email to indicate there is a new
> breakage. Enough to indicate "hey go take a look at the full build
> results! something is wrong here"
That's what it does. Breakage isn't always the same across builds. Waiting
On 2020-02-06 07:19 +0100, Christian Mauderer wrote:
> Someone applied a FreeBSD patch directly to libbsd (which works well).
> In that case git noted that the original author is in the "from" header
> and send him an email that his patch has been applied. He was a bit
> astonished to receive
On 2020-02-06 07:44 +0100, Christian Mauderer wrote:
> Like already said: I'm not against sending the mails. And the situation
> is quite unlikely in RTEMS core. But we should be aware of the
> possibility before enabling such an option.
Agreed and thank you for highlighting this. While I am
On 2020-02-07 16:17 +1100, Chris Johns wrote:
>
> Could we build an "always must build" BSP and if it builds a wider selection
> are
> built? The beaglebone black is my pick.
That's the way it already works now and has for years.
Look at the waterfall the process is:
1. Build snapshot
2.
On 2020-02-06 08:03 -0700, Gedare Bloom wrote:
> I agree with what you say. (And appreciate the unfunded work.)
Thank you.
> I still have reservations about the possibility to generate 250 emails
> all basically the same. Perhaps developers/committers should test
> every commit. Sometimes
On 2020-02-07 09:02 +0100, Sebastian Huber wrote:
> Currently, the build buildbot just build the BSPs with the tests. A next
> step could be to add test suite runs as well. It is a lot more easy to
> debug failures on one of the simulator BSPs even though they are not tier 1.
I actually have a
On 2020-02-08 09:31 +1100, Chris Johns wrote:
> >https://ftp.rtems.org/pub/rtems/people/amar/test1.jpg
> >
>
> That is flash. :)
Heh thanks, I set this up in August 2019 and it's been nagging at me since.
> You are not alone getting to this point. I know OAR has been setting
> something
On 2020-01-24 08:57 -0600, Joel Sherrill wrote:
>
> This failed because the tools are old.
Okay, I'll update those today thanks!
Amar.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 2020-02-05 13:12 +1100, Chris Johns wrote:
> I am OK with that. What do others think?
For example in the last breakage you can see who was responsible by going here
and clicking 'Responsible Users':
https://buildbot.rtems.org/#/builders/19/builds/47
These two would have received direct
On 2020-02-05 10:16 +1100, Chris Johns wrote:
>
> Should fails be posted to devel?
I don't think that's a good idea since it's possible that a commit could break
every BSP and then we'll get 1 email per BSP as they each fail.
I think it's okay if the developer breaking the build gets those
On 2020-02-05 10:15 +1100, Chris Johns wrote:
>
> Many thanks for the buildbot effort and all you do. It is an important part of
> RTEMS's development.
Thank you.
Amar.
___
devel mailing list
devel@rtems.org
On 2020-02-21 12:15 +1100, Chris Johns wrote:
>
> Does the Linux kernel rules apply to the 2 clause BSD license we have?
I don't think so but I've always included BSD licenses in the file as the
license expressly states that it should be included. This on top of adding an
SPDX marker.
Also,
Hi Niteesh, I updated it and created a patch for this here:
https://devel.rtems.org/ticket/3880/
It does fix the issue once it's approved I will push the changes. Thank you
for
highlighting this issue!
Amar.
___
devel mailing list
I've been running this version for a while now. It should fix any issues we're
having I tested it and it works fine.
See here for a ticket the patch is rather large:
https://devel.rtems.org/ticket/3880
Amar.
___
devel mailing list
devel@rtems.org
On 2020-02-13 17:42 -0500, Peter Dufault wrote:
>
> Can you explain this to those of us who are part-time git users?
> I pulled during this time frame, so I must "re-clone" or do a "forced push
> back".
See below.
> I assume "re-clone" means I "rm -rf" a local repository and, well, "re-clone".
Due to a mishap the main repository has been rewound two commits back to
d252e20ab.
The two commits removed were 2272825 and a994e646. You may have to do a force
pull if you grabbed these two commits before this happened.
Amar.
___
devel mailing
On 2020-02-13 15:16 +1100, Chris Johns wrote:
> It is useful if a user is deploying our documentation. I am not sure is
> something people building the docs normally do.
Yes it's actually the main method I've seen many use since it inlines all files
including images so it's just 1 HTML file
On 2020-02-13 07:20 +0100, Christian Mauderer wrote:
> Hello Amar,
Hey!
> Understood it. It still works when build locally so it shouldn't be a
> big problem fixing it. I just wasn't really aware of the single page
> version before and therefore I wasn't sure whether it should work or
> not.
On 2020-02-10 13:05 +1100, Chris Johns wrote:
> On 8/2/20 11:13 am, Amar Takhar wrote:
> > I was going to start with the Beaglebone and do TFTP to load the tests.
>
> I suggest you start with getting rtems-run to run any of the built tests. You
> will need ...
>
> 1.
On 2020-03-12 11:52 +0530, Anmol Mishra wrote:
> Hello,
> With whom can I discuss regarding douts, Any tentative??mentor open for
> guiding
> me, I have a few doubts regarding the project. Is Dr. Gedare going to be a
> tentative??mentor?
I am the mentor for this project. Can you please send any
On 2020-03-09 09:14 +1100, Chris Johns wrote:
> OK to push. Thank you for including the update to the tools with the tools
> change.
Sure, no prob.
Amar.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 2020-03-04 06:58 +0100, Sebastian Huber wrote:
>
> This is really nice. Getting mkimage for Windows was always a pain.
I've updated it to work under Python 2.7+ and switched to to use argparse plus
some other error checking.
Can you try this on your Windows machine to see how it works?
---
rtems/config/tools/rtems-tools-5-1.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rtems/config/tools/rtems-tools-5-1.cfg
b/rtems/config/tools/rtems-tools-5-1.cfg
index cf097c4..e7f6183 100644
--- a/rtems/config/tools/rtems-tools-5-1.cfg
+++
Also check for 'pytest' during configure if not installed print a warning
about installing it to run new test suite.
---
wscript | 9 +
1 file changed, 9 insertions(+)
diff --git a/wscript b/wscript
index bd7c54d..79ab78e 100644
--- a/wscript
+++ b/wscript
@@ -104,6 +104,8 @@ def
This converts three files:
error.py:
- Check for exceptions and error messages
path.py:
- Test params and setting module variables
macros.py:
- Test class with setup and shared module access
This should cover the bulk of what is required to convert the rest to pytest.
Also removes the
+#
+# RTEMS Tools Project (http://www.rtems.org/)
+# Copyright 2020 Amar Takhar
+# All rights reserved.
+#
+# This file is part of the RTEMS Tools package in 'rtems-tools'.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following
/conftest.py b/rtemstoolkit/conftest.py
new file mode 100644
index 000..3e1ec80
--- /dev/null
+++ b/rtemstoolkit/conftest.py
@@ -0,0 +1,37 @@
+# SPDX-License-Identifier: BSD-2-Clause
+
+# RTEMS Tools Project (http://www.rtems.org/)
+# Copyright (C) 2020 Amar Takhar
+#
+# Redistribution and use
On 2020-03-15 21:18 -0600, Gedare Bloom wrote:
>
> I found what I was thinking about:
> http://google.github.io/styleguide/pyguide.html#313-imports-formatting
>
> PEP has similar guidance:
> https://www.python.org/dev/peps/pep-0008/#imports
PEP8 is so old that even the Python project breaks
1 - 100 of 133 matches
Mail list logo
