linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jerome Glisse <j.glisse@gmail.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc64-dev@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: Classic PPC specific ASM (CONFIG_6XX)
Date: Fri, 21 Jan 2005 12:22:10 +0100	[thread overview]
Message-ID: <4240b916050121032230b9c5dc@mail.gmail.com> (raw)
In-Reply-To: <20050120231442.GE2626@smtp.west.cox.net>

On Thu, 20 Jan 2005 16:14:42 -0700, Tom Rini <trini@kernel.crashing.org> wrote:
> On Wed, Jan 12, 2005 at 08:10:58PM +0100, Jerome Glisse wrote:
> 
> > Wanted to know what is going on with CONFIG_6xx?  You will use
> > my patch or do you have another better way ? :)
> 
> Can you resend it please?
> 

Here is another version (the previous one used ifdef to comment
out function call but i read somewhere that this doesn't follow
codeguideline). Anyway i think that my patch is a ugly hack.

Signed-off-by: Jerome Glisse <j.glisse@gmail.com>

best,
Jerome Glisse



diff -Naur linux/arch/ppc/boot/simple/misc-prep.c
linux-2.6.10/arch/ppc/boot/simple/misc-prep.c
--- linux/arch/ppc/boot/simple/misc-prep.c	2004-12-24 22:33:51.000000000 +0100
+++ linux-2.6.10/arch/ppc/boot/simple/misc-prep.c	2005-01-21
12:09:50.976426672 +0100
@@ -34,7 +34,11 @@
 extern void serial_fixups(void);
 extern struct bi_record *decompress_kernel(unsigned long load_addr,
 		int num_words, unsigned long cksum);
+#ifdef CONFIG_6XX
 extern void disable_6xx_mmu(void);
+#elif
+void disable_6xx_mmu(void) {}
+#endif
 extern unsigned long mpc10x_get_mem_size(void);
 
 static void

  parent reply	other threads:[~2005-01-21 11:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 15:40 Classic PPC specific ASM (CONFIG_6XX) Jerome Glisse
2005-01-09 21:03 ` Paul Mackerras
2005-01-10 14:52   ` Tom Rini
2005-01-10 16:39     ` Christoph Hellwig
2005-01-10 16:44       ` Tom Rini
2005-01-10 18:14     ` Jerome Glisse
2005-01-10 18:29       ` Tom Rini
2005-01-10 18:59         ` Jerome Glisse
2005-01-10 19:12           ` Tom Rini
2005-01-10 19:31             ` Jerome Glisse
     [not found]               ` <4240b91605011211101ed322a8@mail.gmail.com>
     [not found]                 ` <20050120231442.GE2626@smtp.west.cox.net>
2005-01-21 11:22                   ` Jerome Glisse [this message]
2005-01-21 12:36                     ` Geert Uytterhoeven

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=4240b916050121032230b9c5dc@mail.gmail.com \
    --to=j.glisse@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).