linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: linuxppc-dev@ozlabs.org
Subject: PREP sym53c8xx sym53c8xx brokeness due to 2.6.9-rc1-bk1 introduced residual data patch ...
Date: Tue, 29 Mar 2005 01:23:55 +0200	[thread overview]
Message-ID: <20050328232355.GA1982@pegasos> (raw)

Hello,

I have been investigating the prep breakage of the sym53c8xx driver on my
powerstack II in recent kernels, and traced it to the residual data patch,
or more exactly to the whole prep_pci.c/prep_setup.c patches that where
introduced between 2.6.9-rc1 and 2.6.9-rc1-bk1. I didn't have time to find
more details as the patch is not so small, and seems to do many things, and
linux.bkbits.net seems done right now.

Mmm, after a bit more of investigation, the changeset breaking it is :

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/08/16 10:35:18-07:00 trini@kernel.crashing.org
#   ppc32: On PReP, use residual data for PCI dev -> IRQ, and use it.
#
#   Signed-off-by: Leigh Brown <leigh@solinno.co.uk>
#   Signed-off-by: Tom Rini <trini@kernel.crashing.org>
#
# include/asm-ppc/residual.h
#   2004/08/16 10:35:09-07:00 trini@kernel.crashing.org +7 -0
#   This adds a function to use the residual data to determine the IRQ
#   for a given PCI device, and changes prep_pcibios_fixup() to use it.
#
# arch/ppc/platforms/residual.c
#   2004/08/16 10:35:09-07:00 trini@kernel.crashing.org +60 -0
#   This adds a function to use the residual data to determine the IRQ
#   for a given PCI device, and changes prep_pcibios_fixup() to use it.
#
# arch/ppc/platforms/prep_pci.c
#   2004/08/16 10:35:09-07:00 trini@kernel.crashing.org +37 -23
#   This adds a function to use the residual data to determine the IRQ
#   for a given PCI device, and changes prep_pcibios_fixup() to use it.

Mmm, i guess this makes sense, since it seems the sym53c8xx doesn'y find its
irq anymore or something. Tom Rini, or Leigh Brown, do you have any comments
on this one ? 

Friendly,

Sven Luther

             reply	other threads:[~2005-03-28 23:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 23:23 Sven Luther [this message]
2005-03-31 14:28 ` PREP sym53c8xx sym53c8xx brokeness due to 2.6.9-rc1-bk1 introduced residual data patch Tom Rini
2005-03-31 18:45   ` Sven Luther
2005-04-05  0:03     ` Christian
2005-04-05  5:39       ` Sven Luther
2005-04-05 14:38         ` Tom Rini
2005-04-05 15:23           ` Sven Luther
2005-04-05 15:47             ` Tom Rini
2005-04-06  1:47           ` Christian
2005-04-06  1:58             ` Christian
2005-04-06 18:50             ` Tom Rini
2005-04-08 11:36               ` Leigh Brown
2005-04-08 14:54                 ` Tom Rini
2005-04-08 15:51                   ` Christian
2005-04-08 15:57                     ` Tom Rini
2005-04-09 11:33                 ` [PATCH 2.6.11+] ppc32: Make the Powerstack II Pro4000 boot again Leigh Brown
2005-04-13  5:18                   ` Greg KH

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=20050328232355.GA1982@pegasos \
    --to=sven.luther@wanadoo.fr \
    --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).