Re: [PATCH] bsps: Move umon header files

2019-03-07 Thread Joel Sherrill
Yes. uMon supports at least m68k and ARM in addition to MIPS. So the question is does a file go in bsps/shared based on potential designed use or actual current use in the tree? --joel On Thu, Mar 7, 2019 at 8:23 AM Gedare Bloom wrote: > There was some effort expended to get it working with Be

Re: [PATCH] bsps: Move umon header files

2019-03-07 Thread Gedare Bloom
There was some effort expended to get it working with Beaglebone: https://devel.rtems.org/wiki/GSoC/2015/BeagleBSPPortingUmon I don't know if this ever made it to primetime. We also set up some RTEMS Project repos and mailing lists to support umon, since it lacks its own community. https://git.rte

Re: [PATCH] bsps: Move umon header files

2019-03-07 Thread Sebastian Huber
On 07/03/2019 13:49, Joel Sherrill wrote: Umon if not MIPS specific even if that is the only bsp we have using it So, this code is intended to be used by several BSPs? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax

Re: [PATCH] bsps: Move umon header files

2019-03-07 Thread Joel Sherrill
Umon if not MIPS specific even if that is the only bsp we have using it On Thu, Mar 7, 2019, 2:46 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > They are only used by the csb337 BSP. > --- > bsps/{ => arm/csb337}/include/rtems/umon.h | 0 > bsps/{ => arm/csb337}/include/umon