mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Martin Hofmann <martin.hofmann@mni.thm.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1 1/1] Add generic implementation for muldi3
Date: Mon, 7 Jan 2019 09:16:21 +0100	[thread overview]
Message-ID: <d53efd8a-73d0-78d6-5583-215692c4ce21@mni.thm.de> (raw)
In-Reply-To: <20190107074459.idj6n577mw6iwyez@pengutronix.de>

Hi Sascha

On 1/7/19 8:44 AM, Sascha Hauer wrote:
> Hi Martin,
> 
> On Sat, Jan 05, 2019 at 07:45:12PM +0100, Martin Hofmann wrote:
>> Since version v2018.08.0 some shared copies of gcc routines got added to
>> barebox so that archs don't need to have thier own copy inside thier
>> lib. The arch I am working on atm also needs support for muldi3 which is
>> not present as a generic version right now.
>>
>> This patch addes the generic version form latest linux v4.20 to barebox
>> and lets the archs select it in thier Kconfig so they don't need to
>> provide it themself.
> 
> Applied, thanks
> 
> Which architecture is it you are working on?
> 
> Sascha
>

It is called eco32 and is a fairly simple RISC CPU made for educational
purpose designed by a lecturer of the Univerity Of Applied Science
Mittelhessen in germany. It is used for courses like operating systems
and compiler construction.

If you are interssted in it the port is available on my github:
https://github.com/mh0fmann/eco32-barebox

Martin

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2019-01-07  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 18:45 Martin Hofmann
2019-01-07  7:44 ` Sascha Hauer
2019-01-07  8:16   ` Martin Hofmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d53efd8a-73d0-78d6-5583-215692c4ce21@mni.thm.de \
    --to=martin.hofmann@mni.thm.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox