linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	linux-arch@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [RFC PATCH 0/9] Thumb-2 ISA kernel port
Date: Thu, 7 Jun 2007 22:05:12 +0100	[thread overview]
Message-ID: <20070607210512.GA13729@linux-mips.org> (raw)
In-Reply-To: <20070606182914.GB6303@uranus.ravnborg.org>

On Wed, Jun 06, 2007 at 08:29:14PM +0200, Sam Ravnborg wrote:

> > Because of the issues listed below, merging the Thumb-2 support into
> > the existing arch/arm files would clutter the existing code with
> > macros like ARM, THUMB or W (for conditional compilation and the wide
> > instruction format). The IT instruction is also not recognised by
> > older toolchains and additional (assembler) macros would be needed,
> > including support for the inline assembly. I therefore decided to
> > create a separate arch/arm_t2 directory that shares a lot of code with
> > the existing arch/arm.
> 
> Hi Catalin.
> Can you please share with us the strong arguments why another (third)
> arm architecture are needed?

It's been my experience with 64-bit MIPS that starting off with a 2nd
arch then eventually factoring out the differences and unifying things
back into a single mips architecture was actually the easier road to go.

Downside: this approach takes long term careful coding.  It is hell with
the kind of "code once and resuse never" style that's only too common in
the embedded industry.

  Ralf

      parent reply	other threads:[~2007-06-08 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070606172409.6689.26641.stgit@localhost.localdomain>
2007-06-06 18:29 ` [RFC PATCH 0/9] Thumb-2 ISA kernel port Sam Ravnborg
2007-06-06 20:47   ` Russell King - ARM Linux
2007-06-06 21:10     ` Sam Ravnborg
2007-06-06 21:19       ` Catalin Marinas
2007-06-06 22:04         ` Russell King - ARM Linux
2007-06-06 22:01       ` Russell King - ARM Linux
2007-06-06 22:02   ` Catalin Marinas
2007-06-07 21:05   ` Ralf Baechle [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=20070607210512.GA13729@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=sam@ravnborg.org \
    /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;
as well as URLs for NNTP newsgroup(s).