Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161208011625.GL1555@brightrain.aerifal.cx>
Date: Wed, 7 Dec 2016 20:16:25 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: cortex-m support?

On Wed, Dec 07, 2016 at 06:55:56PM -0600, Rob Landley wrote:
> 
> On 12/07/2016 09:35 AM, Szabolcs Nagy wrote:
> > * Szabolcs Nagy <nsz@...t70.net> [2016-12-07 16:29:37 +0100]:
> >>
> >> fdpic arm is interesting too but it would be better
> >> if there was an abi spec (so there is no toolchain
> >> compatibility issue).
> >>
> > 
> > ok it seems somebody wrote this:
> > https://github.com/mickael-guene/fdpic_doc/blob/master/abi.txt
> > 
> > it's just not upstreamed anywhere (and not specified by the vendor)
> 
> Ah, that's one of the three authors of this:
> 
> http://www.slideshare.net/linaroorg/sfo15406-arm-fdpic-toolset-kernel-libraries-for-cortexm-cortexr-mmuless-cores
> 
> Although emcraft.com (the company whose full-time business has been
> "Linux on Cortex-M" for over 5 years) is in Moscow. Their fdpic support
> patch in their kernel is:
> 
> https://github.com/EmcraftSystems/linux-emcraft/commit/673205bf926b
> 
> And it looks like it was a port of the work of those guys.
> 
> Not sure where you get the relevant gcc patch...

I have links to the repos somewhere; the problem is that they're
forked from a fairly old gcc version (although not nearly as bad as
sh-fdpic; I think it's 4.8 or so) and the authors probably don't have
copyright assignments taken care of. It would be really nice if
someone could coordinate working with the authors and companies
involved and getting all of that taken care of -- preferably someone
getting paid to do so, since it's not particularly fun work to be
doing as a volunteer.

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.