<offlist> Re: ANN: microblaze-rtems4.11 toolchain

[Gedare Bloom]

Hello Thomas (and Ralf):

I have had time to think on it (and sleep on it) and am not pleased
with how I responded initially.  It is obvious to me now that having
the tools graciously provided by Ralf for a port is vastly superior to
not having them :)

-Gedare

On Fri, Apr 20, 2012 at 2:28 AM, Thomas Doerfler
<Thomas.Doerfler at embedded-brains.de> wrote:
> Gedare,
>
> here I disagree with you. Setting up a proper toolchain for a new target
> is non-trivial and Ralf definitively knows best how to do this. If
> MicroBlaze _might_ get support, havng a proper toolchain ready is a benefit.
>
> If somebody is interested to porting RTEMS to microblaze, this is one
> step further to the goal.
>
> Having a toolchain ready doesn't mean the whole port is done. And
> developers should know the difference.
>
> wkr,
>
> Thomas.
>
> Am 19.04.2012 17:30, schrieb Gedare Bloom:
>> I disagree with pushing out toolchains for unsupported/uncommitted
>> architectures. It sends the message that we will provide/have support
>> for targets that we do not. I should think that anyone working on a
>> port they ought to be able to manage their own toolchains until they
>> release it publicly.
>>
>> -Gedare
>>
>> On Thu, Apr 19, 2012 at 9:29 AM, Ralf Corsepius
>> <ralf.corsepius at rtems.org> wrote:
>>> Hi,
>>>
>>> By public demand, I have added a microblaze-rtems4.11 to the toolchains I am
>>> building for RTEMS.
>>>
>>> The corresponding patches are integrated into the latest rtems-4.11
>>> toolchain patches, which can either be found in
>>> rtems-4.11-branch in git://git.rtems.org/data/git/cross-rpms.git
>>> or in
>>> ftp://ftp.rtems.org/pub/rtems/SOURCES/4.11
>>>
>>> For now, this toolchain is just a "first, experimental stab", which "just
>>> builds", but has not seen any actual testing yet and is meant to be
>>> convenience to prospective users.
>>>
>>> Any feedback welcome.
>>>
>>> Ralf
>>>
>>> P.S.: I don't mean to threaten anybody, but as I don't have any use for this
>>> target myself, I would not have many problems in removing this toolchain
>>> again, shouldn't we see an RTEMS microblaze port inside of the sourcetree in
>>> "not too distant future" ;)
>>> _______________________________________________
>>> rtems-users mailing list
>>> rtems-users at rtems.org
>>> http://www.rtems.org/mailman/listinfo/rtems-users
>> _______________________________________________
>> rtems-devel mailing list
>> rtems-devel at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-devel
>
>
> --
> --------------------------------------------
> Embedded Brains GmbH
> Thomas Doerfler           Obere Lagerstr. 30
> D-82178 Puchheim          Germany
> email: Thomas.Doerfler at embedded-brains.de
> Phone: +49-89-18908079-2
> Fax:   +49-89-18908079-9
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel