From: Tim Hockin <thockin@isunix.it.ilstu.edu>
To: macro@ds2.pg.gda.pl (Maciej W. Rozycki)
Cc: mj@suse.cz (Martin Mares),
al10@inf.tu-dresden.de (Adam Lackorzynski),
linux-kernel@vger.kernel.org (Kernel Mailing List)
Subject: Re: [PATCH] PCI-Devices and ServerWorks chipset
Date: Mon, 22 Jan 2001 21:01:36 -0600 (CST) [thread overview]
Message-ID: <200101230301.VAA13439@isunix.it.ilstu.edu> (raw)
In-Reply-To: <Pine.GSO.3.96.1010117122300.22695B-100000@delta.ds2.pg.gda.pl> from "Maciej W. Rozycki" at Jan 17, 2001 12:25:39 PM
> > patch is wrong -- it doesn't make any sense to scan a bus _range_. The registers
> > 0x44 and 0x45 are probably ID's of two primary buses and the code should scan
> > both of them, but not the space between them.
>
0x44 is the primary bus number of the host bridge, and 0x45 is the
subordinate bus number for the bridge. Just like a PCI-PCI bridge, but
different :) Since there are two CNB30 functions, each has unique values
for this. The primary bus of the second bridge must be the subordinate bus
of the first bridge + 1. PRIMARY(1) = SUBORDINATE(0) + 1;
Tim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-23 3:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 17:12 Adam Lackorzynski
2001-01-17 8:52 ` Martin Mares
2001-01-17 10:14 ` Adam Lackorzynski
2001-01-17 11:25 ` Maciej W. Rozycki
2001-01-17 21:17 ` Dan Hollis
2001-01-18 8:37 ` Maciej W. Rozycki
2001-01-18 10:01 ` Andre Hedrick
2001-01-18 11:08 ` Maciej W. Rozycki
2001-01-18 17:40 ` Andre Hedrick
2001-01-19 12:24 ` Maciej W. Rozycki
2001-01-23 3:01 ` Tim Hockin [this message]
2001-02-08 8:34 ` Martin Mares
2001-01-23 18:18 ` Adam Lackorzynski
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=200101230301.VAA13439@isunix.it.ilstu.edu \
--to=thockin@isunix.it.ilstu.edu \
--cc=al10@inf.tu-dresden.de \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=mj@suse.cz \
/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
all inboxes | Powered by JetHome®