linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Heutling <sheutlin@gmx.de>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linuxppc-dev@ozlabs.org,
	Marc Dietrich <Marc.Dietrich@ap.physik.uni-giessen.de>
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Sun, 02 Jan 2005 00:56:29 +0100	[thread overview]
Message-ID: <1104623790.10369.14.camel@weizen.left.earth> (raw)
In-Reply-To: <20041231222808.GB8078@pegasos>

On Fri, 2004-12-31 at 23:28 +0100, Sven Luther wrote:
> On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote:
> > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote:
> > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote:
> > > > Marc Dietrich schrieb:
> > > > >Hi all,
> > > > >
> > > > >I read this thread about booting a PowerStack with newer kernels. 
> > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with 
> > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during 
> > > > >initialisation. I 
> > > 
> > > I also have some strange issues with network support using the standard debian
> > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes
> > > the kernel, and i hear reports of problems on IBM PReP hardware too with not
> > > working ethernet, altough there is no freeze.
> > > 
> > > Any idea on this ? 
> > 
> > Does it contain the IRQ patch? Where does it boot from SCSI or net? What
> > PCI-Devices are installed?
> 
> Probably not, just the standard debian kernel, i donÃ't remember any irq
> patches, but there where a bunch of patches from leighbb. it is done

The patch is the one that is included in 2.6.10 which is mentioned above
and this thread already has somewhere in the beginning. I attached it
below.
I haven't had the time yet to test the 2.6.10 kernel. Maybe there is
another problem now ...


> netbooting, and the only pci device installed is the cirruss logic graphic
> card.

If you use the standard debian kernel - ok, it doesn't work because of
wrong IRQs on the PowerstackII (Utah).


BTW: The onboard Winbond IDE chip works as well although no connector is
provided. You only need a little bit of soldering and adjusting the IRQ
of Slot 1 from 0 to 4. :-)


Sebastian Heutling

-- 
diff -puN
arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map arch/ppc/platforms/prep_pci.c
---
25/arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map      2004-12-07 01:01:16.000000000 -0800
+++ 25-akpm/arch/ppc/platforms/prep_pci.c       2004-12-07
01:01:16.000000000 -0800
@@ -49,10 +49,10 @@ static char Utah_pci_IRQ_map[23] __prepd
         0,   /* Slot 1  - unused */
         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 */

  reply	other threads:[~2005-01-01 23:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-26 13:35 [FYI] linux 2.6 still not working with PReP (ppc32) Marc Dietrich
2004-12-27  2:47 ` Christian
2004-12-27 21:37   ` Marc Dietrich
2005-01-02  0:31     ` Sebastian Heutling
2005-01-03 12:26       ` Marc Dietrich
2005-01-04  0:54         ` evilninja
2005-01-04 11:31         ` Sebastian Heutling
2005-01-04 14:04           ` Marc Dietrich
2005-01-04 14:42             ` Sebastian Heutling
     [not found]             ` <1104850036.6164.25.camel@weizen.left.earth>
2005-01-05 11:33               ` Marc Dietrich
2005-01-05 15:47                 ` Sven Luther
2005-01-05 17:10                   ` Christian
2005-01-05 17:39                     ` Sven Luther
2005-01-06 16:00                       ` Christian
2005-01-06 16:27                         ` Sven Luther
2005-01-06 20:27                           ` Christian
2005-01-06 21:07                             ` Sven Luther
2005-01-06 21:21                               ` Christian
2005-01-06 21:49                                 ` Sven Luther
2004-12-31  9:55   ` Sven Luther
2004-12-31 15:00     ` Sebastian Heutling
2004-12-31 22:28       ` Sven Luther
2005-01-01 23:56         ` Sebastian Heutling [this message]
2005-01-02  9:39           ` Sven Luther
2005-01-02 21:33             ` Sebastian Heutling
     [not found] ` <200501051733.06350.marvin24@gmx.de>
     [not found]   ` <20050105165551.GA29287@pegasos>
2005-01-05 20:57     ` Marc Dietrich
2005-01-09 23:17       ` Sebastian Heutling
2005-01-10  6:34         ` Sven Luther
2005-01-10 15:19           ` Sebastian Heutling
2005-01-10  6:54         ` Sven Luther
  -- strict thread matches above, loose matches on Subject: below --
2005-01-04  2:12 Christian
2005-01-04 13:23 ` Marc Dietrich
2005-01-04 15:08   ` Christian
2004-12-04 22:45 Christian Kujau
2004-12-05  0:41 ` Sebastian Heutling
2004-12-05 17:41   ` Christian Kujau
2004-12-06  1:46     ` Sebastian Heutling

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=1104623790.10369.14.camel@weizen.left.earth \
    --to=sheutlin@gmx.de \
    --cc=Marc.Dietrich@ap.physik.uni-giessen.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sven.luther@wanadoo.fr \
    /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).