[PATCH 0/2] *** Docs Update ***

[Cillian O'Donnell]

*** Just to note the rsb quick-start is all updated except for the output of 
--list-bsets because my setup only ever finds output for ../bare/config and not 
../source-builder/config so I left that bit out just in case. Maybe someone 
else can update that section to 4.12. ***

Cillian O'Donnell (2):
  rtems-docs/user/../quick.rst: Fix typo, hard coded path, code layout.
  docs/rsb/quick-start.rst: Fix typos, hard coded paths, version

 rsb/quick-start.rst  | 242 +--
 user/start/quick.rst |  15 ++--
 2 files changed, 129 insertions(+), 128 deletions(-)

-- 
2.7.4

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 1/2] rtems-docs/user/../quick.rst: Fix typo, hard coded path, code layout.

[Cillian O'Donnell]

---
 user/start/quick.rst | 15 ---
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/user/start/quick.rst b/user/start/quick.rst
index 47597af..8fc24f1 100644
--- a/user/start/quick.rst
+++ b/user/start/quick.rst
@@ -15,9 +15,9 @@ You need to have your development host set up and ready, the
 :ref:`development-host` covers what you need.
 
 This procedure does a development (unstable) build from Git for a POSIX
-host. You can refer to the specific section that cover the specific part of the
-process in detail if you have an issue. The output from the commands has been
-removed and replaced with ``...``.
+host. You can refer to the specific section that covers the specific part of
+the process in detail if you have an issue. The output from the commands has
+been removed and replaced with ``...``.
 
 Create a workspace, download the RTEMS Source Builder (RSB) and build a tool
 chain (See :ref:`rtems-tools-chain`):
@@ -34,7 +34,7 @@ chain (See :ref:`rtems-tools-chain`):
 ...
   $ cd rtems
   $ ../source-builder/sb-set-builder \
-  --prefix=/usr/home/chris/development/rtems/4.12 4.12/rtems-sparc
+  --prefix=$HOME/development/rtems/4.12 4.12/rtems-sparc
 ...
 
 Build the RTEMS Kernel (See :ref:`rtems-kernel`) by cloning the repository,
@@ -57,9 +57,10 @@ kernel:
   $ cd ..
   $ mkdir erc32
   $ cd erc32
-  $ $HOME/development/rtems/kernel/rtems/configure 
--prefix=$HOME/development/rtems/4.12 \
- --target=sparc-rtems4.12 --enable-rtemsbsp=erc32 
--enable-posix \
---disable-networking
+  $ $HOME/development/rtems/kernel/rtems/configure \
+--prefix=$HOME/development/rtems/4.12 \
+--target=sparc-rtems4.12 --enable-rtemsbsp=erc32 --enable-posix \
+--disable-networking
 ...
   $ make -j 8
 ...
-- 
2.7.4

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 2/2] docs/rsb/quick-start.rst: Fix typos, hard coded paths, version

[Cillian O'Donnell]

---
 rsb/quick-start.rst | 242 ++--
 1 file changed, 121 insertions(+), 121 deletions(-)

diff --git a/rsb/quick-start.rst b/rsb/quick-start.rst
index f39c0a6..387ab61 100644
--- a/rsb/quick-start.rst
+++ b/rsb/quick-start.rst
@@ -42,13 +42,13 @@ difficult to manage in production systems.
 The RSB by default will install (copy) the executables to a directory tree
 under the *prefix* you supply. To use the tools once finished just set your
 path to the ``bin`` directory under the *prefix* you use. In the examples
-that follow the *prefix* is ``$HOME/development/rtems/4.11`` and is set
+that follow the *prefix* is ``$HOME/development/rtems/4.12`` and is set
 using the ``--prefix`` option so the path you need to configure to build
 applications can be set with the following in a BASH shell:
 
 .. code-block:: shell
 
-  $ export PATH=$HOME/development/rtems/4.11/bin:$PATH
+  $ export PATH=$HOME/development/rtems/4.12/bin:$PATH
 
 Make sure you place the RTEMS tool path at the front of your path so they
 are searched first. RTEMS can provide newer versions of some tools your
@@ -74,15 +74,15 @@ Setup
 Setup a development work space::
 
 $ cd
-$ mkdir -p development/rtems/src
-$ cd development/rtems/src
+$ mkdir -p development/rtems
+$ cd development/rtems
 
 The RTEMS Source Builder is distributed as source. It is Python code so all you
 need to do is download the release's RSB tarball or clone the code directly
 from the RTEMS GIT repository::
 
-$ git clone git://git.rtems.org/rtems-source-builder.git
-$ cd rtems-source-builder
+$ git clone git://git.rtems.org/rtems-source-builder.git rsb
+$ cd rsb
 
 .. topic:: Workspaces
 
@@ -118,7 +118,7 @@ given a list of warnings about executable files not in the 
expected location
 however the executable was located somewhere in your environment's path. You
 will need to check each tool to determine if this is an issue. An executable
 not in the standard location may indicate it is not the host operating system's
-standard tool. It maybe ok or it could be buggy, only you can determine this.
+standard tool. It may be ok or it could be buggy, only you can determine this.
 
 The :ref:`Hosts` section lists packages you should install for common host
 operating systems. It maybe worth checking if you have those installed.
@@ -208,30 +208,30 @@ Building
 The quick start builds a SPARC tool set::
 
 $ ../source-builder/sb-set-builder --log=l-sparc.txt \   <1>
-  --prefix=$HOME/development/rtems/4.11 \   <2>
-  4.11/rtems-sparc   <3>
-Source Builder - Set Builder, v0.2.0
-Build Set: 4.11/rtems-sparc
+  --prefix=$HOME/development/rtems/4.12 \   <2>
+  4.12/rtems-sparc   <3>
+RTEMS Source Builder - Set Builder, 4.12
+Build Set: 4.12/rtems-sparc
 config: expat-2.1.0-1.cfg<4>
 package: expat-2.1.0-x86_64-freebsd9.1-1
 building: expat-2.1.0-x86_64-freebsd9.1-1
-config: tools/rtems-binutils-2.22-1.cfg<5>
-package: sparc-rtems4.11-binutils-2.22-1
-building: sparc-rtems4.11-binutils-2.22-1
-config: tools/rtems-gcc-4.7.2-newlib-1.20.0-1.cfg   <6>
-package: sparc-rtems4.11-gcc-4.7.2-newlib-1.20.0-1
-building: sparc-rtems4.11-gcc-4.7.2-newlib-1.20.0-1
-config: tools/rtems-gdb-7.5.1-1.cfg  <7>
-package: sparc-rtems4.11-gdb-7.5.1-1
-building: sparc-rtems4.11-gdb-7.5.1-1
-installing: rtems-4.11-sparc-rtems4.11-1 -> 
/home/chris/development/rtems/4.11 <8>
-installing: rtems-4.11-sparc-rtems4.11-1 -> 
/home/chris/development/rtems/4.11
-installing: rtems-4.11-sparc-rtems4.11-1 -> 
/home/chris/development/rtems/4.11
-installing: rtems-4.11-sparc-rtems4.11-1 -> 
/home/chris/development/rtems/4.11
+config: tools/rtems-binutils-2.28-1.cfg<5>
+package: sparc-rtems4.12-binutils-2.28-1
+building: sparc-rtems4.12-binutils-2.28-1
+config: tools/rtems-gcc-7.1.0-newlib-2.5.0-1.cfg   <6>
+package: sparc-rtems4.12-gcc-7.1.0-newlib-2.5.0-1
+building: sparc-rtems4.12-gcc-7.1.0-newlib-2.5.0-1
+config: tools/rtems-gdb-7.12.1-1.cfg  <7>
+package: sparc-rtems4.12-gdb-7.12.1-1
+building: sparc-rtems4.12-gdb-7.12.1-1
+installing: rtems-4.12-sparc-rtems4.12-1 -> $HOME/development/rtems/4.12 
<8>
+installing: rtems-4.12-sparc-rtems4.12-1 -> $HOME/development/rtems/4.12
+installing: rtems-4.12-sparc-rtems4.12-1 -> $HOME/development/rtems/4.12
+installing: rtems-4.12-sparc-rtems4.12-1 -> $HOME/development/rtems/4.12
 cleaning: expat-2.1.0-x86_64-freebsd9.1-1 <9>
-cleaning: sparc-rtems4.11-binutils-2.22-1
-cleaning: sparc-rtems4.11-gcc-4.7.2-newlib-1.20.0-1
-cleaning: sparc-rtems4.11-gdb-7.5.1-1
+cleaning: sparc-rtems4.12-binutils-2.28-1
+cleaning: sparc-rtems4.12-gcc-7.1.0-newlib-2.5.0-1
+cleaning: sparc-rtems4.12-gdb-7.12.1-1
 Bui

[PATCH v4] User Manual: Added rtems-tester in the docs

[Tanu Hari Dixit]

Added as part of Tools.
Made changes according to Chris' review
Also removed the ini format part inline with
the new release that is expected.
---
 user/tools/index.rst  |   1 +
 user/tools/tester.rst | 446 ++
 2 files changed, 447 insertions(+)
 create mode 100644 user/tools/tester.rst

diff --git a/user/tools/index.rst b/user/tools/index.rst
index d77a7ca..613ceb9 100644
--- a/user/tools/index.rst
+++ b/user/tools/index.rst
@@ -21,3 +21,4 @@ executables.
 .. include:: exeinfo.rst
 .. include:: trace-linker.rst
 .. include:: bsp-builder.rst
+.. include:: tester.rst
diff --git a/user/tools/tester.rst b/user/tools/tester.rst
new file mode 100644
index 000..ae8c3b6
--- /dev/null
+++ b/user/tools/tester.rst
@@ -0,0 +1,446 @@
+.. comment SPDX-License-Identifier: CC-BY-SA-4.0
+
+.. comment: Copyright (c) 2017 Chris Johns 
+.. comment: All rights reserved.
+
+RTEMS Tester
+
+
+.. index:: Tools, rtems-tester
+
+The RTEMS Tester is a test framework. It includes a command line interface to
+run tests on supported targets. The framework provides back-end support for
+common simulators and debuggers. The board support package (BSP) configurations
+for RTEMS are provided and can be used to run all the tests provided with
+RTEMS. The framework is not specific to RTEMS and can be configured to run any
+suitable application.
+
+RTEMS is an embedded operating system and is cross-compiled on a range of host
+machines. The executables run on the target hardware and this can vary widely
+from open source simulators, commercial simulators, debuggers with simulators,
+to debuggers with hardware specific pods and devices. Testing RTEMS requires
+the cross-compiled test executable is transferred to the target hardware,
+executed and the output returned to the host where it is analyzed to determine
+the test result. The RTEMS Tester provides a framework to do this.
+
+Running all the RTEMS tests on your target is very important. It provides you
+with a traceable record showing that your RTEMS version and its tools are
+working at the level the RTEMS development team expect when releasing
+RTEMS. Being able to easily run the tests and verify the results is critical in
+maintaining a high standard.
+
+This document is for users of the RTEMS Tester as well as those wanting to
+develop, extend and investigate the RTEMS Tester.
+
+Available BSP testers
+-
+
+You can list the available BSP testers with:
+
+.. code-block:: shell
+
+$ rtems-test --list-bsps
+arm920
+beagleboardxm
+jmr3904-run
+jmr3904
+mcf5235
+psim-run
+psim
+realview_pbx_a9_qemu
+sis-run
+sis
+xilinx_zynq_a9_qemu
+xilinx_zynq_a9_qemu_smp
+xilinx_zynq_zc706
+xilinx_zynq_zc706_qemu
+
+.. note:: The list is growing all the time and if your BSP is not supported we 
+  encourage you to add it and submit the configuration back to the 
+  project.
+
+Some of the BSPs may appear more than once in the list. These are aliased BSP
+configurations that may use a different back-end. An example is the erc32 BSP. 
+There is the ``erc32`` tester which uses the GDB back-end and the 
+``erc32-run`` tester which uses the ``run`` command for erc32. We will show 
+how to use :program:`rtems-test` command with the erc32 BSP because it is easy 
+to build an use.
+
+Building RTEMS Tests
+
+
+Build the RTEMS Kernel (See :ref:`rtems-kernel`) by cloning the repository, 
+running the ``bootstrap`` procecure, building and finally installing the 
+kernel. Be sure to enable tests by using ``--enable-tests`` option with 
+configure after running ``bootstrap``.
+
+.. code-block:: shell
+
+$ ../../rtems.git/configure --target=sparc-rtems4.12 \
+--enable-tests --enable-rtemsbsp=erc32
+$ make 
+
+Add the -j option to the make command with the number of cores to run the 
+build parallel where it can.
+
+Building all the tests takes time and it uses more disk so be patient. When
+finished all the tests will be built and ready to run. Before running all the 
+tests it is a good idea to run the ``hello`` test. The ``hello`` test is an 
+RTEMS version of the classic "Hello World" example and running it shows you 
+have a working tool chain and build of RTEMS ready to run the tests. Using the 
+run command:
+
+.. code-block:: shell
+
+$ sparc-rtems4.12-run 
sparc-rtems4.12/c/erc32/testsuites/samples/hello/hello.exe
+
+*** BEGIN OF TEST HELLO WORLD ***
+Hello World
+*** END OF TEST HELLO WORLD ***
+
+The run command is the GDB simulator without the GDB part.
+
+Running the example using GDB:
+
+.. code-block:: shell
+
+$ sparc-rtems4.12-gdb 
sparc-rtems4.12/c/erc32/testsuites/samples/hello/hello.exe
+GNU gdb (GDB) 7.12
+Copyright (C) 2016 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later 

+This is free softwa

[PATCH v4 2/2] User Manual: Added ini format in rtems-tester

[Tanu Hari Dixit]

Added specification for ini format for configuration
files in documentation of rtems-tester
---
 user/tools/tester.rst | 134 ++
 1 file changed, 134 insertions(+)

diff --git a/user/tools/tester.rst b/user/tools/tester.rst
index ae8c3b6..966a373 100644
--- a/user/tools/tester.rst
+++ b/user/tools/tester.rst
@@ -66,6 +66,140 @@ There is the ``erc32`` tester which uses the GDB back-end 
and the
 how to use :program:`rtems-test` command with the erc32 BSP because it is easy 
 to build an use.
 
+Adding support for a BSP to the tester
+--
+
+To add support for a BSP, one should add a configuration file in 
+``rtems-tools.git/tester/rtems/testing/bsps``. The configuration files 
+should be specified in an INI file. The configuration files provide a 
+means to the backend of `rtems-tester` to automate the running of tests.
+There is the  tester which uses the GDB back-end and the 
``-run`` 
+tester which uses the command line version of the respective simulator.
+The general format for specifying an INI configuration file is as follows:
+
+``.ini``:
+
+.. code-block:: shell
+
+[]
+bsp = ''
+gdb = '%{_rtscripts}/gdb.cfg'
+arch = ''
+
+[gdb_script]
+gdb_script ='_gdb_script'
+_gdb_script =   ''
+
+``-run.ini``:
+
+.. code-block:: shell
+
+[]
+bsp = ''
+
+[run]
+run = '%{_rtscripts}/run.cfg'
+arch = ''
+bsp_run_cmd = '%{rtems_tools}/%{bsp_arch}-rtems%{rtems_version}-run'
+bsp_run_opts = ''
+
+Here is an example:
+
+``arm7tdmi.ini``:
+
+.. code-block:: shell
+
+[arm7tdmi]
+bsp = 'arm7tdmi'
+gdb = '%{_rtscripts}/gdb.cfg'
+arch = 'arm'
+
+[gdb_script]
+gdb_script ='arm7tdmi_gdb_script'
+arm7tdmi_gdb_script =   'target sim
+load
+run'
+
+``arm7tdmi-run.ini``:
+
+.. code-block:: shell
+
+[arm7tdmi]
+bsp = 'arm7tdmi'
+
+[run]
+run = '%{_rtscripts}/run.cfg'
+arch = 'arm'
+bsp_run_cmd = '%{rtems_tools}/%{bsp_arch}-rtems%{rtems_version}-run'
+bsp_run_opts = '-a -nouartrx'
+
+If the tester should run the tests on qemu for a bsp, the given pattern can 
+be followed:
+
+.. code-block:: shell
+
+[]
+bsp = ''
+
+[qemu-script]
+run = '%{_rtscripts}/qemu.cfg'
+arch = ''
+opts = '%{qemu_opts_base} %{qemu_opts_no_net} -m 32M'
+
+For instance,
+
+``generic_or1k.ini``:
+
+.. code-block:: shell
+
+[generic_or1k]
+bsp = 'generic_or1k'
+
+[qemu-script]
+run = '%{_rtscripts}/qemu.cfg'
+arch = 'or32'
+opts = '%{qemu_opts_base} %{qemu_opts_no_net} -m 32M'
+
+User can also provide a "settings.ini" file in case a configuration file needs 
+a path to, for instance, a first stage bootloader (fsbl) that is placed 
+somewhere in the host machine. The settings.ini file can be passed with 
+``rtems-test --with-settings = /path/to/settings/file`` option. The 
+.ini can contain defaults and the settings file can contain the 
+user-specified configuration.
+
+
+``xilinx_zynq_zc706.ini``:
+
+.. code-block:: shell
+
+[xilinx_zynq_zc706]
+bsp = 'xilinx_zynq_zc706'
+jobs = '1'
+
+[gdb-script]
+gdb = '%{_rtscripts}/gdb.cfg'
+arch = 'arm'
+bsp_tty_dev =  ${settings:bsp_tty_dev}
+gdb_script = 'xilinx_zynq_zc706_gdb_script'
+xilinx_zynq_zc706_gdb_script = 'target remote kaka:
+mon load_image ${settings:path_to_fsbl} 0 elf
+mon resume 0
+mon sleep 4000
+mon halt
+load
+b bsp_reset
+continue'
+
+``settings.ini``:
+
+.. code-block:: shell
+
+[settings]
+bsp_tty_dev = '/dev/cu.SLAB_USBtoUART'
+path_to_fsbl = '/path/to/fsbl'
+
 Building RTEMS Tests
 
 
-- 
2.1.4

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v3] User Manual: Added rtems-tester in the docs

[Tanu Hari Dixit]

Thank you, Chris, for the review. I have made the changes and sent
again as version 4 patches. I have split the commits into 2 parts (one
not containing the ini bits for v4.12 release and the other one
containing it). Kindly review them.
Thank you for your time.
Tanu.

On Thu, Jun 1, 2017 at 7:10 AM, Chris Johns  wrote:
> Thanks for patch. Comments in the email.
>
> Note, I seem to have broken the section headings and will fix soon.
>
> On 31/05/2017 23:33, Tanu Hari Dixit wrote:
>> Adds as part of Tools
>> ---
>>  user/tools/index.rst|   1 +
>>  user/tools/rtems-tester.rst | 636 
>> 
>>  2 files changed, 637 insertions(+)
>>  create mode 100644 user/tools/rtems-tester.rst
>>
>> diff --git a/user/tools/index.rst b/user/tools/index.rst
>> index d77a7ca..9e2ca89 100644
>> --- a/user/tools/index.rst
>> +++ b/user/tools/index.rst
>> @@ -21,3 +21,4 @@ executables.
>>  .. include:: exeinfo.rst
>>  .. include:: trace-linker.rst
>>  .. include:: bsp-builder.rst
>> +.. include:: rtems-tester.rst
>
> Please call the file 'tester.rst'. This makes the naming consistent with the
> other commands (hint: git mv ...).
>
>> diff --git a/user/tools/rtems-tester.rst b/user/tools/rtems-tester.rst
>> new file mode 100644
>> index 000..425a1fb
>> --- /dev/null
>> +++ b/user/tools/rtems-tester.rst
>> @@ -0,0 +1,636 @@
>> +.. comment SPDX-License-Identifier: CC-BY-SA-4.0
>> +
>> +.. comment: Copyright (c) 2017 Chris Johns 
>> +.. comment: All rights reserved.
>> +
>> +RTEMS Tester
>> +
>> +
>> +.. index:: Tools, rtems-tester
>> +
>> +The RTEMS Tester is a test framework. It includes a command line interface 
>> to
>> +run tests on supported targets. The framework provides back-end support for
>> +common simulators and debuggers. The board support package (BSP) 
>> configurations
>> +for RTEMS are provided and can be used to run all the tests provided with
>> +RTEMS. The framework is not specific to RTEMS and can be configured to run 
>> any
>> +suitable application.
>> +
>> +RTEMS is an embedded operating system and is cross-compiled on a range of 
>> host
>> +machines. The executables run on the target hardware and this can vary 
>> widely
>> +from open source simulators, commercial simulators, debuggers with 
>> simulators,
>> +to debuggers with hardware specific pods and devices. Testing RTEMS requires
>> +the cross-compiled test executable is transferred to the target hardware,
>> +executed and the output returned to the host where it is analyzed to 
>> determine
>> +the test result. The RTEMS Tester provides a framework to do this.
>> +
>> +Running all the RTEMS tests on your target is very important. It provides 
>> you
>> +with a traceable record showing that your RTEMS version and its tools are
>> +working at the level the RTEMS development team expect when releasing
>> +RTEMS. Being able to easily run the tests and verify the results is 
>> critical in
>> +maintaining a high standard.
>> +
>> +The RTEMS Tester contains:
>> +
>> +* Command line tool (``rtems-test``)
>
> Please use ":program:`rtems-test`". There are other places that need updating.
>
>> +* BSP Configuration scripts
>> +* Back-end Configuration scripts
>> +* Back-end Python classes
>> +* Python based framework
>> +
>> +This document is for users of the RTEMS Tester as well as those wanting to
>> +develop, extend and investigate the RTEMS Tester.
>
> I think "The RTEMS Tester contains:" ... here can be removed.
>
>> +
>> +License
>> +---
>> +
>> +The RTEMS Tester is part of the RTEMS Tools Project. The code is released 
>> under
>> +the OSI approved "The BSD 2-Clause License". It is free to use and we 
>> encourage
>> +this, including on operating systems other than RTEMS.
>> +
>> +The code and command line tools must retain the same names and always 
>> reference
>> +the RTEMS Tools Project.
>> +
>
> This section can be removed.
>
>> +Quick Start
>> +---
>> +
>> +The quick start will show you how to run the test suite for a BSP. It will
>> +explain how to get the RTEMS Tester, set it up and run the tests for the 
>> erc32
>> +BSP. It assumes you have a valid SPARC tool chain and have built the erc32 
>> BSP
>> +version of RTEMS 4.12.
>> +
>> +Setup
>> +-
>> +
>> +Set up a development work space:
>> +
>> +.. code-block:: shell
>> +
>> +$ cd
>> +$ mkdir -p development/rtems/test
>> +$ cd development/rtems/test
>> +
>> +First fetch the RTEMS tester from the RTEMS Tools repository:
>> +
>> +.. code-block:: shell
>> +
>> +$ git clone git://git.rtems.org/rtems-tools.git rtems-tools.git
>> +$ cd rtems-tools.git/tester
>> +
>
> This section is not needed anymore. The User Manual should have covered this
> already.
>
>> +Available BSP testers
>> +-
>> +
>> +You can list the available BSP testers with:
>> +
>> +.. code-block:: shell
>> +
>> +$ ./rtems-test --list-bsps
>
>$ rtems-test --list-bsps
>
>> +arm920
>> +beagleboardxm

