All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaw Terwilliger <sterwill@io.nu>
To: Martin Costabel <costabel@wanadoo.fr>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch] Paul's rsync kernel compile fix
Date: Sat, 25 Sep 1999 11:48:27 -0500	[thread overview]
Message-ID: <19990925114827.B8312@io.nu> (raw)
In-Reply-To: <37ECF9A9.10B58B88@wanadoo.fr>


Martin Costabel wrote:
> Oh, I see. We are indeed not talking about the same thing. I have the
> development tree (2.3.18), and there arch/ppc/kernel/pmac_setup.c does
> include <asm/dma.h>. 
> What if you just plug a "#include <asm/dma.h>" in there? But then I
> don't know whether the declarations in question are there in this
> version.

Yep, dma.h holds the declarations, and sticking it in pmac_setup.c
corrects my problems.  I thought there must have been a much more
complicated solution because I couldn't imagine I was the only one
seeing this error.  :)

> BTW, Paul's 2.3.18 compiles cleanly (and boots, in contrast to the
> 2.3.18 version from the cvs tree at openprojects), at least if HFS
> support is switched off.

I've got 2.2.12 working very nicely with my Lombard, and generally
I'm aware of the differences between stable/dev kernels, but is
there anything really cool in 2.3.18 for the PPC (from Paul's
archive) that might lead me to switch to it?

-- 
Shaw Terwilliger (sterwill@io.nu)

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~1999-09-25 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-25  3:22 [patch] Paul's rsync kernel compile fix Shaw Terwilliger
1999-09-25  9:26 ` Martin Costabel
     [not found]   ` <19990925110256.A8137@io.nu>
     [not found]     ` <37ECF9A9.10B58B88@wanadoo.fr>
1999-09-25 16:48       ` Shaw Terwilliger [this message]
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=19990925114827.B8312@io.nu \
    --to=sterwill@io.nu \
    --cc=costabel@wanadoo.fr \
    --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.