From: Grant Grundler <grundler@parisc-linux.org>
To: northern snowfall <dbailey27@ameritech.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.4.23 PCI source inconsistency
Date: Wed, 3 Dec 2003 22:45:50 -0700 [thread overview]
Message-ID: <20031204054550.GB31404@colo.lackof.org> (raw)
In-Reply-To: <3FCE5AAE.6080104@ameritech.net>
On Wed, Dec 03, 2003 at 04:50:38PM -0500, northern snowfall wrote:
> 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.
As carlos said, use kernels from ftp.parisc-linux.org or pull
sources directly from cvs.parisc-linux.org.
> pci.c: In function `pcibios_init_bus':
> pci.c:310: structure has no member named `bridge_ctl'
I added this field to clean up FBB and VGA routing support.
"bridge_ctl" is a PCI-PCI Bridge register that controls
both of those behaviors. Ivan K. (ex PCI Maintainer) and I had it
working for parisc/ia32/alpha but apperently it never got
submitted/accepted into any official tree.
Russell King (ARM maintainer) found it useful anyway
and submitted it
http://www.ussg.iu.edu/hypermail/linux/kernel/0208.0/0723.html
and later:
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2003-October/017459.html
Darn...looks like bridge_ctl didn't get pushed into 2.6 either. :^(
I'll follow up a bit offline.
grant
prev parent reply other threads:[~2003-12-04 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 21:50 [parisc-linux] 2.4.23 PCI source inconsistency northern snowfall
2003-12-03 20:56 ` Carlos O'Donell
2003-12-04 5:45 ` Grant Grundler [this message]
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=20031204054550.GB31404@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=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