Re: Building RISC-V BSP

[Denis Obrezkov]

So, am I understand right, that I should make my repo, submit commits to it,
produce patches and send them to your repo as pool requests?
And should I make my repo by cloning yours?

2017-06-02 2:02 GMT+03:00 Hesham Almatary :

> Hi Denis,
>
> On Fri, Jun 2, 2017 at 1:27 AM, Denis Obrezkov 
> wrote:
> > Hello Hesham,
> >
> > should I apply your patches? or should I paste all of them to
> > some directory (rsb has several 'patches' folders).
> >
> You only need to apply this patch [1] to RSB and build the tools again.
>
> [1] https://lists.rtems.org/pipermail/devel/2017-May/017951.html
> > Also, could you describe our workflow? In the context of with what
> > repository
> >  I should work and where I should direct my pull requests.
> >
> Since the port is not upstream yet, you can submit PRs to my GitHub
> repo in the time being until we get it upstreamed. After this you can
> submit patches for review to this mailing list.
>
> > 2017-06-01 5:09 GMT+03:00 Hesham Almatary :
> >>
> >> Hi Denis,
> >>
> >> I submitted two patches for the tools, please use the latest only and
> >> rebuild the tools. This should avoid the newlib issues you had above
> >> as it uses main riscv patches.
> >>
> >> I'll look into the port this weekend and submit fixes unless you beat
> >> me to it. Meanwhile, you can submit error messages and I'll see if I
> >> can help.
> >>
> >> Keep the good work.
> >>
> >> Cheers,
> >> Hesham
> >>
> >> On Thu, Jun 1, 2017 at 12:04 AM, Denis Obrezkov <
> denisobrez...@gmail.com>
> >> wrote:
> >> > 2017-05-31 16:39 GMT+03:00 Denis Obrezkov :
> >> >>
> >> >> Thanks, I downloaded it.
> >> >> There was a mistake also that _JBLEN wasn't defined in
> machine/setjmp.h
> >> >> I don't know the exact value, so I did the following:
> >> >> #ifdef __riscv
> >> >>
> >> >> /* TBD: not the exact number */
> >> >>
> >> >> #define _JBLEN 16
> >> >>
> >> >> #endif
> >> >>
> >> >> Now, it compiles further. But then I get the error:
> >> >> riscv32-rtems4.12-gcc --pipe -B../../../lib/
> >> >> -B../../../riscv_generic/lib/
> >> >> -specs bsp_specs -qrtems -DPACKAGE_NAME=\"rtems-c-src\"
> >> >> -DPACKAGE_TARNAME=\"rtems-c-src\" -DPACKAGE_VERSION=\"4.11.99.0\"
> >> >> -DPACKAGE_STRING=\"rtems-c-src\ 4.11.99.0\"
> >> >> -DPACKAGE_BUGREPORT=\"https://devel.rtems.org/newticket\";
> >> >> -DPACKAGE_URL=\"\"
> >> >> -I.
> >> >>
> >> >> -I/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip
> >> >> -isystem ../../../riscv_generic/lib/include   -O0 -g -Wall
> >> >> -Wmissing-prototypes -Wimplicit-function-declaration
> >> >> -Wstrict-prototypes
> >> >> -Wnested-externs -MT display/libdisplay_a-disp_hcms29xx.o -MD -MP
> -MF
> >> >> display/.deps/libdisplay_a-disp_hcms29xx.Tpo -c -o
> >> >> display/libdisplay_a-disp_hcms29xx.o `test -f
> 'display/disp_hcms29xx.c'
> >> >> ||
> >> >> echo
> >> >>
> >> >> '/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/'`display/disp_hcms29xx.c
> >> >> riscv32-rtems4.12-gcc: error: bsp_specs: No such file or directory
> >> >>
> >> >> So, I inserted it manually. But I can't figure out, why it wasn't
> >> >> copied
> >> >> automatically.
> >> >>
> >> >> Now I have an error:
> >> >> riscv32-rtems4.12-gcc --pipe -B../../../lib/
> >> >> -B../../../riscv_generic/lib/
> >> >> -specs bsp_specs -qrtems -DPACKAGE_NAME=\"rtems-c-src\"
> >> >> -DPACKAGE_TARNAME=\"rtems-c-src\" -DPACKAGE_VERSION=\"4.11.99.0\"
> >> >> -DPACKAGE_STRING=\"rtems-c-src\ 4.11.99.0\"
> >> >> -DPACKAGE_BUGREPORT=\"https://devel.rtems.org/newticket\";
> >> >> -DPACKAGE_URL=\"\"
> >> >> -I.
> >> >>
> >> >> -I/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip
> >> >> -isystem ../../../riscv_generic/lib/include   -O0 -g -Wall
> >> >> -Wmissing-prototypes -Wimplicit-function-declaration
> >> >> -Wstrict-prototypes
> >> >> -Wnested-externs -MT display/libdisplay_a-disp_hcms29xx.o -MD -MP
> -MF
> >> >> display/.deps/libdisplay_a-disp_hcms29xx.Tpo -c -o
> >> >> display/libdisplay_a-disp_hcms29xx.o `test -f
> 'display/disp_hcms29xx.c'
> >> >> ||
> >> >> echo
> >> >>
> >> >> '/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/'`display/disp_hcms29xx.c
> >> >>
> >> >>
> >> >> /home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/display/disp_hcms29xx.c:26:10:
> >> >> fatal error: bsp.h: No such file or directory
> >> >>  #include 
> >> >>
> >> >> It seems that configure scripts should be modified.
> >> >>
> >> >> 2017-05-31 8:46 GMT+03:00 Hesham Almatary  >:
> >> >>>
> >> >>> Hi Denis,
> >> >>>
> >> >>> Please use priv-1.10 branch. I rebased it (against master) and added
> >> >>> some fixes to make the build progress. Still, there's more work
> >> >>> needed. Your contributions are welcomed.
> >> >>>
> >> >>> Cheers,
> >> >>> Hesham
> >> >>> .
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >> Regards, Denis Obrezkov
> >> >
> >> > I think I worked it out. In a few da

