From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nicolas DET <nd@bplan-gmbh.de>
Cc: linuxppc-dev@ozlabs.org, Olaf Hering <olaf@aepfle.de>,
linux-kernel@vger.kernel.org
Subject: Re: Badness in irq_create_mapping at arch/powerpc/kernel/irq.c:527
Date: Fri, 20 Oct 2006 09:33:28 +1000 [thread overview]
Message-ID: <1161300808.10524.62.camel@localhost.localdomain> (raw)
In-Reply-To: <45377ED3.9030001@bplan-gmbh.de>
On Thu, 2006-10-19 at 15:34 +0200, Nicolas DET wrote:
> Olaf Hering wrote:
> > I get irq warnings with current Linus tree on Pegasos.
> > The EDID handling for radeonfb appears to be broken as well,
> > but thats a different story:
> >
>
> This patch enables chrp_pcibios_fixup() for bPlan's machine. however,
> this function should NOT be called as thoses platforms.
>
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=26c5032eaa64090b2a01973b0c6ea9e7f6a80fa7
>
> An upcomming patch will "ppc_md.pcibios_fixup = NULL;" for every bPlan's
> platforms.
Ugh ?
I'm not sure what the patch you pointed to has to do with fixups :)
Anyway, the irq code should work with Pegasos. I think the problem is
that it's missing a call to irq_set_default_host() on the i8259 when no
MPIC is present. It's strange, I though I had it... BriQ needs it too.
Ben.
next prev parent reply other threads:[~2006-10-19 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 12:28 Badness in irq_create_mapping at arch/powerpc/kernel/irq.c:527 Olaf Hering
2006-10-19 13:34 ` Nicolas DET
2006-10-19 23:33 ` Benjamin Herrenschmidt [this message]
2006-10-20 1:37 ` Benjamin Herrenschmidt
2006-10-20 1:47 ` Stephen Rothwell
2006-10-20 3:24 ` Benjamin Herrenschmidt
2006-10-20 5:02 ` Sven Luther
2006-10-20 6:19 ` Olaf Hering
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=1161300808.10524.62.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nd@bplan-gmbh.de \
--cc=olaf@aepfle.de \
/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).