From: "James Black" <jblack547@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: muram in device tree for mpc8250 in arch/powerpc
Date: Mon, 24 Mar 2008 16:28:52 -0600 [thread overview]
Message-ID: <b77025b40803241528j210ee097j64b9d7dd2ee73c84@mail.gmail.com> (raw)
In-Reply-To: <b77025b40803241509p44162ebfg2728bec85efb5d7a@mail.gmail.com>
That was it. It seems that the eldk/4.2 is missing the ilog2_u32
declaration. Makes me wonder what else is missing. I'll start again
with the kernel.org version and see what happens.
I'll send an email when this work gets done. Good catch.
JB
On Mon, Mar 24, 2008 at 4:09 PM, James Black <jblack547@gmail.com> wrote:
> I must have the old one. I don't see '__ilog2_u32' defined. This is
> the kernel I got from denx eldk 4.2. I'll grab the kernel from
> kernel.org and check there. Thanks.
>
> JB
>
>
>
> On Mon, Mar 24, 2008 at 4:05 PM, Scott Wood <scottwood@freescale.com> wrote:
> > James Black wrote:
> > > OK, you are right. I was looking at my old copy I was trying to fix.
> > > The error is,
> > >
> > > arch/powerpc/boot/cuboot-pq2.c: In function 'fixup_pci':
> > > arch/powerpc/boot/cuboot-pq2.c:204: warning: implicit declaration of
> > > function '__ilog2_u32'
> >
> > It's defined as an inline function in ops.h. Do you have an old ops.h?
> >
> > -Scott
> >
>
prev parent reply other threads:[~2008-03-24 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 17:06 muram in device tree for mpc8250 in arch/powerpc James Black
2008-03-19 17:40 ` Scott Wood
[not found] ` <b77025b40803191107x2f9a7884n9b7f062fcf45370@mail.gmail.com>
2008-03-20 18:02 ` James Black
2008-03-20 18:20 ` Scott Wood
2008-03-20 23:02 ` James Black
2008-03-21 16:18 ` Scott Wood
2008-03-21 20:14 ` James Black
2008-03-21 20:34 ` Scott Wood
2008-03-21 21:35 ` James Black
2008-03-24 16:52 ` Scott Wood
2008-03-24 21:45 ` James Black
2008-03-24 21:53 ` Scott Wood
2008-03-24 21:59 ` James Black
2008-03-24 22:05 ` Scott Wood
2008-03-24 22:09 ` James Black
2008-03-24 22:28 ` James Black [this message]
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=b77025b40803241528j210ee097j64b9d7dd2ee73c84@mail.gmail.com \
--to=jblack547@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.com \
/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).