From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Raymond Waldrop <rwaldrop@sbcglobal.net>,
Bill Fink <billfink@mindspring.com>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: aic7xxx breakage
Date: Sun, 11 Aug 2002 10:26:15 +0200 [thread overview]
Message-ID: <20020811082616.1423@192.168.4.1> (raw)
In-Reply-To: <20020810084648.A1510@adsl-208-190-252-230.dsl.wchtks.swbell.net>
>Ben,
>
>I also encountered this problem on a dual G4 450 (AGP graphics). On the
>theory that more information is often useful (or at least easily deleted
>from the email queue), I am sending the results of "lspci -vv" as well as
>a couple of dmesg logs. The last kernel I made that works with the card
>is a 2.4.19-rc1 kernel from the linuxppc_2_4 tree. This is the kernel
>I was running for the lspci output. I am also sending dmesg logs from
>this kernel, and from a 2.4.19 kernel built from the linuxppc_2_4_devel
>tree. If they would be useful, I can also send diffs of any of the PCI
>driver source code files between the two trees. (I don't know how many
>versions you might have laying around easily fed into diff.)
Ok, can you both try editing arch/ppc/kernel/pci.c, and in
pcibios_init(), replace the call to pcibios_assign_resource()
with a call to pci_assign_unassigned_resources() and tell me
what happens ?
If the resulting kernel boots, please send me the dmesg log and
the lspci -vv output.
Thanks
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-08-11 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020810084648.A1510@adsl-208-190-252-230.dsl.wchtks.swbell.net>
2002-08-11 8:26 ` Benjamin Herrenschmidt [this message]
2002-08-11 9:57 ` aic7xxx breakage Bill Fink
2002-08-11 8:41 ` Benjamin Herrenschmidt
2002-08-11 11:54 ` Bill Fink
2002-08-11 9:17 ` Benjamin Herrenschmidt
2002-08-21 10:12 ` Benjamin Herrenschmidt
2002-08-21 23:20 ` Bill Fink
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=20020811082616.1423@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=billfink@mindspring.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rwaldrop@sbcglobal.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.