Re: [PATCH 3/6] shgen: Import from RTEMS

On Mon, Jun 11, 2018 at 5:35 AM, Chris Johns wrote: > On 11/6/18 5:49 pm, Sebastian Huber wrote: >> On 11/06/18 08:22, Joel Sherrill wrote: >>> >>> >>> > >>> > > >>> > >>> Does this tool need to move over? >>> > >> I would like to move all host tools out of the RTEMS >>

Re: [PATCH 3/6] shgen: Import from RTEMS

On 11/6/18 7:48 pm, Sebastian Huber wrote: > On 11/06/18 11:35, Chris Johns wrote: >>> 3. Remove the gensh1 and gensh2 BSPs. >>> >> What is in the generated file? >> >> We use weak symbols in the Zynq BSP to allow us to override defaults. Could >> this >> approach be used? > > The generated file

Re: [PATCH 3/6] shgen: Import from RTEMS

On 11/06/18 11:35, Chris Johns wrote: 3. Remove the gensh1 and gensh2 BSPs. What is in the generated file? We use weak symbols in the Zynq BSP to allow us to override defaults. Could this approach be used? The generated file provides a function _sci_get_brparms() and an array with generated

Re: [PATCH 3/6] shgen: Import from RTEMS

On 11/6/18 5:49 pm, Sebastian Huber wrote: > On 11/06/18 08:22, Joel Sherrill wrote: >> >> >>     > >>     >     > >>     >     >>> Does this tool need to move over? >>     >     >> I would like to move all host tools out of the RTEMS >>     repository >>     >     to simplify the >>     >     >> b

Re: [PATCH 3/6] shgen: Import from RTEMS

On 11/06/18 08:22, Joel Sherrill wrote: > >     > >     >>> Does this tool need to move over? >     >> I would like to move all host tools out of the RTEMS repository >     to simplify the >     >> build. If we get rid of the host tools, then we have only to >   

Re: [PATCH 3/6] shgen: Import from RTEMS

On Mon, Jun 11, 2018, 8:14 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 11/06/18 08:10, Joel Sherrill wrote: > > > > > > On Mon, Jun 11, 2018, 7:53 AM Sebastian Huber > > > > wrote: > > > > On 08/06/18 04:19, Chris Johns wrote

Re: [PATCH 3/6] shgen: Import from RTEMS

On 11/06/18 08:10, Joel Sherrill wrote: On Mon, Jun 11, 2018, 7:53 AM Sebastian Huber > wrote: On 08/06/18 04:19, Chris Johns wrote: > On 07/06/2018 16:11, Sebastian Huber wrote: >> On 07/06/18 07:53, Chris Johns wrote: >>> On 07/06/

Re: [PATCH 3/6] shgen: Import from RTEMS

On Mon, Jun 11, 2018, 7:53 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 08/06/18 04:19, Chris Johns wrote: > > On 07/06/2018 16:11, Sebastian Huber wrote: > >> On 07/06/18 07:53, Chris Johns wrote: > >>> On 07/06/2018 15:39, Sebastian Huber wrote: > Corresponding RTEMS

Re: [PATCH 3/6] shgen: Import from RTEMS

On 08/06/18 04:19, Chris Johns wrote: On 07/06/2018 16:11, Sebastian Huber wrote: On 07/06/18 07:53, Chris Johns wrote: On 07/06/2018 15:39, Sebastian Huber wrote: Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. Update #3443. ---   misc/shgen/AUTHORS |   3 +   misc/s

Re: [PATCH 3/6] shgen: Import from RTEMS

On 9/6/18 9:48 am, Joel Sherrill wrote: > On Fri, Jun 8, 2018 at 6:28 PM, Chris Johns > wrote: > > On 8/6/18 10:32 pm, Gedare Bloom wrote: > > On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns > wrote: > >> On 07/06/2018 16:11, Sebasti

Re: [PATCH 3/6] shgen: Import from RTEMS

On Fri, Jun 8, 2018 at 6:28 PM, Chris Johns wrote: > On 8/6/18 10:32 pm, Gedare Bloom wrote: > > On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns wrote: > >> On 07/06/2018 16:11, Sebastian Huber wrote: > >>> On 07/06/18 07:53, Chris Johns wrote: > On 07/06/2018 15:39, Sebastian Huber wrote: > >

Re: [PATCH 3/6] shgen: Import from RTEMS

On 8/6/18 10:32 pm, Gedare Bloom wrote: > On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns wrote: >> On 07/06/2018 16:11, Sebastian Huber wrote: >>> On 07/06/18 07:53, Chris Johns wrote: On 07/06/2018 15:39, Sebastian Huber wrote: > Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a

Re: [PATCH 3/6] shgen: Import from RTEMS

I had an email some time ago with the developer of the SuperH FPGA implementation (http://j-core.org/). Personally, I was close to putting it on the deprecate list about the time I read about that project. Seeing there would be an open implementation seemed a reason to give it a lease on life. I

Re: [PATCH 3/6] shgen: Import from RTEMS

On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns wrote: > On 07/06/2018 16:11, Sebastian Huber wrote: >> On 07/06/18 07:53, Chris Johns wrote: >>> On 07/06/2018 15:39, Sebastian Huber wrote: Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. Update #3443. --- >

Re: [PATCH 3/6] shgen: Import from RTEMS

On 07/06/2018 16:11, Sebastian Huber wrote: > On 07/06/18 07:53, Chris Johns wrote: >> On 07/06/2018 15:39, Sebastian Huber wrote: >>> Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. >>> >>> Update #3443. >>> --- >>>   misc/shgen/AUTHORS |   3 + >>>   misc/shgen/COPYING | 34

Re: [PATCH 3/6] shgen: Import from RTEMS

On 07/06/18 07:53, Chris Johns wrote: On 07/06/2018 15:39, Sebastian Huber wrote: Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. Update #3443. --- misc/shgen/AUTHORS | 3 + misc/shgen/COPYING | 340 + misc/shgen/

Re: [PATCH 3/6] shgen: Import from RTEMS

On 07/06/2018 15:39, Sebastian Huber wrote: > Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. > > Update #3443. > --- > misc/shgen/AUTHORS | 3 + > misc/shgen/COPYING | 340 > + > misc/shgen/TODO| 13 ++ > misc/sh

[PATCH 3/6] shgen: Import from RTEMS

Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. Update #3443. --- misc/shgen/AUTHORS | 3 + misc/shgen/COPYING | 340 + misc/shgen/TODO| 13 ++ misc/shgen/sci.c | 177 misc/shgen/sci.