* linuxppc_2_4_devel patch to arch/ppc/kernel/setup.c
@ 2003-05-22 23:19 Mark A. Greer
0 siblings, 0 replies; only message in thread
From: Mark A. Greer @ 2003-05-22 23:19 UTC (permalink / raw)
To: linuxppc-dev
[-- 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-05-22 23:19 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-22 23:19 linuxppc_2_4_devel patch to arch/ppc/kernel/setup.c Mark A. Greer
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).