public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Christian <evil@g-house.de>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	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: Sat, 26 Feb 2005 07:04:35 +0100	[thread overview]
Message-ID: <20050226060435.GA16401@pegasos> (raw)
In-Reply-To: <421FEF81.2070806@g-house.de>

On Sat, Feb 26, 2005 at 04:39:45AM +0100, Christian wrote:
> Sven Luther wrote:
> >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
> 
> dooh, these websvn patches are giving me a headache.... will have to 
> learn /usr/bin/svn first :-\

Well : 

  svn co svn://svn.debian.org/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches

> >--- kernel-source-2.6.8.orig/arch/ppc/platforms/prep_pci.c	2004-12-28
> 
> yes, the prep_pci.c and its irq-mappings. the PowerStackII lines were 
> changed back and forth, and a current 2.6-BK is only different in one 
> line to the patch you mentioned:

I guess the one line is the one for the IDE device, ..., indeed. The one line
in question is to enable the onboard IDE controller, which exist but is
probably not used, since the place on the board where it should be has no
connector soldered. I hear that there is an IDE powerstack II model though, so
...

> http://nerdbynature.de/bits/hal/2.6.11-rc5.patched/powerpc-prep-powerstack-irq_2.6.11-rc5.patch
> 
> unfortunately it did not help either and i'll switch back to vanilla 
> 2.6.8 again and hopefully find out exactly when scsi stopped working.

As i understand leigh's and other post, i believe that this is the fix, but
that other stuff went in too which did break.

> http://nerdbynature.de/bits/hal/2.6.11-rc5/
> http://nerdbynature.de/bits/hal/2.6.11-rc5.patched/

Friendly,

Sven Luther


      reply	other threads:[~2005-02-26  6:14 UTC|newest]

Thread overview: 18+ 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
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
2005-02-26  3:39                 ` Christian
2005-02-26  6:04                   ` Sven Luther [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=20050226060435.GA16401@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