From: Greg KH <gregkh@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Matthew Wilcox <matthew@wil.cx>, Andi Kleen <ak@suse.de>,
tom.l.nguyen@intel.com
Subject: Re: Status of PCI domain support?
Date: Fri, 2 Dec 2005 13:38:11 -0800 [thread overview]
Message-ID: <20051202213811.GA3948@suse.de> (raw)
In-Reply-To: <4390B752.90006@pobox.com>
On Fri, Dec 02, 2005 at 04:06:26PM -0500, Jeff Garzik wrote:
>
> The lack of PCI domain support on x86-64 prevents me from seeing the
> following devices on the PCI bus:
>
> 61:04.0 RAID bus controller: Silicon Image, Inc. Adaptec AAR-1210SA SATA
> HostRAID Controller (rev 02)
> 61:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
> Fusion-MPT Dual Ultra320 SCSI (rev 07)
> 61:06.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
> Fusion-MPT Dual Ultra320 SCSI (rev 07)
>
> I get the following errors, unless I disable the BIOS option 'ACPI bus
> segmentation', which is enabled by default (and will be enabled on most
> future machines):
>
> Dec 2 10:40:18 localhost kernel: ACPI: PCI Root Bridge [PCI1] (0001:40)
> Dec 2 10:40:18 localhost kernel: PCI: Multiple domains not supported
> Dec 2 10:40:18 localhost kernel: ACPI: PCI Root Bridge [PCI2] (0002:80)
> Dec 2 10:40:18 localhost kernel: PCI: Multiple domains not supported
>
> Full machine info was just posted in another message, subject
> "[2.6.15-rc4] oops in acpiphp".
>
> Is this a bug? Is this expected behavior (not implemented yet)? A
> jump-start on tracking this down would be appreciated.
Based on the logic in arch/i386/pci/acpi.c (which is shared with
x86-64), it's just not implemented yet at all.
I don't know of anyone currently working on adding this support to this
code, does anyone else?
thanks,
greg k-h
next prev parent reply other threads:[~2005-12-02 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 21:06 Status of PCI domain support? Jeff Garzik
2005-12-02 21:38 ` Greg KH [this message]
2005-12-03 1:46 ` Jeff Garzik
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=20051202213811.GA3948@suse.de \
--to=gregkh@suse.de \
--cc=ak@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tom.l.nguyen@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.