linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Marc Dietrich <Marc.Dietrich@ap.physik.uni-giessen.de>
To: linuxppc-dev@ozlabs.org
Subject: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Sun, 26 Dec 2004 14:35:12 +0100	[thread overview]
Message-ID: <200412261435.13562.marc.dietrich@ap.physik.uni-giessen.de> (raw)


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 
had this problem also with the 2.4er kernels, but this was solved in later 
versions (I'm running 2.4.21 now). Now the old driver seem to be removed (or 
merged with sym53c8xx_2) and is only available to MCA and GSC devices.

I also tried to change the irq routings in prep_pci.c like in the latest patch 
with the sym53c8xx_2 driver,
	Slot 12 -> IRQ 15 (sym53c825)
	Slot 15 -> IRQ 11 (dec 21140)
but this didn't helped.

Has anyone a working config file for this machine (PowerStack II 4000/Utah)?

Thanks

Marc

             reply	other threads:[~2004-12-26 13:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-26 13:35 Marc Dietrich [this message]
2004-12-27  2:47 ` [FYI] linux 2.6 still not working with PReP (ppc32) 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
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=200412261435.13562.marc.dietrich@ap.physik.uni-giessen.de \
    --to=marc.dietrich@ap.physik.uni-giessen.de \
    --cc=linuxppc-dev@ozlabs.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).