From: Sven Luther <sven.luther@wanadoo.fr>
To: Christian <evil@g-house.de>
Cc: Tom Rini <trini@kernel.crashing.org>,
Meelis Roos <mroos@linux.ee>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, Sven Hartge <hartge@ds9.gnuu.de>
Subject: Re: [PATCH 2.6.10-rc3][PPC32] Fix Motorola PReP (PowerstackII Utah) PCI IRQ map
Date: Fri, 25 Feb 2005 13:15:37 +0100 [thread overview]
Message-ID: <20050225121536.GA20174@pegasos> (raw)
In-Reply-To: <49984.195.126.66.126.1109332744.squirrel@housecafe.dyndns.org>
On Fri, Feb 25, 2005 at 12:59:04PM +0100, Christian wrote:
> On Fri, February 25, 2005 7:36, Sven Luther said:
> > So, now, we need to find out what the problems where, i think it is
> > something that went in between 2.6.8 and 2.6.10, and leigh said he had
> > some ideas.
>
> may i ask what patches were applied to a vanilla 2.6.8 kernel to build the
> 2.6.8-d-i then?
Some backports that i got from the list. The complete list of patches is at :
http://svn.debian.org/wsvn/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches/?rev=0&sc=0
And i guess the one at hand here is :
http://svn.debian.org/wsvn/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches/powerpc-prep-powerstack-irq.dpatch?op=file&rev=0&sc=0
--- kernel-source-2.6.8.orig/arch/ppc/platforms/prep_pci.c 2004-12-28
08:24:07.000000000 +0100
+++ kernel-source-2.6.8/arch/ppc/platforms/prep_pci.c 2005-01-03
11:15:30.604274816 +0100ll lines beginning with `## DP:' are a description of
the patch.
## DP: Description: Fix PReP - motorola powerstack II utah pci irq mapping.
## DP: Patch author: Tom Rini <trini@kernel.crashing.org>
## DP: Upstream status: backport
. $(dirname $0)/DPATCH
@DPATCH@
@@ -115,13 +115,13 @@
static char Utah_pci_IRQ_map[23] __prepdata =
{
0, /* Slot 0 - unused */
- 0, /* Slot 1 - unused */
+ 4, /* Slot 1 - IDE - SL82C105 */
5, /* Slot 2 - SCSI - NCR825A */
0, /* Slot 3 - unused */
- 1, /* Slot 4 - Ethernet - DEC2114x */
+ 3, /* Slot 4 - Ethernet - DEC2114x */
0, /* Slot 5 - unused */
- 3, /* Slot 6 - PCI Card slot #1 */
- 4, /* Slot 7 - PCI Card slot #2 */
+ 2, /* Slot 6 - PCI Card slot #1 */
+ 3, /* Slot 7 - PCI Card slot #2 */
5, /* Slot 8 - PCI Card slot #3 */
5, /* Slot 9 - PCI Bridge */
/* added here in case we ever support PCI bridges */
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-02-25 12:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 18:54 [PATCH 2.6.10-rc3][PPC32] Fix Motorola PReP (PowerstackII Utah) PCI IRQ map Tom Rini
2004-12-07 18:21 ` Linus Torvalds
2004-12-07 18:23 ` Linus Torvalds
2005-02-22 8:36 ` Meelis Roos
2005-02-22 12:01 ` Sebastian Heutling
2005-02-22 12:23 ` Leigh Brown
2005-02-22 16:27 ` Christian Kujau
2005-02-22 18:27 ` Sebastian Heutling
2005-02-24 7:47 ` Sven Luther
2005-02-24 15:47 ` Meelis Roos
2005-02-24 16:06 ` Sven Luther
2005-02-24 16:34 ` Meelis Roos
2005-02-24 17:01 ` Sven Luther
2005-02-24 20:51 ` Meelis Roos
2005-02-25 0:24 ` Christian Kujau
2005-02-25 6:36 ` Sven Luther
2005-02-25 11:59 ` Christian
2005-02-25 12:15 ` Sven Luther [this message]
2005-02-26 3:39 ` Christian
2005-02-26 6:04 ` Sven Luther
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=20050225121536.GA20174@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=evil@g-house.de \
--cc=hartge@ds9.gnuu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mroos@linux.ee \
--cc=trini@kernel.crashing.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).