From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Andy Fleming <afleming@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Fix IRQ handling on MPC8540 ADS
Date: Fri, 18 Aug 2006 23:33:38 +0400 [thread overview]
Message-ID: <44E61612.6070405@ru.mvista.com> (raw)
In-Reply-To: <44E608F3.4060505@ru.mvista.com>
Hello.
Sergei Shtylyov wrote:
>>* Fixed IRQ handling for the 85xx ADS boards so it uses the new
>> generic irq stuff
>>* Fixed PCI IRQ mapping so it comes from the device tree
> NAK. The kernel doesn't build with this patch. I'm getting this:
> CC arch/powerpc/platforms/85xx/mpc85xx_ads.o
> arch/powerpc/platforms/85xx/mpc85xx_ads.c: In function `mpc85xx_ads_pic_init':
> arch/powerpc/platforms/85xx/mpc85xx_ads.c:76: warning: implicit declaration of
> function `of_put_node'
> and then finally:
> LD .tmp_vmlinux1
> arch/powerpc/platforms/built-in.o(.init.text+0x26c): In function
> `mpc85xx_ads_pic_init':
> arch/powerpc/platforms/85xx/mpc85xx_ads.c:84: undefined reference to `of_put_node'
> arch/powerpc/platforms/built-in.o(.init.text+0x404):arch/powerpc/platforms/85xx/mpc85xx_ads.c:76:
> undefined reference to `of_put_node'
> make: *** [.tmp_vmlinux1] Error 1
>
> There's no such function in the kernel -- it actually aclled
> of_node_put(). I can post an updated patch after testing (if it succeeds) if
> you like...
Alas, the patched kernel didn't boot further than the early startup
messages (after I've updated U-Boot with the correct PIC device type).
>>This patch *really* needs to go in before 2.6.18 is final, else 2.6.18
>>doesn't build for 85xx.
> Looks like it's a bit crude yet to be committed...
Not even compile tested. :-/
WBR, Sergei
next prev parent reply other threads:[~2006-08-18 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 1:22 [PATCH] Fix IRQ handling on MPC8540 ADS Andy Fleming
2006-08-18 18:37 ` Sergei Shtylyov
2006-08-18 19:33 ` Sergei Shtylyov [this message]
2006-08-18 20:48 ` Andy Fleming
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=44E61612.6070405@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).