Re: [PATCH 1/1] Refactor class and main module per comments

2018-08-03 Thread Gedare Bloom
Hi Dannie,

Please send this as a squashed patch showing only your original
changes now, and provide with -v2
https://devel.rtems.org/wiki/Developer/Git/Users#CreatingaPatch

At this point we will need to see what Chris thinks about the Python.
I think it looks much better now.

Gedare

On Thu, Aug 2, 2018 at 10:48 PM, Dannie Huang  wrote:
> Address multiple comments:
>
> 1. Refactored makedoc2rst class.
> 2. Refactored main module
> 3. Removed strcmp.rst
>
> On Thu, Aug 2, 2018 at 9:44 PM, Dannie Huang  wrote:
>>
>> ---
>>  README.md|  4 +-
>>  gen_rst_from_makedoc.py  | 31 +--
>>  makedoc2rst.py   | 99
>> 
>>  makedoc2rst_converter.py | 85 -
>>  strcmp.rst   | 47 ---
>>  5 files changed, 110 insertions(+), 156 deletions(-)
>>  create mode 100644 makedoc2rst.py
>>  delete mode 100644 makedoc2rst_converter.py
>>  delete mode 100644 strcmp.rst
>>
>> diff --git a/README.md b/README.md
>> index 8ebb224..64a3ba9 100644
>> --- a/README.md
>> +++ b/README.md
>> @@ -1,2 +1,2 @@
>> -# NewlibMarkup2SphinxConvertorPrivate
>> -(PRIVATE) This repo contains code for
>> NewlibMarkup2SphinxConvertorPrivate.
>> +# NewlibMarkup2SphinxConverter
>> +This repo contains code for NewlibMarkup2SphinxConverter
>> diff --git a/gen_rst_from_makedoc.py b/gen_rst_from_makedoc.py
>> index 4100756..8e4d9b0 100755
>> --- a/gen_rst_from_makedoc.py
>> +++ b/gen_rst_from_makedoc.py
>> @@ -30,7 +30,7 @@
>>  #
>>
>>  import argparse
>> -import makedoc2rst_converter
>> +import makedoc2rst
>>
>>
>>  def get_parser():
>> @@ -38,37 +38,24 @@ def get_parser():
>>  description='Convert newlib style markup to rst markup'
>>  )
>>  parser.add_argument(
>> -'-s',
>> -'--source_file_path',
>> +'-c',
>> +'--c_file_path',
>>  type=str,
>> -help='Path of source file with newlib style comments',
>> +help='Path of c source file with newlib style comments',
>>  )
>>  parser.add_argument(
>> -'-d',
>> -'--dest_file_path',
>> +'-r',
>> +'--rst_file_path',
>>  type=str,
>>  help='Path of destination file with rst markup',
>>  )
>>  return parser
>>
>>
>> -def main(source_file_dir, dest_file_dir):
>> -with open(source_file_dir, 'r') as source_file, open(dest_file_dir,
>> 'w') as dest_file:
>> -file_content = source_file.read()
>> -
>> -makedoc2rst = makedoc2rst_converter.makedoc2rst_converter()
>> -# Get comments inside of /* */
>> -comments = makedoc2rst.extract_comments(file_content)
>> -
>> -# Parse comments
>> -command_text_dict =
>> makedoc2rst.extract_command_and_text(comments)
>> -
>> -# Process text based on command type
>> -rst_str = makedoc2rst.generate_rst(command_text_dict)
>> -
>> -dest_file.write(rst_str)
>> +def main(c_file, rst_file):
>> +makedoc2rst.makedoc2rst(c_file, rst_file).convert()
>>
>>
>>  if __name__ == '__main__':
>>  args = get_parser().parse_args()
>> -main(args.source_file_path, args.dest_file_path)
>> +main(args.c_file_path, args.rst_file_path)
>> diff --git a/makedoc2rst.py b/makedoc2rst.py
>> new file mode 100644
>> index 000..d887323
>> --- /dev/null
>> +++ b/makedoc2rst.py
>> @@ -0,0 +1,99 @@
>> +#!/usr/bin/env python
>> +#
>> +# RTEMS Tools Project (http://www.rtems.org/)
>> +# Copyright 2018 Danxue Huang (danxue.hu...@gmail.com)
>> +# 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 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 COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 

