linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH 2.4.0 parisc PCI support
Date: Fri, 02 Mar 2001 19:09:07 -0500	[thread overview]
Message-ID: <3AA03623.E37EEF04@mandrakesoft.com> (raw)
In-Reply-To: <200103022143.NAA29984@milano.cup.hp.com>

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

Just tested your patch on an x86 laptop with two CardBus controllers
(kernel's CardBus bridge code == kernel's PCI-PCI bridge code, for the
most part) and an SMP x86 desktop machine.

The patch worked 100% on my laptop, but failed to allocate a PCI memory
region on my desktop machine.  Two attachments... "diff -u" output for
dmesg before and after your patch, and "diff -u" output for lspci before
and after your patch.

-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie

[-- Attachment #2: dmesg.diff --]
[-- Type: text/plain, Size: 2844 bytes --]

--- rum-dmesg-before.txt	Fri Mar  2 17:42:33 2001
+++ rum-dmesg-after.txt	Fri Mar  2 17:07:17 2001
@@ -1,4 +1,4 @@
-Linux version 2.4.2 (jgarzik@rum.normnet.org) (gcc version 2.96 20000731 (Linux-Mandrake 8.0)) #5 SMP Fri Mar 2 17:37:39 EST 2001
+Linux version 2.4.2 (jgarzik@rum.normnet.org) (gcc version 2.96 20000731 (Linux-Mandrake 8.0)) #2 SMP Fri Mar 2 16:52:53 EST 2001
 BIOS-provided physical RAM map:
  BIOS-e820: 000000000009fc00 @ 0000000000000000 (usable)
  BIOS-e820: 0000000000000400 @ 000000000009fc00 (reserved)
@@ -29,7 +29,7 @@
 ide_setup: ide0=autotune
 ide_setup: ide1=autotune
 Initializing CPU#0
-Detected 400.918 MHz processor.
+Detected 400.915 MHz processor.
 Console: colour VGA+ 80x25
 Calibrating delay loop... 799.53 BogoMIPS
 Memory: 126276k/131060k available (1209k kernel code, 4396k reserved, 434k data, 192k init, 0k highmem)
@@ -138,19 +138,19 @@
 IRQ19 -> 19
 .................................... done.
 calibrating APIC timer ...
-..... CPU clock speed is 400.9022 MHz.
-..... host bus clock speed is 100.2254 MHz.
-cpu: 0, clocks: 1002254, slice: 334084
-CPU0<T0:1002240,T1:668144,D:12,S:334084,C:1002254>
-cpu: 1, clocks: 1002254, slice: 334084
-CPU1<T0:1002240,T1:334064,D:8,S:334084,C:1002254>
+..... CPU clock speed is 400.9365 MHz.
+..... host bus clock speed is 100.2340 MHz.
+cpu: 0, clocks: 1002340, slice: 334113
+CPU0<T0:1002336,T1:668208,D:15,S:334113,C:1002340>
+cpu: 1, clocks: 1002340, slice: 334113
+CPU1<T0:1002336,T1:334096,D:14,S:334113,C:1002340>
 checking TSC synchronization across CPUs: passed.
 PCI: Using configuration type 1
 PCI: Probing PCI hardware
 PCI: IDE base address fixup for 00:04.1
 PCI: Scanning for ghost devices on bus 0
 PCI: Scanning for ghost devices on bus 1
-Unknown bridge resource 0: assuming transparent
+PCI : ignoring 00:01.0 PCI-PCI bridge (I/O BASE not configured)
 PCI: IRQ init
 PCI: Interrupt Routing Table found at 0xc00f0d20
 00:0c slot=01 0:60/1eb8 1:61/1eb8 2:62/1eb8 3:63/1eb8
@@ -179,6 +179,8 @@
 PCI: Resource ce800000-ce800fff (f=200, d=0, p=0)
 PCI: Resource 0000b400-0000b47f (f=101, d=0, p=0)
 PCI: Resource d0000000-d7ffffff (f=200, d=0, p=0)
+PCI: Cannot allocate resource region 0 of device 01:00.0
+PCI: Failed to allocate resource 0 for 01:00.0
 Limiting direct PCI/PCI transfers.
 Linux NET4.0 for Linux 2.4
 Based upon Swansea University Computer Society NET3.039
@@ -186,7 +188,7 @@
 IA-32 Microcode Update Driver: v1.08 <tigran@veritas.com>
 Starting kswapd v1.8
 pty: 256 Unix98 ptys configured
-block: queued sectors max/low 83802kB/27934kB, 256 slots per queue
+block: queued sectors max/low 83794kB/27931kB, 256 slots per queue
 RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
 Uniform Multi-Platform E-IDE driver Revision: 6.31
 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx

[-- Attachment #3: lspci.diff --]
[-- Type: text/plain, Size: 629 bytes --]

--- rum-lspci-before.txt	Fri Mar  2 17:42:23 2001
+++ rum-lspci-after.txt	Fri Mar  2 17:07:26 2001
@@ -88,7 +88,7 @@
 	Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 	Latency: 64 (1250ns min, 63750ns max), cache line size 08
 	Interrupt: pin A routed to IRQ 16
-	Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=128M]
+	Region 0: Memory at <ignored> (32-bit, non-prefetchable) [size=128M]
 	Expansion ROM at e5ff0000 [disabled] [size=64K]
 	Capabilities: [dc] Power Management version 1
 		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

  reply	other threads:[~2001-03-03  0:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-02 19:32 PATCH 2.4.0 parisc PCI support Grant Grundler
2001-03-02 20:46 ` Jeff Garzik
2001-03-02 21:43   ` Grant Grundler
2001-03-03  0:09     ` Jeff Garzik [this message]
2001-03-03  0:42       ` Grant Grundler
2001-03-04 12:19 ` Ivan Kokshaysky
2001-03-05 22:16   ` Grant Grundler
2001-03-06 17:20     ` Ivan Kokshaysky
2001-03-06 20:57       ` Grant Grundler
2001-03-07 14:48         ` Ivan Kokshaysky
2001-03-08  1:27           ` Grant Grundler

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=3AA03623.E37EEF04@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=grundler@cup.hp.com \
    --cc=linux-kernel@vger.kernel.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).