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 2/2] MN10300: Add the MN10300/AM33 architecture to the kernel [try #2]
Date: Mon, 05 Nov 2007 15:38:05 +0000 [thread overview]
Message-ID: <15038.1194277085@redhat.com> (raw)
In-Reply-To: <b1c6420f0711030907g10149e1asda1afe4e2f3c8e02@mail.gmail.com>
Suzuki Takashi <suzuki.takashi@gmail.com> wrote:
> I'm very annoyed and a bit surprised to hear they admitted such a big
> change so easily.
Why be annoyed? It's not actually a substantial change.
> You and I know there are consumer devices already out running the am33
> port of the kernel.
Yes, and have been for years, I suspect.
> What triggered me to comment on your patch was that its directory and file
> structure is very different from the ones there. There are no cpu-, proc-
> and unit- directories and no names with mn103e10_* there.
Things are allowed to change.
> The kernels there seem to be already running on several processors,
> some of which are with AM34 cores that you concern about, according to
> the #ifdefs there.
Yes.
> > The problem is how much? I could just move all the cpu-am33v2/ files into
> > the dir above, but what happens if an incompatible CPU core is introduced?
>
> How does your client say?
MEI have agreed for me to do that. I can always undo it later if sufficiently
incompatible CPU cores arise that warrant that level of segregation.
David
prev parent reply other threads:[~2007-11-05 16:05 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
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 [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=15038.1194277085@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 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.