[PATCH] implementation of inttypes.h and test related to its methods

[aadit0402]

---
 cpukit/Makefile.am   |   1 +
 cpukit/configure.ac  |   1 +
 cpukit/inttypes/Makefile.am  |  14 +++
 cpukit/inttypes/imaxabs.c|  40 +
 cpukit/inttypes/imaxdiv.c|  50 +++
 cpukit/inttypes/strtoimax.c  | 117 +
 cpukit/inttypes/strtoumax.c  | 116 +
 cpukit/inttypes/wcstoimax.c  | 125 +++
 cpukit/inttypes/wcstoumax.c  | 119 +
 testsuites/samples/Makefile.am   |   1 +
 testsuites/samples/configure.ac  |   1 +
 testsuites/samples/psxinttypes01/Makefile.am |  22 +
 testsuites/samples/psxinttypes01/init.c  |  69 +++
 testsuites/samples/psxinttypes01/psxid01.doc |  35 
 testsuites/samples/psxinttypes01/psxid01.scn |  38 
 15 files changed, 749 insertions(+)
 create mode 100644 cpukit/inttypes/Makefile.am
 create mode 100644 cpukit/inttypes/imaxabs.c
 create mode 100644 cpukit/inttypes/imaxdiv.c
 create mode 100644 cpukit/inttypes/strtoimax.c
 create mode 100644 cpukit/inttypes/strtoumax.c
 create mode 100644 cpukit/inttypes/wcstoimax.c
 create mode 100644 cpukit/inttypes/wcstoumax.c
 create mode 100644 testsuites/samples/psxinttypes01/Makefile.am
 create mode 100644 testsuites/samples/psxinttypes01/init.c
 create mode 100644 testsuites/samples/psxinttypes01/psxid01.doc
 create mode 100644 testsuites/samples/psxinttypes01/psxid01.scn

diff --git a/cpukit/Makefile.am b/cpukit/Makefile.am
index ae5ed9b..045017e 100644
--- a/cpukit/Makefile.am
+++ b/cpukit/Makefile.am
@@ -7,6 +7,7 @@ include $(top_srcdir)/automake/multilib.am
 _SUBDIRS = . score rtems sapi posix
 _SUBDIRS += dev
 _SUBDIRS += dtc/libfdt
+_SUBDIRS += inttypes
 _SUBDIRS += libcrypt
 _SUBDIRS += libcsupport libblock libfs
 _SUBDIRS += libdrvmgr
diff --git a/cpukit/configure.ac b/cpukit/configure.ac
index b0aa9a0..ad0865b 100644
--- a/cpukit/configure.ac
+++ b/cpukit/configure.ac
@@ -461,6 +461,7 @@ score/cpu/sparc64/Makefile
 score/cpu/v850/Makefile
 score/cpu/no_cpu/Makefile
 posix/Makefile
+inttypes/Makefile
 libblock/Makefile
 libdrvmgr/Makefile
 libfs/Makefile
diff --git a/cpukit/inttypes/Makefile.am b/cpukit/inttypes/Makefile.am
new file mode 100644
index 000..c90b872
--- /dev/null
+++ b/cpukit/inttypes/Makefile.am
@@ -0,0 +1,14 @@
+include $(top_srcdir)/automake/multilib.am
+include $(top_srcdir)/automake/compile.am
+
+
+noinst_LIBRARIES = libinttypes.a
+
+libinttypes_a_SOURCES = imaxdiv.c imaxabs.c strtoimax.c strtoumax.c 
wcstoimax.c wcstoumax.c
+
+libinttypes_a_CPPFLAGS = $(AM_CPPFLAGS) 
+
+
+#include $(srcdir)/preinstall.am
+include $(top_srcdir)/automake/subdirs.am
+include $(top_srcdir)/automake/local.am
diff --git a/cpukit/inttypes/imaxabs.c b/cpukit/inttypes/imaxabs.c
new file mode 100644
index 000..525e9c0
--- /dev/null
+++ b/cpukit/inttypes/imaxabs.c
@@ -0,0 +1,40 @@
+/*-
+ * Copyright (c) 2001 Mike Barcroft 
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ *notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ *notice, this list of conditions and the following disclaimer in the
+ *documentation and/or other materials provided with the distribution.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ */
+#if HAVE_CONFIG_H
+#include "config.h"
+#endif
+
+#include 
+#include 
+
+#include 
+
+
+intmax_t
+imaxabs(intmax_t j)
+{
+  return (j < 0 ? -j : j);
+}
diff --git a/cpukit/inttypes/imaxdiv.c b/cpukit/inttypes/imaxdiv.c
new file mode 100644
index 000..7992caa
--- /dev/null
+++ b/cpukit/inttypes/imaxdiv.c
@@ -0,0 +1,50 @@
+/*-
+ * Copyright (c) 2001 Mike Barcroft 
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of sour

Re: [PATCH] implementation of inttypes.h and test related to its methods

[Chris Johns]

On 02/06/2017 09:35, aadit0402 wrote:

Could you please use a real name in the commit message?

Thank you.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 2/2] implementation of inttypes.h and test related to its methods

[Aditya Upadhyay]

From: aadit0402 

---
 cpukit/Makefile.am   |   1 +
 cpukit/configure.ac  |   1 +
 cpukit/inttypes/Makefile.am  |  14 +++
 cpukit/inttypes/imaxabs.c|  40 +
 cpukit/inttypes/imaxdiv.c|  50 +++
 cpukit/inttypes/strtoimax.c  | 117 +
 cpukit/inttypes/strtoumax.c  | 116 +
 cpukit/inttypes/wcstoimax.c  | 125 +++
 cpukit/inttypes/wcstoumax.c  | 119 +
 testsuites/samples/Makefile.am   |   1 +
 testsuites/samples/configure.ac  |   1 +
 testsuites/samples/psxinttypes01/Makefile.am |  22 +
 testsuites/samples/psxinttypes01/init.c  |  69 +++
 testsuites/samples/psxinttypes01/psxid01.doc |  35 
 testsuites/samples/psxinttypes01/psxid01.scn |  38 
 15 files changed, 749 insertions(+)
 create mode 100644 cpukit/inttypes/Makefile.am
 create mode 100644 cpukit/inttypes/imaxabs.c
 create mode 100644 cpukit/inttypes/imaxdiv.c
 create mode 100644 cpukit/inttypes/strtoimax.c
 create mode 100644 cpukit/inttypes/strtoumax.c
 create mode 100644 cpukit/inttypes/wcstoimax.c
 create mode 100644 cpukit/inttypes/wcstoumax.c
 create mode 100644 testsuites/samples/psxinttypes01/Makefile.am
 create mode 100644 testsuites/samples/psxinttypes01/init.c
 create mode 100644 testsuites/samples/psxinttypes01/psxid01.doc
 create mode 100644 testsuites/samples/psxinttypes01/psxid01.scn

diff --git a/cpukit/Makefile.am b/cpukit/Makefile.am
index ae5ed9b..045017e 100644
--- a/cpukit/Makefile.am
+++ b/cpukit/Makefile.am
@@ -7,6 +7,7 @@ include $(top_srcdir)/automake/multilib.am
 _SUBDIRS = . score rtems sapi posix
 _SUBDIRS += dev
 _SUBDIRS += dtc/libfdt
+_SUBDIRS += inttypes
 _SUBDIRS += libcrypt
 _SUBDIRS += libcsupport libblock libfs
 _SUBDIRS += libdrvmgr
diff --git a/cpukit/configure.ac b/cpukit/configure.ac
index b0aa9a0..ad0865b 100644
--- a/cpukit/configure.ac
+++ b/cpukit/configure.ac
@@ -461,6 +461,7 @@ score/cpu/sparc64/Makefile
 score/cpu/v850/Makefile
 score/cpu/no_cpu/Makefile
 posix/Makefile
+inttypes/Makefile
 libblock/Makefile
 libdrvmgr/Makefile
 libfs/Makefile
diff --git a/cpukit/inttypes/Makefile.am b/cpukit/inttypes/Makefile.am
new file mode 100644
index 000..c90b872
--- /dev/null
+++ b/cpukit/inttypes/Makefile.am
@@ -0,0 +1,14 @@
+include $(top_srcdir)/automake/multilib.am
+include $(top_srcdir)/automake/compile.am
+
+
+noinst_LIBRARIES = libinttypes.a
+
+libinttypes_a_SOURCES = imaxdiv.c imaxabs.c strtoimax.c strtoumax.c 
wcstoimax.c wcstoumax.c
+
+libinttypes_a_CPPFLAGS = $(AM_CPPFLAGS) 
+
+
+#include $(srcdir)/preinstall.am
+include $(top_srcdir)/automake/subdirs.am
+include $(top_srcdir)/automake/local.am
diff --git a/cpukit/inttypes/imaxabs.c b/cpukit/inttypes/imaxabs.c
new file mode 100644
index 000..525e9c0
--- /dev/null
+++ b/cpukit/inttypes/imaxabs.c
@@ -0,0 +1,40 @@
+/*-
+ * Copyright (c) 2001 Mike Barcroft 
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ *notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ *notice, this list of conditions and the following disclaimer in the
+ *documentation and/or other materials provided with the distribution.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ */
+#if HAVE_CONFIG_H
+#include "config.h"
+#endif
+
+#include 
+#include 
+
+#include 
+
+
+intmax_t
+imaxabs(intmax_t j)
+{
+  return (j < 0 ? -j : j);
+}
diff --git a/cpukit/inttypes/imaxdiv.c b/cpukit/inttypes/imaxdiv.c
new file mode 100644
index 000..7992caa
--- /dev/null
+++ b/cpukit/inttypes/imaxdiv.c
@@ -0,0 +1,50 @@
+/*-
+ * Copyright (c) 2001 Mike Barcroft 
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redis

Re: [rtems commit] bsp/motorola_powerpc: Fix for Binutils 2.28+

[Chris Johns]

On 02/06/2017 15:11, Sebastian Huber wrote:
> Module:rtems
> Branch:master
> Commit:7203b70be0266cdb4830537dfc8fd6189851708c
> Changeset: 
> http://git.rtems.org/rtems/commit/?id=7203b70be0266cdb4830537dfc8fd6189851708c
> 
> Author:Sebastian Huber 
> Date:  Thu Jun  1 19:04:05 2017 +0200
> 
> bsp/motorola_powerpc: Fix for Binutils 2.28+
> 
> There are mismatched sections in the bootloader input:
> 
> ld: Warning: ticker.exe uses hard float, ticker.ralf uses soft float
> ld: ticker.exe: compiled normally and linked with modules compiled with 
> -mrelocatable
> ld: failed to merge target specific data of file ticker.exe
> 
> Suppress this error explicitly.

Thank you for fixing this. A binutils observation ...

Yes an error cause the build fails so 

> 
> ---
> 
>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg | 1 
> +
>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mtx603e.cfg| 1 
> +
>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mvme2100.cfg   | 1 
> +
>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mvme2307.cfg   | 1 
> +
>  .../lib/libbsp/powerpc/motorola_powerpc/make/custom/qemuprep-altivec.cfg | 1 
> +
>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/qemuprep.cfg   | 1 
> +
>  6 files changed, 6 insertions(+)
> 
> diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg 
> b/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg
> index 98e8fd9..67d1766 100644
> --- a/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg
> +++ b/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg
> @@ -25,6 +25,7 @@ define bsp-post-link
>   $(LD) -o $(basename $@)$(DOWNEXT) \
>   $ $(PROJECT_RELEASE)/lib/bootloader.o \
>   --just-symbols=$(basename $@)$(EXEEXT) \
> + --no-warn-mismatch \

... is this option poorly named because it is an error?

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems commit] bsp/motorola_powerpc: Fix for Binutils 2.28+

[Sebastian Huber]

- Am 2. Jun 2017 um 7:16 schrieb Chris Johns chr...@rtems.org:

> On 02/06/2017 15:11, Sebastian Huber wrote:
>> Module:rtems
>> Branch:master
>> Commit:7203b70be0266cdb4830537dfc8fd6189851708c
>> Changeset:
>> http://git.rtems.org/rtems/commit/?id=7203b70be0266cdb4830537dfc8fd6189851708c
>> 
>> Author:Sebastian Huber 
>> Date:  Thu Jun  1 19:04:05 2017 +0200
>> 
>> bsp/motorola_powerpc: Fix for Binutils 2.28+
>> 
>> There are mismatched sections in the bootloader input:
>> 
>> ld: Warning: ticker.exe uses hard float, ticker.ralf uses soft float
>> ld: ticker.exe: compiled normally and linked with modules compiled with
>> -mrelocatable
>> ld: failed to merge target specific data of file ticker.exe
>> 
>> Suppress this error explicitly.
> 
> Thank you for fixing this. A binutils observation ...
> 
> Yes an error cause the build fails so 
> 
>> 
>> ---
>> 
>>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg | 
>> 1 +
>>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mtx603e.cfg| 
>> 1 +
>>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mvme2100.cfg   | 
>> 1 +
>>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mvme2307.cfg   | 
>> 1 +
>>  .../lib/libbsp/powerpc/motorola_powerpc/make/custom/qemuprep-altivec.cfg | 
>> 1 +
>>  c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/qemuprep.cfg   | 
>> 1 +
>>  6 files changed, 6 insertions(+)
>> 
>> diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg
>> b/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg
>> index 98e8fd9..67d1766 100644
>> --- a/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg
>> +++ b/c/src/lib/libbsp/powerpc/motorola_powerpc/make/custom/mcp750.cfg
>> @@ -25,6 +25,7 @@ define bsp-post-link
>>  $(LD) -o $(basename $@)$(DOWNEXT) \
>>  $ $(PROJECT_RELEASE)/lib/bootloader.o \
>>  --just-symbols=$(basename $@)$(EXEEXT) \
>> +--no-warn-mismatch \
> 
> ... is this option poorly named because it is an error?

Yes, this is what surprised me a bit, that it is an actual error. I had to run 
the linker in GDB to figure out what is going on. I guess everything is all 
right now.

Maybe its worth to ask on the Binutils mailing list why the --no-warn-mismatch 
suppresses an error and update the documentation accordingly.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RFC: Any Outstanding Issues Before Branching 4.12?

[Chris Johns]

On 01/06/2017 16:43, Joel Sherrill wrote:
> Hi
> 
> Once the recent tool switch to gcc 7.1 has settled, I know of no major
> outstanding issues holding back branching 4.12.
> 
> If anyone has items they consider critical to resolve before branching or
> releasing 4.12.0, please speak up ASAP. Otherwise, we will be moving tickets 
> to
> either the next major release or a 4.12 dot release.
> 
> Thanks to everyone who has contributed to make this release series possible. 
> 

Please see my post on Users:

https://lists.rtems.org/pipermail/users/2017-June/031357.html

Thanks
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RFC: Any Outstanding Issues Before Branching 4.12?

[Joel Sherrill]

On Thursday, June 1, 2017, Chris Johns  wrote:

> On 01/06/2017 16:43, Joel Sherrill wrote:
> > Hi
> >
> > Once the recent tool switch to gcc 7.1 has settled, I know of no major
> > outstanding issues holding back branching 4.12.
> >
> > If anyone has items they consider critical to resolve before branching or
> > releasing 4.12.0, please speak up ASAP. Otherwise, we will be moving
> tickets to
> > either the next major release or a 4.12 dot release.
> >
> > Thanks to everyone who has contributed to make this release series
> possible.
> >
>
> Please see my post on Users:
>
> https://lists.rtems.org/pipermail/users/2017-June/031357.html
>
>
Thanks for the reminder Chris. We are close but there is some loose ends
and polishing to be done.

Help is definitely appreciated from the community. Any RTEMS user should be
able to help with the Getting Started guide review and update. Other issues
have fewer people who can help.


> Thanks
> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

RTEMS cfg of uncrustify

[Sichen Zhao]

Hi all,

The rtems cfg file of uncrustify: 
https://devel.rtems.org/wiki/Developer/Coding/Conventions#Tools
I feel weird about : there are always space after and before the parenthesis. 
It seems has conflict with Linux kernel tools checkpatch.pl rule 

Best Regards
Sichen Zhao
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RTEMS cfg of uncrustify

[Joel Sherrill]

On Thu, Jun 1, 2017 at 9:07 AM, Sichen Zhao  wrote:

> Hi all,
>
> The rtems cfg file of uncrustify: https://devel.rtems.org/wiki/
> Developer/Coding/Conventions#Tools
> I feel weird about : there are always space after and before the
> parenthesis. It seems has conflict with Linux kernel tools checkpatch.pl
> rule
>

Any overlap between the RTEMS and Linux coding standards is purely by
accident.

I would suggest that perhaps the checkpatch script from Linux be copied and
then
modified to match the RTEMS rules  :)


> Best Regards
> Sichen Zhao
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RTEMS cfg of uncrustify

[Gedare Bloom]

On Thu, Jun 1, 2017 at 11:09 AM, Joel Sherrill  wrote:
>
>
> On Thu, Jun 1, 2017 at 9:07 AM, Sichen Zhao  wrote:
>>
>> Hi all,
>>
>> The rtems cfg file of uncrustify:
>> https://devel.rtems.org/wiki/Developer/Coding/Conventions#Tools
>> I feel weird about : there are always space after and before the
>> parenthesis. It seems has conflict with Linux kernel tools checkpatch.pl
>> rule
>
>
> Any overlap between the RTEMS and Linux coding standards is purely by
> accident.
>
> I would suggest that perhaps the checkpatch script from Linux be copied and
> then
> modified to match the RTEMS rules  :)
>
This is on purpose. The RTEMS style is different than the Linux.
Please read https://devel.rtems.org/wiki/Developer/Coding/Conventions

>>
>> Best Regards
>> Sichen Zhao
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RTEMS cfg of uncrustify

[Sichen Zhao]

Ok, i see. Thank you.

Best Regards
Sichen Zhao


From: ged...@gwmail.gwu.edu  on behalf of Gedare Bloom 

Sent: Thursday, June 1, 2017 23:14
To: Joel Sherrill
Cc: Sichen Zhao; RTEMS
Subject: Re: RTEMS cfg of uncrustify

On Thu, Jun 1, 2017 at 11:09 AM, Joel Sherrill  wrote:
>
>
> On Thu, Jun 1, 2017 at 9:07 AM, Sichen Zhao  wrote:
>>
>> Hi all,
>>
>> The rtems cfg file of uncrustify:
>> https://devel.rtems.org/wiki/Developer/Coding/Conventions#Tools
>> I feel weird about : there are always space after and before the
>> parenthesis. It seems has conflict with Linux kernel tools checkpatch.pl
>> rule
>
>
> Any overlap between the RTEMS and Linux coding standards is purely by
> accident.
>
> I would suggest that perhaps the checkpatch script from Linux be copied and
> then
> modified to match the RTEMS rules  :)
>
This is on purpose. The RTEMS style is different than the Linux.
Please read https://devel.rtems.org/wiki/Developer/Coding/Conventions

>>
>> Best Regards
>> Sichen Zhao
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Building RISC-V BSP

[Denis Obrezkov]

Hello Hesham,

should I apply your patches? or should I paste all of them to
some directory (rsb has several 'patches' folders).

Also, could you describe our workflow? In the context of with what
repository
 I should work and where I should direct my pull requests.

2017-06-01 5:09 GMT+03:00 Hesham Almatary :

> Hi Denis,
>
> I submitted two patches for the tools, please use the latest only and
> rebuild the tools. This should avoid the newlib issues you had above
> as it uses main riscv patches.
>
> I'll look into the port this weekend and submit fixes unless you beat
> me to it. Meanwhile, you can submit error messages and I'll see if I
> can help.
>
> Keep the good work.
>
> Cheers,
> Hesham
>
> On Thu, Jun 1, 2017 at 12:04 AM, Denis Obrezkov 
> wrote:
> > 2017-05-31 16:39 GMT+03:00 Denis Obrezkov :
> >>
> >> Thanks, I downloaded it.
> >> There was a mistake also that _JBLEN wasn't defined in machine/setjmp.h
> >> I don't know the exact value, so I did the following:
> >> #ifdef __riscv
> >>
> >> /* TBD: not the exact number */
> >>
> >> #define _JBLEN 16
> >>
> >> #endif
> >>
> >> Now, it compiles further. But then I get the error:
> >> riscv32-rtems4.12-gcc --pipe -B../../../lib/
> -B../../../riscv_generic/lib/
> >> -specs bsp_specs -qrtems -DPACKAGE_NAME=\"rtems-c-src\"
> >> -DPACKAGE_TARNAME=\"rtems-c-src\" -DPACKAGE_VERSION=\"4.11.99.0\"
> >> -DPACKAGE_STRING=\"rtems-c-src\ 4.11.99.0\"
> >> -DPACKAGE_BUGREPORT=\"https://devel.rtems.org/newticket\";
> -DPACKAGE_URL=\"\"
> >> -I.
> >> -I/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip
> >> -isystem ../../../riscv_generic/lib/include   -O0 -g -Wall
> >> -Wmissing-prototypes -Wimplicit-function-declaration
> -Wstrict-prototypes
> >> -Wnested-externs -MT display/libdisplay_a-disp_hcms29xx.o -MD -MP -MF
> >> display/.deps/libdisplay_a-disp_hcms29xx.Tpo -c -o
> >> display/libdisplay_a-disp_hcms29xx.o `test -f
> 'display/disp_hcms29xx.c' ||
> >> echo
> >> '/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/'`display/disp_hcms29xx.c
> >> riscv32-rtems4.12-gcc: error: bsp_specs: No such file or directory
> >>
> >> So, I inserted it manually. But I can't figure out, why it wasn't copied
> >> automatically.
> >>
> >> Now I have an error:
> >> riscv32-rtems4.12-gcc --pipe -B../../../lib/
> -B../../../riscv_generic/lib/
> >> -specs bsp_specs -qrtems -DPACKAGE_NAME=\"rtems-c-src\"
> >> -DPACKAGE_TARNAME=\"rtems-c-src\" -DPACKAGE_VERSION=\"4.11.99.0\"
> >> -DPACKAGE_STRING=\"rtems-c-src\ 4.11.99.0\"
> >> -DPACKAGE_BUGREPORT=\"https://devel.rtems.org/newticket\";
> -DPACKAGE_URL=\"\"
> >> -I.
> >> -I/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip
> >> -isystem ../../../riscv_generic/lib/include   -O0 -g -Wall
> >> -Wmissing-prototypes -Wimplicit-function-declaration
> -Wstrict-prototypes
> >> -Wnested-externs -MT display/libdisplay_a-disp_hcms29xx.o -MD -MP -MF
> >> display/.deps/libdisplay_a-disp_hcms29xx.Tpo -c -o
> >> display/libdisplay_a-disp_hcms29xx.o `test -f
> 'display/disp_hcms29xx.c' ||
> >> echo
> >> '/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/'`display/disp_hcms29xx.c
> >>
> >> /home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/display/disp_hcms29xx.c:26:10:
> >> fatal error: bsp.h: No such file or directory
> >>  #include 
> >>
> >> It seems that configure scripts should be modified.
> >>
> >> 2017-05-31 8:46 GMT+03:00 Hesham Almatary :
> >>>
> >>> Hi Denis,
> >>>
> >>> Please use priv-1.10 branch. I rebased it (against master) and added
> >>> some fixes to make the build progress. Still, there's more work
> >>> needed. Your contributions are welcomed.
> >>>
> >>> Cheers,
> >>> Hesham
> >>> .
> >>>
> >>
> >>
> >> --
> >> Regards, Denis Obrezkov
> >
> > I think I worked it out. In a few days I will produce patches.
> > Now I am trying to compile .S files. Seems that some instructions are
> > missing.
> >
> >
> > --
> > Regards, Denis Obrezkov
>
>
>
> --
> Hesham
>



-- 
Regards, Denis Obrezkov
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel