linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: asm/delay.h missing on powerpc (was: Re: Linuv 2.6.15-rc1)
Date: Sun, 13 Nov 2005 10:54:56 +0100	[thread overview]
Message-ID: <200511131054.57289.mbuesch@freenet.de> (raw)
In-Reply-To: <1131841993.5504.13.camel@gaston>

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

On Sunday 13 November 2005 01:33, you wrote:
> On Sun, 2005-11-13 at 00:13 +0100, Michael Buesch wrote:
> > On Saturday 12 November 2005 23:24, you wrote:
> > > Ìt should still work. I'm running -rc1 with "powerpc" on mine so that at
> > > least works, it's possible that we broke "ppc", I'll have a look and
> > > send a fix.
> > 
> > powerpc arch builds and runs now, but
> > I have problems compiling the bcm430x driver. It includes linux/delay.h.
> > linux/delay.h includes asm/delay.h, which does not exist.
> > What to do now?
> 
> I suspect that building drivers out of tree doesn't work very well with
> the new "merged" architecture where includes are split between asm/ppc
> and asm-powerpc... You should make sure that you build the driver with
> the same ARCH as the kernel, that is ARCH=powerpc at least, if we got
> the Makefiles right, that should give you all the headers...

Call me an idiot ;)
doing make ARCH=powerpc in the driver works perfectly fine.

> (building glibc is definitely a pain :)

Try out the stable LFS book. It will guilde you trough it step by step. ;)

-- 
Greetings Michael.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-11-13  9:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0511111753080.3263@g5.osdl.org>
2005-11-12 20:45 ` Linuv 2.6.15-rc1 Michael Buesch
2005-11-12 21:00   ` Linus Torvalds
2005-11-12 21:37     ` Michael Buesch
2005-11-12 21:53       ` Adrian Bunk
2005-11-12 21:57         ` Michael Buesch
2005-11-12 22:20           ` Adrian Bunk
2005-11-12 22:31             ` Benjamin Herrenschmidt
2005-11-12 23:51               ` Ulrich Teichert
2005-11-13  9:17                 ` Geert Uytterhoeven
2005-11-13 14:46                   ` Powerstack II (was: Re: Linuv 2.6.15-rc1) Ulrich Teichert
2005-11-13  1:26               ` [2.6 patch] PPC_PREP: remove unneeded exports Adrian Bunk
2005-11-13  3:23                 ` Benjamin Herrenschmidt
2005-11-14 19:56               ` Linuv 2.6.15-rc1 Tom Rini
2005-11-12 22:08       ` Olof Johansson
2005-11-12 22:25       ` Benjamin Herrenschmidt
2005-11-12 22:33         ` Michael Buesch
2005-11-13 16:37         ` Kumar Gala
2005-11-13 20:59           ` Benjamin Herrenschmidt
2005-11-15 18:53             ` Olaf Hering
2005-11-14  1:04       ` Jesper Juhl
2005-11-12 22:24     ` Benjamin Herrenschmidt
2005-11-12 23:13       ` asm/delay.h missing on powerpc (was: Re: Linuv 2.6.15-rc1) Michael Buesch
2005-11-13  0:33         ` Benjamin Herrenschmidt
2005-11-13  9:54           ` Michael Buesch [this message]
2005-11-12 21:28   ` PowerBook G4 boot failure " Alexey Dobriyan

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=200511131054.57289.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).