From: Adrian Bunk <bunk@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-am33-list@redhat.com
Subject: Re: [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #3]
Date: Thu, 8 Nov 2007 05:13:14 +0100 [thread overview]
Message-ID: <20071108041314.GG26163@stusta.de> (raw)
In-Reply-To: <20071107174323.31820.65054.stgit@warthog.procyon.org.uk>
On Wed, Nov 07, 2007 at 05:43:23PM +0000, David Howells wrote:
>
>
> These patches add the MEI/Panasonic MN10300/AM33 architecture to the Linux
> kernel.
>
> The first patch suppresses AOUT support in the kernel if CONFIG_BINFMT_AOUT=n
> and CONFIG_IA32_AOUT=n. MN10300 does not support the AOUT binfmt, so the ELF
> binfmt should not be permitted to go looking for AOUT libraries to load, nor
> should random bits of the kernel depend on asm/a.out.h.
>
> The second patch adds the architecture itself, to be selected by ARCH=mn10300
> on the make command line.
>
> The patches can also be downloaded from:
>
> http://people.redhat.com/~dhowells/mn10300/mn10300-arch.tar.bz2
The patch to include/asm-generic/Kbuild.asm doesn't seem to be required.
+#elif defined(__mn10300__)
Please use a CONFIG_ variable in such cases.
The parts outside arch/mn10300/ and include/asm-mn10300/ (except for the
trivial "&& {,!}MN10300" Kconfig changes) should go separately through
the maintainers or get ACKs from the maintainers, even more since they
also contain cleanups like
- .regions = {ERASEINFO(0x01000,64),
+ .regions = {
+ ERASEINFO(0x01000,64),
}
--- a/include/linux/kprobes.h
+++ b/include/linux/kprobes.h
...
+extern void __kprobes arch_remove_kprobe(struct kprobe *p);
This looks as if it will break compilation on avr32 and sparc64.
> A suitable toolchain can be downloaded from:
>
> ftp://ftp.redhat.com/pub/redhat/gnupro/AM33/
>...
What is the status of support in upstream GNU binutils and GNU gcc?
> David
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-11-08 4:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 17:43 [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #3] David Howells
2007-11-07 17:43 ` [PATCH 1/2] Suppress A.OUT library support in ELF binfmt if !CONFIG_BINFMT_AOUT " David Howells
2007-11-07 17:52 ` Mike Frysinger
2007-11-07 22:07 ` David Woodhouse
2007-11-07 23:30 ` David Howells
2007-11-07 23:54 ` Adrian Bunk
2007-11-08 4:13 ` Adrian Bunk [this message]
2007-11-08 14:00 ` [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel " David Howells
2007-11-09 11:02 ` Adrian Bunk
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=20071108041314.GG26163@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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