Re: [PATCH v2] c-user: Update partition create documentation

2018-08-03 Thread Gedare Bloom
Thanks

On Fri, Aug 3, 2018 at 1:57 AM, Sebastian Huber
 wrote:
> Add an example.
>
> Close #3482.
> ---
>  c-user/partition_manager.rst | 65 
> 
>  1 file changed, 54 insertions(+), 11 deletions(-)
>
> diff --git a/c-user/partition_manager.rst b/c-user/partition_manager.rst
> index 68761da..010f63a 100644
> --- a/c-user/partition_manager.rst
> +++ b/c-user/partition_manager.rst
> @@ -162,21 +162,23 @@ DIRECTIVE STATUS CODES:
>   * - ``RTEMS_SUCCESSFUL``
> - partition created successfully
>   * - ``RTEMS_INVALID_NAME``
> -   - invalid partition name
> +   - invalid partition ``name``
>   * - ``RTEMS_TOO_MANY``
> - too many partitions created
>   * - ``RTEMS_INVALID_ADDRESS``
> -   - address not on four byte boundary
> +   - ``starting_address`` is not on a pointer size boundary
>   * - ``RTEMS_INVALID_ADDRESS``
> - ``starting_address`` is NULL
>   * - ``RTEMS_INVALID_ADDRESS``
> - ``id`` is NULL
>   * - ``RTEMS_INVALID_SIZE``
> -   - length or buffer size is 0
> +   - ``length`` or ``buffer_size`` is 0
>   * - ``RTEMS_INVALID_SIZE``
> -   - length is less than the buffer size
> +   - ``length`` is less than the ``buffer_size``
>   * - ``RTEMS_INVALID_SIZE``
> -   - buffer size not a multiple of 4
> +   - ``buffer_size`` is not an integral multiple of the pointer size
> + * - ``RTEMS_INVALID_SIZE``
> +   - ``buffer_size`` is less than two times the pointer size
>   * - ``RTEMS_MP_NOT_CONFIGURED``
> - multiprocessing not configured
>   * - ``RTEMS_TOO_MANY``
> @@ -194,13 +196,18 @@ DESCRIPTION:
>  NOTES:
>  This directive will not cause the calling task to be preempted.
>
> -The ``starting_address`` must be properly aligned for the target
> -architecture.
> +The partition buffer area specified by the ``starting_address`` must be
> +properly aligned.  It must be possible to directly store target
> +architecture pointers and the also the user data.  For example, if the 
> user
> +data contains some long double or vector data types, the partition buffer
> +area and the buffer size must take the alignment of these types into
> +account which is usually larger than the pointer alignment.  A cache line
> +alignment may be also a factor.
>
> -The ``buffer_size`` parameter must be a multiple of the CPU alignment
> -factor.  Additionally, ``buffer_size`` must be large enough to hold two
> -pointers on the target architecture.  This is required for RTEMS to 
> manage
> -the buffers when they are free.
> +The ``buffer_size`` parameter must be an integral multiple of the pointer
> +size on the target architecture.  Additionally, ``buffer_size`` must be
> +large enough to hold two pointers on the target architecture.  This is
> +required for RTEMS to manage the buffers when they are free.
>
>  Memory from the partition is not used by RTEMS to store the Partition
>  Control Block.
> @@ -226,6 +233,42 @@ NOTES:
>  The total number of global objects, including partitions, is limited by 
> the
>  maximum_global_objects field in the Configuration Table.
>
> +EXAMPLE:
> +.. code-block:: c
> +
> +#include 
> +#include 
> +
> +#include 
> +
> +typedef struct {
> +  char less;
> +  short more;
> +} item;
> +
> +union {
> +  item data;
> +  rtems_chain_node node;
> +} items[ 13 ];
> +
> +rtems_id create_partition(void)
> +{
> +  rtems_id  id;
> +  rtems_status_code sc;
> +
> +  sc = rtems_partition_create(
> +rtems_build_name( 'P', 'A', 'R', 'T' ),
> +items,
> +sizeof( items ),
> +sizeof( items[ 0 ] ),
> +RTEMS_DEFAULT_ATTRIBUTES,
> +&id
> +  );
> +  assert(sc == RTEMS_SUCCESSFUL);
> +
> +  return id;
> +}
> +
>  .. raw:: latex
>
> \clearpage
> --
> 2.13.7
>
> ___
> 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


SPARC BSP Build Failures

2018-08-03 Thread Joel Sherrill
Hi

I have done two recent sweeps with rtems-bsp-builder and a number of odd
SPARC BSP build failures occur. I haven't been able to reproduce them with
by-hand builds.

https://lists.rtems.org/pipermail/build/2018-August/000903.html


This is the relevant part of the summary. Anyone got any ideas? These are
not good BSPs to have build problems with. :(

   8 smp sparc/gr712rc build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
  --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

   9 smp-debug sparc/gr712rc build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
  --enable-rtems-debug --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  10 smp-network sparc/gr712rc build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
  --enable-networking --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  11 smp-network-debug sparc/gr712rc build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
  --enable-rtems-debug --enable-networking --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  12 smp sparc/gr740 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
  --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  13 smp-debug sparc/gr740 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
  --enable-rtems-debug --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  14 smp-network sparc/gr740 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
  --enable-networking --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  15 smp-network-debug sparc/gr740 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
  --enable-rtems-debug --enable-networking --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  16 smp sparc/leon3 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
  --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  17 smp-debug sparc/leon3 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
  --enable-rtems-debug --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  18 smp-network sparc/leon3 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
  --enable-networking --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  19 smp-network-debug sparc/leon3 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
  --enable-rtems-debug --enable-networking --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  20 smp sparc/ut699 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=ut699 --prefix=/home/joel/rtems-work/bsps\
  --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  21 smp-debug sparc/ut699 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=ut699 --prefix=/home/joel/rtems-work/bsps\
  --enable-rtems-debug --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  22 smp-network sparc/ut699 build:
  configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
  rtems5 --enable-rtemsbsp=ut699 --prefix=/home/joel/rtems-work/bsps\
  --enable-networking --enable-smp
 error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
`mv'

  23 smp-net

Re: SPARC BSP Build Failures

2018-08-03 Thread Sebastian Huber
Please use the latest master.

- Joel Sherrill  schrieb:
> Hi
> 
> I have done two recent sweeps with rtems-bsp-builder and a number of odd
> SPARC BSP build failures occur. I haven't been able to reproduce them with
> by-hand builds.
> 
> https://lists.rtems.org/pipermail/build/2018-August/000903.html
> 
> 
> This is the relevant part of the summary. Anyone got any ideas? These are
> not good BSPs to have build problems with. :(
> 
>8 smp sparc/gr712rc build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
>   --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>9 smp-debug sparc/gr712rc build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
>   --enable-rtems-debug --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   10 smp-network sparc/gr712rc build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
>   --enable-networking --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   11 smp-network-debug sparc/gr712rc build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-work/bsps\
>   --enable-rtems-debug --enable-networking --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   12 smp sparc/gr740 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
>   --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   13 smp-debug sparc/gr740 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
>   --enable-rtems-debug --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   14 smp-network sparc/gr740 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
>   --enable-networking --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   15 smp-network-debug sparc/gr740 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-work/bsps\
>   --enable-rtems-debug --enable-networking --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   16 smp sparc/leon3 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
>   --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   17 smp-debug sparc/leon3 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
>   --enable-rtems-debug --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   18 smp-network sparc/leon3 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
>   --enable-networking --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   19 smp-network-debug sparc/leon3 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-work/bsps\
>   --enable-rtems-debug --enable-networking --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   20 smp sparc/ut699 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=ut699 --prefix=/home/joel/rtems-work/bsps\
>   --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   21 smp-debug sparc/ut699 build:
>   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
>   rtems5 --enable-rtemsbsp=ut699 --prefix=/home/joel/rtems-work/bsps\
>   --enable-rtems-debug --enable-smp
>  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> `mv'
> 
>   22 smp-network sparc/ut699 build:
>  

Re: SPARC BSP Build Failures

2018-08-03 Thread Joel Sherrill
OK. Weird that I couldn't reproduce this by hand though.

Need to build new tools so this may take a while.

--joel

On Fri, Aug 3, 2018 at 9:41 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> Please use the latest master.
>
> - Joel Sherrill  schrieb:
> > Hi
> >
> > I have done two recent sweeps with rtems-bsp-builder and a number of odd
> > SPARC BSP build failures occur. I haven't been able to reproduce them
> with
> > by-hand builds.
> >
> > https://lists.rtems.org/pipermail/build/2018-August/000903.html
> >
> >
> > This is the relevant part of the summary. Anyone got any ideas? These are
> > not good BSPs to have build problems with. :(
> >
> >8 smp sparc/gr712rc build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >9 smp-debug sparc/gr712rc build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-rtems-debug --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   10 smp-network sparc/gr712rc build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-networking --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   11 smp-network-debug sparc/gr712rc build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr712rc --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-rtems-debug --enable-networking --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   12 smp sparc/gr740 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   13 smp-debug sparc/gr740 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-rtems-debug --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   14 smp-network sparc/gr740 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-networking --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   15 smp-network-debug sparc/gr740 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=gr740 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-rtems-debug --enable-networking --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   16 smp sparc/leon3 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   17 smp-debug sparc/leon3 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-rtems-debug --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   18 smp-network sparc/leon3 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-networking --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   19 smp-network-debug sparc/leon3 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=leon3 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-rtems-debug --enable-networking --enable-smp
> >  error: bsps/sparc/shared/start/start.S:313 Error: Unknown opcode:
> > `mv'
> >
> >   20 smp sparc/ut699 build:
> >   configure: /home/joel/rtems-work/rtems/configure --target=sparc-\
> >   rtems5 --enable-rtemsbsp=ut699 --prefix=/home/joel/rtems-
> work/bsps\
> >   --enable-smp
> >  error: bsp

Version of FreeBSD for libbsd

2018-08-03 Thread Joel Sherrill
Hi

libbsd.txt says this is based on FreeBSD 9.2 but I thought it
had been updated past that.

Also how could I have figured this out otherwise?

If it matters, there are also man pages references to FreeBSD 9.2.

And is the Changes up to date? It has a date of 2017?

Thanks.


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

Re: Fwd: [PATCH] libgloss support for nios2 QEMU

2018-08-03 Thread Joel Sherrill
On Fri, Aug 3, 2018 at 1:52 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 03/08/18 00:10, Joel Sherrill wrote:
>
>> This looks like a solution for having a way to test the Nios II.
>>
>
> There is support for Nios II in upstream Qemu since 2017.


Yeah but it is easy to cobble a BSP together from libgloss code and Sandra
just posted that.

--joel


>
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germa
> 
> ny
> Phone   : +49 89 189 47 41-16
> Fax : +49 89 189 47 41-09
> E-Mail  : sebastian.hu...@embedded-brains.de
> PGP : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH v2] Initial implemantation

2018-08-03 Thread Dannie Huang
From: Danxue Huang <36866155+dh0...@users.noreply.github.com>

---
 .gitignore  |   3 ++
 README.md   |   2 +
 gen_rst_from_makedoc.py |  61 
 makedoc2rst.py  |  99 +
 rst.py  | 104 
 5 files changed, 269 insertions(+)
 create mode 100644 .gitignore
 create mode 100644 README.md
 create mode 100755 gen_rst_from_makedoc.py
 create mode 100644 makedoc2rst.py
 create mode 100644 rst.py

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..f707fbd
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,3 @@
+.idea/*
+__pycache__/*
+*.rst
diff --git a/README.md b/README.md
new file mode 100644
index 000..64a3ba9
--- /dev/null
+++ b/README.md
@@ -0,0 +1,2 @@
+# NewlibMarkup2SphinxConverter
+This repo contains code for NewlibMarkup2SphinxConverter
diff --git a/gen_rst_from_makedoc.py b/gen_rst_from_makedoc.py
new file mode 100755
index 000..8e4d9b0
--- /dev/null
+++ b/gen_rst_from_makedoc.py
@@ -0,0 +1,61 @@
+#!/usr/bin/env python
+#
+# RTEMS Tools Project (http://www.rtems.org/)
+# Copyright 2018 Danxue Huang (danxue.hu...@gmail.com)
+# 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 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 COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
+#
+
+import argparse
+import makedoc2rst
+
+
+def get_parser():
+parser = argparse.ArgumentParser(
+description='Convert newlib style markup to rst markup'
+)
+parser.add_argument(
+'-c',
+'--c_file_path',
+type=str,
+help='Path of c source file with newlib style comments',
+)
+parser.add_argument(
+'-r',
+'--rst_file_path',
+type=str,
+help='Path of destination file with rst markup',
+)
+return parser
+
+
+def main(c_file, rst_file):
+makedoc2rst.makedoc2rst(c_file, rst_file).convert()
+
+
+if __name__ == '__main__':
+args = get_parser().parse_args()
+main(args.c_file_path, args.rst_file_path)
diff --git a/makedoc2rst.py b/makedoc2rst.py
new file mode 100644
index 000..d887323
--- /dev/null
+++ b/makedoc2rst.py
@@ -0,0 +1,99 @@
+#!/usr/bin/env python
+#
+# RTEMS Tools Project (http://www.rtems.org/)
+# Copyright 2018 Danxue Huang (danxue.hu...@gmail.com)
+# 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 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 COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
+#
+

Re: [PATCH v2] Initial implemantation

2018-08-03 Thread Dannie Huang
Hi Chris and Dr. Joel,

Here is the latest version based on various comments, what do think about
it? Is there anything else you want to add or change?

Best,
Dannie

On Fri, Aug 3, 2018 at 10:19 PM, Dannie Huang 
wrote:

> From: Danxue Huang <36866155+dh0...@users.noreply.github.com>
>
> ---
>  .gitignore  |   3 ++
>  README.md   |   2 +
>  gen_rst_from_makedoc.py |  61 
>  makedoc2rst.py  |  99 ++
> +++
>  rst.py  | 104 ++
> ++
>  5 files changed, 269 insertions(+)
>  create mode 100644 .gitignore
>  create mode 100644 README.md
>  create mode 100755 gen_rst_from_makedoc.py
>  create mode 100644 makedoc2rst.py
>  create mode 100644 rst.py
>
> diff --git a/.gitignore b/.gitignore
> new file mode 100644
> index 000..f707fbd
> --- /dev/null
> +++ b/.gitignore
> @@ -0,0 +1,3 @@
> +.idea/*
> +__pycache__/*
> +*.rst
> diff --git a/README.md b/README.md
> new file mode 100644
> index 000..64a3ba9
> --- /dev/null
> +++ b/README.md
> @@ -0,0 +1,2 @@
> +# NewlibMarkup2SphinxConverter
> +This repo contains code for NewlibMarkup2SphinxConverter
> diff --git a/gen_rst_from_makedoc.py b/gen_rst_from_makedoc.py
> new file mode 100755
> index 000..8e4d9b0
> --- /dev/null
> +++ b/gen_rst_from_makedoc.py
> @@ -0,0 +1,61 @@
> +#!/usr/bin/env python
> +#
> +# RTEMS Tools Project (http://www.rtems.org/)
> +# Copyright 2018 Danxue Huang (danxue.hu...@gmail.com)
> +# 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 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 COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
> +#
> +
> +import argparse
> +import makedoc2rst
> +
> +
> +def get_parser():
> +parser = argparse.ArgumentParser(
> +description='Convert newlib style markup to rst markup'
> +)
> +parser.add_argument(
> +'-c',
> +'--c_file_path',
> +type=str,
> +help='Path of c source file with newlib style comments',
> +)
> +parser.add_argument(
> +'-r',
> +'--rst_file_path',
> +type=str,
> +help='Path of destination file with rst markup',
> +)
> +return parser
> +
> +
> +def main(c_file, rst_file):
> +makedoc2rst.makedoc2rst(c_file, rst_file).convert()
> +
> +
> +if __name__ == '__main__':
> +args = get_parser().parse_args()
> +main(args.c_file_path, args.rst_file_path)
> diff --git a/makedoc2rst.py b/makedoc2rst.py
> new file mode 100644
> index 000..d887323
> --- /dev/null
> +++ b/makedoc2rst.py
> @@ -0,0 +1,99 @@
> +#!/usr/bin/env python
> +#
> +# RTEMS Tools Project (http://www.rtems.org/)
> +# Copyright 2018 Danxue Huang (danxue.hu...@gmail.com)
> +# 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 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 COPYRIGHT HOLDERS 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 COPYRI