linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gardiner <daveg@sonartech.com.au>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: powerpc with gigabit card hanging
Date: Wed, 29 Sep 2004 08:45:01 +1000	[thread overview]
Message-ID: <4159E96D.5040207@sonartech.com.au> (raw)
In-Reply-To: <20040927235948.G30772@home.com>

[-- Attachment #1: Type: text/plain, Size: 561 bytes --]


>only the PMCSPAN IDSEL routing is missing. Don't know what your 2.4
>  
>
linuxppc_2_4_devel

>kernel looks like or your current map in your 2.6 port.
>  
>
Thanks Matt, that was pretty easy once I knew where to look, being that 
the gigabit was on the span card and they were all set to zero and in 
the linuxppc_2_4_devel tree they weren't, anyway the patch is attatched. 
I don't want anything to be done with this patch as I still would like 
to "try" and fold the mvme5100 into pplus and I'm only attatching it in 
case I get hit by a bus.

dodah,
dlg
 

[-- Attachment #2: irq.patch --]
[-- Type: text/plain, Size: 586 bytes --]

--- play-2.6.9.patched.changed.compile/arch/ppc/platforms/mvme5100.c.orig	2004-09-29 08:25:47.549383101 +1000
+++ play-2.6.9.patched.changed.compile/arch/ppc/platforms/mvme5100.c	2004-09-29 08:25:54.199430187 +1000
@@ -81,7 +81,7 @@ mvme5100_map_irq(struct pci_dev *dev, un
 		{ 28, 25, 26, 27 },	/* IDSEL 17 - PMC Slot 2 */
 		{  0,  0,  0,  0 },	/* IDSEL 18 - unused */
 		{ 29,  0,  0,  0 },	/* IDSEL 19 - Enet 2 */
-		{  0,  0,  0,  0 },	/* IDSEL 20 - PMCSPAN */
+		{ 25, 26, 27, 28 }, /* IDSEL 20 - PMCSPAN */
 	};
 
 	const long min_idsel = 11, max_idsel = 20, irqs_per_slot = 4;

      reply	other threads:[~2004-09-28 22:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  4:32 powerpc with gigabit card hanging David Gardiner
2004-09-24 15:01 ` Segher Boessenkool
2004-09-28  3:41   ` David Gardiner
2004-09-28  5:13     ` Matt Porter
     [not found]       ` <C617C694-1110-11D9-8370-000A95A4DC02@kernel.crashing.org>
2004-09-28  5:48         ` Matt Porter
2004-09-28  5:58           ` Segher Boessenkool
2004-09-28  6:14             ` Matt Porter
2004-09-28  6:23               ` Segher Boessenkool
2004-09-28  6:37                 ` Matt Porter
2004-09-28  6:45                   ` Segher Boessenkool
2004-09-28  7:01                     ` Matt Porter
2004-09-28  7:10                       ` Segher Boessenkool
2004-09-28  6:46               ` David Gardiner
2004-09-28  6:59                 ` Matt Porter
2004-09-28 22:45                   ` David Gardiner [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=4159E96D.5040207@sonartech.com.au \
    --to=daveg@sonartech.com.au \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mporter@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).