All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: build arch memset/memcpy in Thumb2 mode
Date: Mon, 15 Dec 2014 15:24:22 +0100	[thread overview]
Message-ID: <548EEF16.1090707@suse.de> (raw)
In-Reply-To: <294bf2ac008a7d4ba98a19e28f3ae004@agner.ch>

Hi Stefan,

Am 03.12.2014 um 18:04 schrieb Stefan Agner:
> Can this be fixed by the merger or should I create a new revision?

It looks as if this was neither applied nor respun? I have some more
patches to make CONFIG_USE_PRIVATE_LIBGCC build for Thumb that I would
like to rebase on it.

In particular, I have pieced together a tiny asm/unified.h file with
THUMB() and ARM() macros and doing the .syntax unified in that central
place, and resyncing the various arch/arm/lib/_*.S files from Linux.
https://github.com/afaerber/u-boot/commits/stm32

Is there a particular reason you are doing the .syntax inline here?

And looking beyond this patch, assuming this is for your Vybrid's M4, do
you already have a concept for how to go about vectors.S, start.S and
the like for ARMv7-M? :) I've stubbed them out for now but haven't
managed to successfully link yet...

Regards,
Andreas

-- 
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer; HRB 21284 AG N?rnberg

  reply	other threads:[~2014-12-15 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 15:34 [U-Boot] [PATCH v2] arm: build arch memset/memcpy in Thumb2 mode Stefan Agner
2014-11-27 23:02 ` Stefan Agner
2014-11-30 19:33 ` Simon Glass
2014-11-30 20:07   ` Stefan Agner
2014-12-03 15:44 ` Bill Pringlemeir
2014-12-03 17:04   ` Stefan Agner
2014-12-15 14:24     ` Andreas Färber [this message]
2014-12-15 21:06       ` Stefan Agner
2014-12-18 15:39         ` Albert ARIBAUD

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=548EEF16.1090707@suse.de \
    --to=afaerber@suse.de \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.