From: Shinya Kuribayashi <skuribay@pobox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/6] Mips: Move content of arch/mips/cpu to arch/mips/cpu/mips32
Date: Sat, 12 Mar 2011 23:43:18 +0900 [thread overview]
Message-ID: <4D7B8686.9060101@pobox.com> (raw)
In-Reply-To: <1299676619-7963-2-git-send-email-daniel.schwierzeck@googlemail.com>
On 3/9/11 10:16 PM, daniel.schwierzeck at googlemail.com wrote:
> All current CPUs and SoCs are based on Mips32 arch. The complete
Is that true? What about purple SoC? IIUC It's based on MIPS 5Kc
and capable of 64-bit, which MIPS32 is 32-bit only architecture.
> code resides in the global arch/mips/cpu directory. This is not
> suitable if other Mips architectures like Mips64 or Octeon should
> be supported in the future.
Just for the record.
Personally, Octeon is sort of a special case. It's based on MIPS64
architecture, and definitely a MIPS SoC, but not usual MIPS machine.
As Aaron already mentioned before, we have very few files sharable
with other MIPS machines even in the Linux kernel case. I think it
will take long time the Octeon port gets merged to upstream, regard-
less of my opinions, because they have a lot of things need to be
resolved prior to Octeon itself.
> To achieve this the current CPU code is moved to its own mips32
> subdirectory. All Mips32 boards have to use mips32 as config switch
> in board.cfg.
>
> Signed-off-by: Daniel Schwierzeck<daniel.schwierzeck@googlemail.com>
> Cc: Shinya Kuribayashi<skuribay@pobox.com>
next prev parent reply other threads:[~2011-03-12 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 13:16 [U-Boot] [RFC PATCH 0/6] Mips: Refactoring of CPU and SoC code daniel.schwierzeck at googlemail.com
2011-03-09 13:16 ` [U-Boot] [RFC PATCH 1/6] Mips: Move content of arch/mips/cpu to arch/mips/cpu/mips32 daniel.schwierzeck at googlemail.com
2011-03-12 14:43 ` Shinya Kuribayashi [this message]
2011-03-13 0:48 ` Daniel Schwierzeck
2011-03-13 22:44 ` Wolfgang Denk
2011-03-14 12:15 ` Daniel Schwierzeck
2011-03-14 12:41 ` Wolfgang Denk
2011-03-15 0:29 ` Aaron Williams
2011-03-09 13:16 ` [U-Boot] [RFC PATCH 2/6] Mips: Purple: Adapt u-boot.lds to changed CPU directory layout daniel.schwierzeck at googlemail.com
2011-03-12 14:27 ` Shinya Kuribayashi
2011-03-09 13:16 ` [U-Boot] [RFC PATCH 3/6] Mips: IncaIP: Move all IncaIP specific code to separate subdirectory daniel.schwierzeck at googlemail.com
2011-03-09 13:16 ` [U-Boot] [RFC PATCH 4/6] Mips: Purple: Move all Purple " daniel.schwierzeck at googlemail.com
2011-03-09 13:16 ` [U-Boot] [RFC PATCH 5/6] Mips: Au1x00: Move all Au1x00 " daniel.schwierzeck at googlemail.com
2011-03-09 13:16 ` [U-Boot] [RFC PATCH 6/6] Mips: Update setting of endianess and CPU optimization flags daniel.schwierzeck at googlemail.com
2011-03-12 14:58 ` [U-Boot] [RFC PATCH 0/6] Mips: Refactoring of CPU and SoC code Shinya Kuribayashi
2011-03-12 15:00 ` Shinya Kuribayashi
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=4D7B8686.9060101@pobox.com \
--to=skuribay@pobox.com \
--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.