From: Nicolas DET <nd@bplan-gmbh.de>
To: Olaf Hering <olaf@aepfle.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Badness in irq_create_mapping at arch/powerpc/kernel/irq.c:527
Date: Thu, 19 Oct 2006 15:34:11 +0200 [thread overview]
Message-ID: <45377ED3.9030001@bplan-gmbh.de> (raw)
In-Reply-To: <20061019122802.GA26637@aepfle.de>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
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.
Regards,
[-- Attachment #2: nd.vcf --]
[-- Type: text/x-vcard, Size: 249 bytes --]
begin:vcard
fn:Nicolas DET ( bplan GmbH )
n:DET;Nicolas
org:bplan GmbH
adr:;;;;;;Germany
email;internet:nd@bplan-gmbh.de
title:Software Entwicklung
tel;work:+49 6171 9187 - 31
x-mozilla-html:FALSE
url:http://www.bplan-gmbh.de
version:2.1
end:vcard
next prev parent reply other threads:[~2006-10-19 13:36 UTC|newest]
Thread overview: 14+ 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 [this message]
2006-10-19 23:33 ` Benjamin Herrenschmidt
2006-10-19 23:33 ` Benjamin Herrenschmidt
2006-10-20 1:37 ` Benjamin Herrenschmidt
2006-10-20 1:37 ` Benjamin Herrenschmidt
2006-10-20 1:47 ` Stephen Rothwell
2006-10-20 1:47 ` Stephen Rothwell
2006-10-20 3:24 ` Benjamin Herrenschmidt
2006-10-20 3:24 ` Benjamin Herrenschmidt
2006-10-20 5:02 ` Sven Luther
2006-10-20 5:02 ` Sven Luther
2006-10-20 6:19 ` Olaf Hering
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=45377ED3.9030001@bplan-gmbh.de \
--to=nd@bplan-gmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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 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.