linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shaw Terwilliger <sterwill@io.nu>
To: linuxppc-dev@lists.linuxppc.org
Subject: [patch] Paul's rsync kernel compile fix
Date: Fri, 24 Sep 1999 22:22:14 -0500	[thread overview]
Message-ID: <19990924222214.A7489@io.nu> (raw)

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

I've been compiling Paul's rsync kernel on my PowerBook G3 and I've
prepared a patch that blocks out some undeclared (and reference)
variable initializations in linux/arch/ppc/kernel/pmac_setup.c.  A quick
look at the other ????_setup.c (prep, chrp, apus) shows this might also
be useful there, but I didn't run through the compiles to check.

Has everyone else had the same problem compiling these kernels?  

This is the first time I've dug around in "kernel" kernel stuff,
and I think I'm clear on why these variables really don't mean
anything, but I could always be wrong.  :)

-- 
Shaw Terwilliger (sterwill@io.nu)

[-- Attachment #2: pmac_setup.c.diff --]
[-- Type: text/plain, Size: 591 bytes --]

--- pmac_setup.c.orig	Fri Sep 24 18:27:25 1999
+++ pmac_setup.c	Fri Sep 24 18:29:27 1999
@@ -594,9 +594,15 @@
 	/* isa_io_base gets set in pmac_find_bridges */
 	isa_mem_base = PMAC_ISA_MEM_BASE;
 	pci_dram_offset = PMAC_PCI_DRAM_OFFSET;
+
+	/* These three variables don't seem to be used in pmac_setup.c and 
+	   aren't declared anywhere.  Do we need them at all?  They're 
+	   declared "unsigned long" in arch/ppc/kernel/setup.c */
+/*
 	ISA_DMA_THRESHOLD = ~0L;
 	DMA_MODE_READ = 1;
 	DMA_MODE_WRITE = 2;
+*/
 
 	ppc_md.setup_arch     = pmac_setup_arch;
 	ppc_md.setup_residual = NULL;

             reply	other threads:[~1999-09-25  3:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-25  3:22 Shaw Terwilliger [this message]
1999-09-25  9:26 ` [patch] Paul's rsync kernel compile fix Martin Costabel
     [not found]   ` <19990925110256.A8137@io.nu>
     [not found]     ` <37ECF9A9.10B58B88@wanadoo.fr>
1999-09-25 16:48       ` Shaw Terwilliger
1999-09-25 17:21   ` Michael Fenske
1999-09-25 16:44     ` Shaw Terwilliger

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=19990924222214.A7489@io.nu \
    --to=sterwill@io.nu \
    --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 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).