Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Bryan Chua <chua@ayrnetworks.com>
To: linux-mips@oss.sgi.com
Subject: arch/mips/setup.c
Date: Mon, 21 Jan 2002 14:02:10 -0800	[thread overview]
Message-ID: <3C4C8FE2.9090800@ayrnetworks.com> (raw)

I recall a bunch of disussion about changing arch/mips/setup.c to 
simplify adding vendor-specific platform code in setup_arch, but to date 
nothing has come of it.  So while this is a dramatic oversimplification 
of the various proposals, how about this for now --

just a vendor-defined function "platform_setup (void)" and it is up to 
the vendor to figure out what to do from there.

-- bryan


Index: arch/mips/kernel/setup.c
===================================================================
RCS file: /cvs/linux/arch/mips/kernel/setup.c,v
retrieving revision 1.96.2.3
diff -u -r1.96.2.3 setup.c
--- arch/mips/kernel/setup.c	2001/12/26 23:27:02	1.96.2.3
+++ arch/mips/kernel/setup.c	2002/01/21 22:55:35
@@ -666,6 +666,7 @@
   	void it8172_setup(void);
  	void swarm_setup(void);
  	void hp_setup(void);
+ 
void platform_setup (void);

  	unsigned long bootmap_size;
  	unsigned long start_pfn, max_pfn, first_usable_pfn;
@@ -793,7 +794,8 @@
                  break;
  #endif
  	default:
- 
	panic("Unsupported architecture");
+ 
         platform_setup ();
+ 
	break;
  	}

  	strncpy(command_line, arcs_cmdline, sizeof command_line);

             reply	other threads:[~2002-01-21 23:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 22:02 Bryan Chua [this message]
2002-01-22  9:17 ` arch/mips/setup.c Geert Uytterhoeven
2002-01-22 19:52   ` arch/mips/setup.c Bryan Chua

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=3C4C8FE2.9090800@ayrnetworks.com \
    --to=chua@ayrnetworks.com \
    --cc=linux-mips@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox