From: David Howells <dhowells@redhat.com>
To: "Suzuki Takashi" <suzuki.takashi@gmail.com>
Cc: dhowells@redhat.com, torvalds@osdl.org,
akpm@linux-foundation.org, linux-am33-list@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-am33-list] [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #2]
Date: Tue, 30 Oct 2007 23:06:04 +0000 [thread overview]
Message-ID: <31286.1193785564@redhat.com> (raw)
In-Reply-To: <b1c6420f0710301459i147f0f00n1f7009139d3ac31a@mail.gmail.com>
Suzuki Takashi <suzuki.takashi@gmail.com> wrote:
> But is there any utility that depends on that uname says mn10300?
autoconf:-)
> I know existing developers should learn the arch name change.
> But how many developers?
I don't know. MEI probably does.
> That's the point. They must always be told or consult the documentations.
> Don't you think an arch name should be natural?
Can you guarantee there won't be any non-AM33 variants of mn10300 that need
supporting? An AM34, perhaps?
So basically, the toolchain name should change from am33 to mn10300 by your
argument.
> People need not to be told on other, at least major, archs.
There are plenty of other complications for other archs, such as 32-bit vs
64-bit, LE vs BE and other more subtle variants, so your argument isn't that
compelling.
> - growing new developers will have difficulties in understanding arch
> name difference,
You tell them, they then know. It doesn't take long. Standard practice, I
suspect, will involve giving them the toolchains and basic root filesystems.
The discrepancy has been around for years, and I suspect it's not going to
change now. If MEI ask, I will change it.
David
next prev parent reply other threads:[~2007-10-30 23:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 12:27 [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #2] David Howells
2007-10-29 12:28 ` [PATCH 1/2] MN10300: Suppress AOUT library support in ELF binfmt if !CONFIG_BINFMT_AOUT " David Howells
2007-10-30 12:57 ` [Linux-am33-list] [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel " Suzuki Takashi
2007-10-30 14:14 ` David Howells
2007-10-30 15:10 ` Suzuki Takashi
2007-10-30 16:53 ` David Howells
2007-10-30 17:47 ` DJ Delorie
2007-10-30 21:59 ` Suzuki Takashi
2007-10-30 23:06 ` David Howells [this message]
2007-10-31 10:50 ` Alan Cox
2007-11-02 15:19 ` Suzuki Takashi
[not found] ` <20071029122809.2846.58795.stgit@warthog.procyon.org.uk>
2007-10-30 14:40 ` [Linux-am33-list] [PATCH 2/2] MN10300: Add the MN10300/AM33 architecture to the " Suzuki Takashi
2007-10-30 20:04 ` David Howells
2007-10-31 0:03 ` Suzuki Takashi
2007-10-31 11:46 ` David Howells
2007-11-03 16:07 ` Suzuki Takashi
2007-11-05 15:38 ` David Howells
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=31286.1193785564@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suzuki.takashi@gmail.com \
--cc=torvalds@osdl.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