[PATCH] bsps: Move umon header files
Joel Sherrill
joel at rtems.org
Thu Mar 7 16:45:56 UTC 2019
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 <gedare at rtems.org> wrote:
> 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.rtems.org/umon/
>
> Gedare
>
> On Thu, Mar 7, 2019 at 7:53 AM Sebastian Huber <
> sebastian.huber at embedded-brains.de> wrote:
>
>> 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 : +49 89 189 47 41-09
>> E-Mail : sebastian.huber at embedded-brains.de
>> PGP : Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190307/1ece149e/attachment-0002.html>
More information about the devel
mailing list