From: Ralf Baechle <ralf@linux-mips.org>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux-mips@linux-mips.org,
CE Linux Developers List <celinux-dev@tree.celinuxforum.org>
Subject: Re: CONFIG_XIP_ROM vs. CONFIG_XIP_KERNEL
Date: Fri, 30 Apr 2004 03:34:10 +0200 [thread overview]
Message-ID: <20040430013410.GA29246@linux-mips.org> (raw)
In-Reply-To: <40916C15.7000500@am.sony.com>
On Thu, Apr 29, 2004 at 01:56:53PM -0700, Tim Bird wrote:
> Well this is interesting. One the architectures where this is supported
> in my tree is MIPS. I'm looking at the CELF source tree. The patch for
> this was submitted to me by Toshiba. I had assumed (based on some other
> indications) that they were submitting stuff to me that they had already
> submitted to kernel.org or to the MIPS list. This appears not to be
> the case.
>
> We should discuss this. I have some patches for MIPS stuff in the
> CELF tree from MontaVista, Toshiba, and NEC. Unfortunately, the
> CELF tree is based on Linux 2.4.20, so I don't know how much of it,
> if any, would be useful to you.
Depends. The linux-mips.org tree is at 2.4.26. Some areas have changed
significantly since 2.4.20, some not at all. If you want to send patches
please make sure they still apply to the latest kernel.
> How do I proceed with finding out what's interesting, and how to get
> it to you? Just post some stuff (even if old) to the mips mailing
> list? Request the originator to do such a post? Do things need to
> be migrated to 2.6?
Preferably yes. I don't really care who sends the patch as long as the
sender takes responsibility also after the initial submission.
Any new features preferably for 2.6.
> Could we bypass that for a casual "is this interesting" review? Etc.
If all you need is a comment, sure.
> The questions are endless.
> Let me know what you think.
>
> And, BTW, in my tree the variable used for MIPS is CONFIG_XIP_ROM.
> For SH, it's CONFIG_XIP_KERNEL, and for ARM, it has conditionals
> for both, but only defines CONFIG_XIP_ROM in the config.in!
In the kernel.org kernel the only references to these symbols are to
CONFIG_XIP_KERNEL in a few files under arch/arm26.
Ralf
next prev parent reply other threads:[~2004-04-30 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 19:07 CONFIG_XIP_ROM vs. CONFIG_XIP_KERNEL Tim Bird
2004-04-29 20:09 ` Ralf Baechle
[not found] ` <40916C15.7000500@am.sony.com>
2004-04-30 1:34 ` Ralf Baechle [this message]
2004-04-29 20:49 ` Nicolas Pitre
2004-04-29 20:49 ` Nicolas Pitre
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=20040430013410.GA29246@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-mips@linux-mips.org \
--cc=tim.bird@am.sony.com \
/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.