All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: linuxppc_2_4_devel patch to arch/ppc/kernel/setup.c
Date: Thu, 22 May 2003 16:19:58 -0700	[thread overview]
Message-ID: <3ECD5B1E.4070805@mvista.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 539 bytes --]

This is a minor patch to move the default setting of the default
loops_per_jiffy to before the call to platform_init().  This would be
necessary if someone required a reasonable value for loops_per_jiffy so
that their progress output would work (e.g., polled UART I/O that
required a udelay() call).  Ideally, this should never be necessary
since the board-specific platform_init() should set it up correctly.
This is just in case.

Mark

P.S., I would almost prefer just getting rid of the default
loops_per_jiffy setup.  Anyone else?
--

[-- Attachment #2: setup.patch --]
[-- Type: text/plain, Size: 733 bytes --]

===== arch/ppc/kernel/setup.c 1.119 vs edited =====
--- 1.119/arch/ppc/kernel/setup.c	Mon Apr 21 17:13:07 2003
+++ edited/arch/ppc/kernel/setup.c	Thu May  8 17:43:26 2003
@@ -513,6 +513,9 @@
 	strcpy(cmd_line, CONFIG_CMDLINE);
 #endif /* CONFIG_CMDLINE */

+	/* so udelay does something sensible, assume <= 1000 bogomips */
+	loops_per_jiffy = 500000000 / HZ;
+
 	platform_init(r3, r4, r5, r6, r7);

 	if (ppc_md.progress_init)
@@ -558,9 +561,6 @@
 	extern char _etext[], _edata[];
 	extern char *klimit;
 	extern void do_init_bootmem(void);
-
-	/* so udelay does something sensible, assume <= 1000 bogomips */
-	loops_per_jiffy = 500000000 / HZ;

 #ifdef CONFIG_ALL_PPC
 	/* This could be called "early setup arch", it must be done

                 reply	other threads:[~2003-05-22 23:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3ECD5B1E.4070805@mvista.com \
    --to=mgreer@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.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 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.