From: Bob Brose <linuxppcdev@lists.qbjnet.com>
To: linuxppc-dev@ozlabs.org
Subject: PReP PCI resource allocations
Date: 12 Feb 2006 21:01:23 -0000 [thread overview]
Message-ID: <20060212210123.24360.qmail@kunk.qbjnet.com> (raw)
This is a 7248-133 43p. I had a lot of trouble with the early 2.6
kernels on this prep machine however 2.6.14.7 runs well (the
vga console driver even works now). There is one thing I noticed
different from 2.4.32 involving PCI resources. On 2.6.14.7 I get...
Total memory = 192MB; using 512kB for hash table (at c0300000)
Linux version 2.6.14.7 (root@oldbb) (gcc version 4.0.3 20051201 (prerelease)
(Debian 4.0.2-5)) #4 Fri Feb 10 13:27:45 CST 2006
PReP architecture
IBM planar ID: f7
...
PCI: Probing PCI hardware
Setting PCI interrupts for a "IBM 7248, PowerSeries 830/850 (Carolina)"
PCI: Cannot allocate resource region 0 of device 0000:00:0c.0
PCI: Cannot allocate resource region 1 of device 0000:00:0c.0
PCI: Cannot allocate resource region 0 of device 0000:00:10.0
The regions correspond to:
Region 0: I/O ports at 80001020 [size=32] of the builtin pcnet32 ethernet.
Region 1: Memory at c0800100 (32-bit, non-prefetchable) [size=32] pcnet32..
Region 0: I/O ports at 80001400 [size=256] of the Symbios Logic 53c810 scsi.
Both the ethernet and scsi work fine though..
2.4.32 remaps these...
Linux version 2.4.32 (root@oldbb) (gcc version 2.95.4 20011002
(Debian prerelease)) #2 Tue Feb 7 12:30:21 CST 2006
PReP architecture
IBM planar ID: 000000f7
...
PCI: Cannot allocate resource region 0 of device 00:0c.0
PCI: Cannot allocate resource region 0 of device 00:10.0
PCI: moved device 00:0c.0 resource 0 (101) to 1020
PCI: moved device 00:0c.0 resource 1 (200) to 0
PCI: moved device 00:10.0 resource 0 (101) to 1400
Is this important??
2.6.15 BTW doesn't work at all. I need to hook up a serial console to
see if I can figure out what is going on...
Bob
reply other threads:[~2006-02-12 21:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060212210123.24360.qmail@kunk.qbjnet.com \
--to=linuxppcdev@lists.qbjnet.com \
--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