[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <15038.1194277085@redhat.com>
Date: Mon, 05 Nov 2007 15:38:05 +0000
From: David Howells <dhowells@...hat.com>
To: "Suzuki Takashi" <suzuki.takashi@...il.com>
Cc: dhowells@...hat.com, torvalds@...l.org, akpm@...ux-foundation.org,
linux-am33-list@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [Linux-am33-list] [PATCH 2/2] MN10300: Add the MN10300/AM33 architecture to the kernel [try #2]
Suzuki Takashi <suzuki.takashi@...il.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists