Linux PARISC architecture development
 help / color / mirror / Atom feed
From: northern snowfall <dbailey27@ameritech.net>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] 2.4.23 PCI source inconsistency
Date: Wed, 03 Dec 2003 16:50:38 -0500	[thread overview]
Message-ID: <3FCE5AAE.6080104@ameritech.net> (raw)

Hey all,
    I compiled 2.4.23 from kernel.org for 32bit PA-RISC today
and found that the PA-RISC specific PCI code seems to be out-
of sync with the generic pci code.

from arch/parisc/kernel/pci.c:

gcc -D__KERNEL__ -I/usr/home/north_/k/linux-2.4.23/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common 
-fomit-frame-pointer -D__linux__ -pipe -fno-strength-reduce 
-mno-space-regs -mfast-indirect-calls -mdisable-fpregs 
-ffunction-sections -march=2.0 -mschedule=8000   -nostdinc -iwithprefix 
include -DKBUILD_BASENAME=pci  -c -o pci.o pci.c
pci.c: In function `pcibios_init_bus':
pci.c:310: structure has no member named `bridge_ctl'
pci.c:311: structure has no member named `bridge_ctl'
pci.c:312: structure has no member named `bridge_ctl'
pci.c:315: structure has no member named `bridge_ctl'
make[1]: *** [pci.o] Error 1

Of course, the pci_bus structure is declared in the header
include/linux/pci.h:/^struct.*pci_bus However, there is
no longer a bridge_ctl member.

I'm running 2.4.17 off the Debian 3.0 release on a B2000,
and /usr/include/linux/pci.h still has the bridge_ctl
member in the pci_bus structure.

Advice?

Thanks,
Don (north_)

             reply	other threads:[~2003-12-03 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 21:50 northern snowfall [this message]
2003-12-03 20:56 ` [parisc-linux] 2.4.23 PCI source inconsistency Carlos O'Donell
2003-12-04  5:45 ` 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=3FCE5AAE.6080104@ameritech.net \
    --to=dbailey27@ameritech.net \
    --cc=parisc-linux@lists.parisc-linux.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