From: Jonathan McDowell <noodles@earth.li>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re-add quirk for ServerWorks bridge secondary buses
Date: Mon, 28 Mar 2011 13:36:53 -0700 [thread overview]
Message-ID: <20110328203653.GL4835@earth.li> (raw)
In-Reply-To: <AANLkTimDV5m0Ug5H76HcdfFNrJaZcdGrChxVpCp9dMW6@mail.gmail.com>
On Thu, Mar 24, 2011 at 05:58:30PM -0700, Bjorn Helgaas wrote:
> On Thu, Mar 24, 2011 at 11:27 AM, Jonathan McDowell
> <noodles@earth.li>wrote:
>
> > On Wed, Mar 23, 2011 at 10:50:20PM -0700, Bjorn Helgaas wrote:
>
> > > I assume that since you don't have a standard BIOS, you don't have
> > > ACPI?
> >
> > Nope. Nor DMI. As previously mentioned there is a custom ASIC, but
> > it's hidden behind these bridges.
> >
>
> Thanks. Looks like your box doesn't even have PCI BIOS, so
> pcibios_last_bus == -1 until pci_fixup_serverworks() updates it, so we
> only scan bus 00.
>
> Another option would be to boot with "pci=lastbus=0xff". If you just
> have a box or two, that might be the easiest solution, but I guess I'm
> not opposed to a quirk like this. It's a firmware workaround, not a
> hardware bug, and the message is irrelevant and possibly distracting
> on machines with decent firmware, but it's not terrible.
I've managed to get detection of the non-standard BIOS working, so I can
actually quirk much more specifically now for my purposes. I don't
believe there's any need to take this upstream if no one else is
reporting problems.
J.
--
"This sentence no verb." -- Robin Stevens, ox.talk
This .sig brought to you by the letter T and the number 42
Product of the Republic of HuggieTag
prev parent reply other threads:[~2011-03-28 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 4:36 [PATCH] Re-add quirk for ServerWorks bridge secondary buses Jonathan McDowell
2011-03-24 5:50 ` Bjorn Helgaas
2011-03-24 18:27 ` Jonathan McDowell
[not found] ` <AANLkTimDV5m0Ug5H76HcdfFNrJaZcdGrChxVpCp9dMW6@mail.gmail.com>
2011-03-28 20:36 ` Jonathan McDowell [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=20110328203653.GL4835@earth.li \
--to=noodles@earth.li \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 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.