From: Thomas Andrews <tandrews@grok.co.za>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: pci_enable_device() and pci=routeirq
Date: Wed, 06 Dec 2006 08:54:49 +0200 [thread overview]
Message-ID: <45766939.80303@grok.co.za> (raw)
In-Reply-To: <200612051058.19960.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> On Monday 04 December 2006 21:50, Thomas Andrews wrote:
>> On Mon, Dec 04, 2006 at 02:20:12PM -0700, Bjorn Helgaas wrote:
>>> Can you post the entire dmesg log with and without "pci=routeirq"?
>> And here it is with "pci=routeirq":
>
> I think this is a BIOS bug. Are there any updates available?
>
> My guess is that 0000:00:0a.0[A] is really connected to LNKC,
> and the BIOS writer forgot to tell us that.
>
> Without "pci=routeirq", we leave LNKC disabled. With
> "pci=routeirq", we enable LNKC at IRQ 10 for 0000:00:0e.0[A]
> even though you don't have a driver for the 0000:00:0e.0 device,
> and I think this makes the 0000:00:0a.0[A] interrupt work as
> a side-effect.
>
> If you load a driver for the firewire device at 0000:00:0e.0,
> that should enable LNKC, and I bet that will make your qozap
> driver start working.
Compiling firewire support into the kernel does indeed make it start
working, so your theory appears to be 100% correct. Is there any way to
confirm the BIOS bug by looking at the DSDT code? I am in touch with the
manufacturers of the board, so it would be very nice if I could just
send them a patch. (The board is quite new and there are no updates.)
Thanks again for your assistance - this has been *really* helpful!
Thomas
next prev parent reply other threads:[~2006-12-06 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 15:05 pci_enable_device() and pci=routeirq Thomas Andrews
2006-12-04 17:49 ` Bjorn Helgaas
2006-12-04 19:29 ` Thomas Andrews
2006-12-04 21:20 ` Bjorn Helgaas
2006-12-05 4:39 ` Thomas Andrews
2006-12-05 4:50 ` Thomas Andrews
2006-12-05 17:58 ` Bjorn Helgaas
2006-12-06 6:54 ` Thomas Andrews [this message]
2006-12-06 16:45 ` Bjorn Helgaas
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=45766939.80303@grok.co.za \
--to=tandrews@grok.co.za \
--cc=bjorn.helgaas@hp.com \
--cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox